<p>
</p>
<p>
</p>
<p>Yet it’s not quite that simple, as the last few years have demonstrated in excruciating detail. I agree that plenty of people on Wall Street generated giant returns for themselves in the short-run…but only by creating not ‘true’ returns, but rather ‘fictitious’ returns where the risks were secretly bundled only to appear later like a baleful jack-in-the-box. Or, put in financial jargon, future-laden beta was disguised as alpha. All of the bankers who synthesized toxic securities throughout the early to mid-2000’s whose risks only became apparent years later earned huge annual bonuses, and they’re not giving any of it back. Hence, the employees managed to shift downside risk to bank shareholders. Bank employees therefore enjoyed the ultimate ‘call’ option: during high times, they make huge bonuses, but when times are bad, they just lose somebody else’s money. {Bank shareholders then in turn propagate the chain of risk by shifting a chunk of their downside to the taxpayers who are summoned for bailouts.} </p>
<p>
</p>
<p>
</p>
<p>And here I believe we have the seeds of what I had hoped cosmicfish and others would have provided. I had set the foundation for just such a litany of non-obvious but actionable steps that engineers can take to capture more of the value that they create. Consider the following points:</p>
<p>*Learn as much about the patent system as you can. Ideally, you should try to pass the exam to become a patent agent as soon as you can. (You do not need a law degree to become a patent agent).</p>
<p>*Take college lab courses that teach you how to develop inventions that are actually patentable (and where you, and not the university, control the patent). </p>
<p>As a case in point, MIT offers a product design & development course that is cross-listed between the mechanical engineering and the Sloan School of Management where teams of students are tasked to build their own invention. At the end of the course, many students will actually apply for patents for the projects they developed, where such patents will be under their own names and control, not under the control of MIT. </p>
<p>Other courses may not be specifically geared towards teaching you how to design/develop a product, but can nevertheless be useful by teaching you practical design skills. For example, your electric circuits lab course can actually teach you how to build actual working circuits, including how to use a breadboard, multimeter, oscilloscope, and various electrical components. For every new lab skill you learn, you should be thinking about where to procure the gear for yourself should you want to use it for a project on your own (i.e. on Ebay, Radio Shack, etc.). A good chemistry lab textbook can teach you a multitude of useful techniques that you can replicate for yourself with a cheap home lab. The real goal is then to develop a skillset of practical skills that can be used to build a real project, all by yourself. For example, I believe that every graduating electrical engineer should know how to build a basic working radio and every graduating mechanical engineer should know how to build a basic toy car out of parts bought from Ebay. </p>
<p>
</p>
<p>But this I cannot agree with. As I said, a defining feature of strategy is not simply determining what you should do, but also what you will not do (or, at least, do as little as you can possibly get away with). To say that you should learn everything is not a workable suggestion, the key is to figure out what you should learn and what you should not learn.</p>
<p>Hence, I would say that you should probably not learn the upper reaches of engineering theory, for that is not patentable. As a matter of law, you can’t patent basic ideas, but only implementations of ideas. Hence, pure theories are largely unpatentable. Learning how to derive theories from first principles is then, frankly, not a very useful skill. You may need to know it to pass your exams, but frankly, unless you are heading for an academic career, you have no long-term use for that skill.</p>