contents/articles/making-it-big-in-software.html
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 |
----- title: "Book Review: Making it Big in Software" content-type: article subtitle: "A handbook for (almost) guaranteed success in IT" timestamp: 1285406501 tags: "review|books|software" pdf: true ----- <section class="section"> <p>When this book came out, it was immediately followed by a lot of buzz. Positive reviews started popping up almost instantly, a lot of people blogged about it, it was surrended by a lot of… what’s that word again? Oh yes, <em>hype</em>. The title pissed me off really: who on Earth wants to title his book <a href="http://bit.ly/b08auR">Making it Big in Software</a>? Steve Jobs? Bill Gates?</p> <p>No, just a guy named <a href="http://lightstone.x10hosting.com/">Sam Lightstone</a>. When I was offered a review copy, I was a bit reluctant to even bother: I thought it was one of those overly-hyped titles that claim to make you famous and successful, but all they do stating the obvious: work hard, be innovative, use your money wisely, etc. Well, this book is not one of them.</p> <p>When I got my copy, I immediately read the author’s bio on the second-last page of the book: Sam Lightstone runs a site called <a href="http://makingitbigcareers.com/">Making it Big Careers</a> (again, I got instantly worried by this), <em>but</em> also happens to be one of the brightest minds in <span class="caps">IBM</span>, a <a href="http://en.wikipedia.org/wiki/IBM_Master_Inventor"><span class="caps">IBM</span> Master Inventor</a>, author and co-author of 30+ patents.</p> <p><img src="/images/pictures/books/making-it-big.jpg" class="right" /><br /> The 17 exclusive interviews with software gurus, visionaries, minor and major deities of the IT world are definitely worth the 24.99$ this book costs <em>on their own</em>. This was one of the major selling points of the book itself (as the merry-looking pictures of Marissa Mayer, James Gosling, Steve Wozniak and John Schwarz on the cover suggest), but far from being the only one. The interviews are strategically placed throughout the book, as supporting material for the author’s advice: if you don’t believe him, you will believe those who <em>made it</em>. Anyhow, let’s say something about the book itself, shall we?</p> <p><em>Making it Big with Software</em> is divided into three parts:</p> <ul> <li><strong>Part I: Fundamentals</strong> — all you need to know to get hired. Finish school, learn new things, and get a job in the Software industry.</li> <li><strong>Part II: Leadership</strong> — tips on what to do to start climbing the corporate ladder, from junior to senior manager.</li> <li><strong>Part <span class="caps">III</span>: Greatness</strong> — go beyond a successful career and become a luminary in IT, an example for future generations (and earn the big bucks).</li> </ul> <section class="section"> <header> <h1 id="h_1" class="toc">Part I: Fundamentals</h1> </header> <p>After two introductory chapters, aimed at answering questions like “Why bother?” or “What do big shots in software do?”, the book starts analyzing what graduates get when they get out of school. I was really taken by the following paragraph, outlining the main difference between school and work:</p> <blockquote> <p>[…] although schools encourage students to do their own work, on penalty of expulsion or severe reprimand, professional work is saturated with the ubiquitous mantra of “teamwork.” In school, your success depends on individual effort, whereas professional life depends frequently on your ability to work in teams.</p> </blockquote> <p>So true. I never thought about it until I read it in this book. And this is a common causes of failure in the workplace: not being able to work in a team. It’s understandable: after years of striving to be the best, to do things for yourself, you’re suddenly asked to work for and with others.</p> <p>The author gives junior graduates some useful tips to get a job in software development (or the software industry in general), with some useful tips on how to create a proper résumé, how to survive interviews, the usual. Hell I wish I had this book when I started!</p> <p>Readers like me who already have a job should not dismiss this part. Maybe skim through the first few chapters, but towards the end there are some useful suggestions on how to build essential interpersonal skills and a nicely-written chapter about <em>career killers</em>.</p> </section> <section class="section"> <header> <h1 id="h_2" class="toc">Part II: Leadership</h1> </header> <p>The second part of the book opens with <strong>Chapter 9</strong>, Working the Org, which I found most amusing for the funny, but insightful, <em>Negotiating 101</em> section. Again, particular emphasis is put on non-technical skills, which are however essential for success. I particularly enjoyed reading this part of the book, because I could relate to it, being a Technical Leader myself.</p> <p><strong>Chapter 12</strong> is a must-read, as the author himself says:</p> <blockquote> <p>If you read only one chapter in this book, this should probably be the one.</p> </blockquote> <p>If you never read anything about time management, you rhave to read this, as it helps you realize how much time you waste, why, and what you can do to improve the situation. I attended a course on the subject at work, a while ago, and I was shocked to read most of the stuff I learned at that course so tidily organized in no-nonsense prose in this chapter. Granted, it doesn’t substitute a time management course or practical experience with managing your priorities, but it is a good starting point.</p> <p><strong>Chapter 14</strong> deals with <em>Zen and the critical art of balance [between work and personal life]</em>. The diagram on page 249 scared the hell out of me. Here it is, transposed in tabular form: </p> <table> <tr> <th>Desired State</th> <th>Current State</th> </tr> <tr> <td>Work: 9 hours</td> <td>Work: 13 hours</td> </tr> <tr> <td>Sleep: 8 hours</td> <td>Sleep: 6 hours</td> </tr> <tr> <td>Travel: 1 hour</td> <td>Travel: 2 hours</td> </tr> <tr> <td>Family & Leisure: 4 hours</td> <td>Family & Leisure: 1 hours</td> </tr> <tr> <td>Chores & Hygiene: 2 hours</td> <td>Chores & Hygiene: 2 hours</td> </tr> </table> <p><em>Thirtheen hours</em>? Really? If <em>you</em> work 13-hour days then you have to read this chapter <em>and put it into practice</em> instantly or you’ll regret it. Luckily <em>I</em> manage to work most of the time for 8 hours a day (as everyone should, by law).</p> <p>Another chapter I particularly enjoyed (and will re-read periodically) is <strong>Chapter16</strong>, which contains the best definition of leadership I ever came across:</p> <blockquote> <p>“Leadership is communicating to people their worth and potential so clearly that they come to see it in themselves.”</p> </blockquote> <p style="margin-left: 4em">– Stephen Covey</p> <p>Again, this chapter teaches you the basics on leadership and management. If you didn’t take a course on the subject yet, it’s definitely worth a read.</p> </section> <section class="section"> <header> <h1 id="h_3" class="toc">Part III: Greatness</h1> </header> <p>I particularly enjoyed the first two chapters of this last part: <strong>Chapter 17</strong> and <strong>Chapter 18</strong> are about <em>innovation</em>, which I found to be the fastest and best way to get noticed in a company.</p> <p>These two chapters won’t teach you to become a genius or an inventor, but they do provide help on the subject: why innovating is important, how to innovate and what to do once your idea gets a shape. The <em>Patenting</em>, <em>Publishing</em> and <em>Public Speaking</em> sections in chapter 8 are useful and practical, and deserve a good read. Again, the book does not go too in-depth, but the author provides just enough information to make you aware of the main issues.</p> <p>The final chapters of the book felt a bit distant from my current work reality. Business talk, stock options, startups, acquisitions… They may interest some readers with an enterpreneurial mindset, but not me, at least not now. Nonetheless, business and politics pay a very important role in any IT job, so it’s wise to be aware of them.</p> </section> <section class="section"> <header> <h1 id="h_4" class="toc">The Interviews</h1> </header> <p>The 17 interviews with software gurus, miracle workers and other extremely successful chaps make up for about the 20% of the book. They are carefully placed by the author in specific places of the book where they make the most sense (well, most of the time). Every person had to answer a similar set of questions, like “How did you get started in software”, “How do you stay on top of technology trends and innovation?” or “Technical leaders and executives are famous for being time-strapped. What strategies do you use to stay sane and use your time effectively?”.</p> <p>Every interviews has at least one personal anecdotes. Some feel almost legendary, like the following:</p> <blockquote> <p>In 1967, at the age of 12, I dreamed of making a difference in the field of computer science. I went off to the local <span class="caps">IBM</span> office, literally knocked on their door, and said, “I will do anything for the summer-empty trash cans, you name it.” They said, “Go away kid.” But there was a sales guy who took pity upon me and threw me a nice Fortran IV [<span class="caps">IBM</span> Mathematical Formula Translating System] manual, with the expectation that I’d probably read it and get bored and never come back. But much to his surprise, I came back the following Monday and said, “Hey, this is cool! I just wrote a program and I want to run it.” The sales guy was so impressed that he found me an open computer to work on where I could teach myself how to keypunch, program, and debug for what I still recall as a delightful summer.</p> </blockquote> <p style="margin-left: 4em">– Grady Booch, <span class="caps">IBM</span> Fellow and Chief Scientist for Software Engineering, <span class="caps">IBM</span> Research</p> <p>Every interview provides at least a good piece of advice for newcomers to the field. The last chapter of the book summarizes the interviews attempting to draw the profile of the successful IT professional: some founded their own companies, other climbed up the corporate ladder, a few contributed with key inventions (email, the Internet, …) that changed society as we know it. Different levels of greatness, and different ways to reach it: this is what this book is really about.</p> </section> <section class="section"> <header> <h1 id="h_5" class="toc">Final Thoughts</h1> </header> <p><em>Making it Big in Software</em> is very well organized, in its three main parts. Unless you’re already the <span class="caps">CEO</span> of a multi-million-dollar company, you can learn something from this book, and even if you are, learning how other people <em>made it</em> is always beneficial.</p> <p>It is not a specialized book, and as such it does not go in depth on anything specific. This is a good thing though, because after you read some of the chapters you feel motivated to learn more about this or that particular topic, skill or problem. In a way, it can be a good surrogate for more specialized books about résumé creation, job interviews, time management, leadership etc.</p> <p>Overall, I recommend this book to everyone who wants to become successful in the software industry. Success can come to different degrees of course (or not come at all), but if you’re motivated enough and interested in your work, it is definitely within your grasp. <em>Be goal oriented</em>. It’s not enough, but it’s a good start.</p> </section> </section> |