Uber seems to hit a lot of legal challenges. It seems like, in every city, the incumbent taxi market has a different set of legal hurdles for you to pass through. It's kind of a shame, too, because everyone involved with Uber is making an honest living providing a needed service.
What's tends to be your day-to-day balance of being lawyer versus entrepreneur? Would you say that you have more legal woes than a normal startup? Do you think this is "par for the course" any time someone's starting an interesting company?
I disagree. American doctors have to take standardized board exams before they specialize. The exams are significantly more rigorous, and better-designed, than the job interviews that I run.
Specifically, in the American medical system, specialization happens with on-the-job training after taking a standard exam. Students seeking to be pediatricians, heart surgeons, and dermatologists all take the same standardized exam. The score is then presented when students apply to programs to specialize.
I find it very hard to judge skill when I interview candidates. I can easily filter out incompetent people. Someone I work with says, "when you interview people, all you find out is if the person interviews well."
Many professional fields have long professional exams. Civil engineers need to be certified, as well as doctors. Frankly, I wish I could look at some kind of a score, and spend most of the interview on "soft" topics.
I've heard that a co-worker of mine upgraded his MBP's SSD and RAM.
This website, http://www.everymac.com/systems/apple/macbook-air/macbook-air-faq/macbook-air-mid-2012-how-to-replace-upgrade-ssd-storage.html, seems to imply that the only thing you need is a funky screwdriver.
Back in the 90s, when computers cost $5,000-$10,000 in today's dollars, it made sense to keep upgrading them. Now the top-of-the-line computers are cheap enough that it's easier to just buy one that you can afford to replace every 4 years or so.
Let's not forget how bug free a framework used widely by thousands will be - there's no job security there at all if there's no bugfixing! But if we write our own, then there will surely be some horrific bug in the field that we can work until 4AM to fix, and management will call us heroes!
Counter that with the amount of time I've spent wresting design flaws due to well-known but poorly-chosen frameworks.
Don't pick a framework because you assume that you're supposed to:
The issue with frameworks is that they often touch all layers of a program, or product. If the wrong framework is chosen, (or built,) then the entire project must be refactored to recover from the mistake. That is why it's critical to understand the correct design pattern before choosing a framework or building your own.
"If truth is beauty, how come no one has their hair done in the library?" -- Lily Tomlin