19 ms·
Effective Engineer – Notes
- edmondlau 9y agoHi! I'm Edmond, the author of the book. Happy to answer any questions about my two-year journey in self-publishing the book.
- gdubs 9y agoWhat was the process like? How much time did you spend relative to other projects, and how did you incorporate your principles of leverage into creating the book?
- edmondlau 9y agoIn many ways, it was similar to building a startup product. I quit my full-time job at Quora and spent ten months full-time on the book (with bits of traveling). Like any other project, I drastically estimated how long it would take. I estimated one year; it ended up taking almost two. I finished the book while working full-time at Quip. At times, it was an amazing adventure. I loved going around Silicon Valley and interviewing people like Mike Krieger or Sam Schillace to get their stories and their most valuable lessons. Other times, there were also intense periods of self-doubt. The first person I shared a chapter draft with was my wife. She's also an engineer and by default can give quite critical feedback. And, wow, did I feel shut down after my first round of feedback. It's confusing! I don't understand the point of this! etc. I ended up spending two months iterating by myself on my next drafts to build up more confidence before sharing with more engineering friends -- they then really gave me the support I needed to feel confident about writing the book. The experience was a great lesson in how new ideas need to be nurtured, and you need to either find supporters who will nurture that for you, or ask for the type of feedback you want (which is what I now do with my wife). It was also a valuable lesson in getting feedback sooner on your project before you are too emotionally attached to feel comfortable about asking for feedback. All in all, it's one of my proudest accomplishments in my career.
- edmondlau 9y agoI also just remembered that I wrote this blog post a while back on what self-publishing taught me about shipping products. It also shares a few vignettes and lessons from my self-publishing experience. http://www.effectiveengineer.com/blog/lessons-from-self-publishing-on-shipping-products http://www.effectiveengineer.com/blog/lessons-from-self-publ...
- 0xdeadbeefbabe 9y agoI saw your google tech talk a while ago, and I really like the concept of leverage even though I usually dislike this genre https://www.youtube.com/watch?v=BnIz7H5ruy0 https://www.youtube.com/watch?v=BnIz7H5ruy0 I think people get too religious about effectiveness. I was wondering what you do when you don't want to follow a list of good things to do? I assume self-publishing was discouraging at times, wasn't it?
- edmondlau 9y agoTwo things I've learned since writing the book: 1) It's also important to align your energy levels and what you want to do with your list of high-leverage tasks. When you're really excited about doing something, even if isn't strictly the highest-leverage thing you could do, you can actually end up creating more impact because you do a much better job of it. 2) Sometimes what's needed is just a change in perspective about things you need to do. I play with this a lot in the leadership coaching that I do. For example, I hate responding to emails because processing them all feels like a chore. But if I reframe responding to emails in my mind to be hunting for gems that might lead to new opportunities, I'm much more likely to go through them (at least the ones that are gems). And oh yes, there were definitely discouraging points. The story about early, negative feedback from my wife (that I posted in another comment) was one. Another is that ten months into book writing, around the start of 2014, I started feeling a sense of intense FOMO from reading Hacker News. Stripe had raised a valuation round of over $1B, and WhatsApp had been acquired for $16B. That led to moments where I would wonder "What in the world was I doing writing a book?" and "When will I ever finish?". I had just finished a first draft, I wasn't sure how rewarding financially the book would be, and I was feeling like I had removed myself from the startup game. That led me to start looking for jobs, which quite fortunately, also led me to my current role at Quip. So everything worked out in the end.
- mzzter 9y agoHi Edmond, is “high leverage” a phrase you use in the book? From the notes, “leverage” is defined as “impact / time invested.” Why did you choose “leverage” to describe this concept? “Leverage” suggests to me that it is grown with the idea of using it to climb a career ladder, but I’d like to hear your thoughts on this, as I have read just these notes and not the book yet.
- edmondlau 9y agoYes, "high-leverage" is a phrase I use in the book. I learned about leverage when I read Andy Grove's High Output Management. Why the word leverage? Time is our most limited resource. And so the way to really increase our impact (say by 10x) is not to increase the number of hours you work, but to increase your rate of impact, which is how I define leverage in the book. Another way to think about leverage is in terms of a lever, which lets you apply a little bit of force, have it amplified, and then move large boulders. Many of the stories and strategies from the book talk about these leverage points in engineering, e.g. investing in iterating speed or validating your ideas early and often, where small bits of effort end up having a disproportionate impact.
- mzzter 9y agoThanks for your response, I understand it better now. Sorry for what must have seemed like a stupid question.
- davidjnelson 9y agoWhat’s the right level of completion for validation? A few weeks for a prototype seems reasonable, but even that can result in feedback that isn’t or isn’t considered fast enough.
- brucephillips 9y agoIt depends. Easily communicated product ideas can be validated on day 0 by talking to users. Less easily communicated ideas often need at least a demo. Dropbox is one example.
- brucephillips 9y agoHave you read much Drucker? You cover some of the same ideas.
- edmondlau 9y agoYep! I've read The Effective Executive. One of my big motivators for writing the book was that there were all these great ideas that were encapsulated in business books or personal improvement books, and very few books that would tie them back to engineering. That's the gap I wanted to fill.
- brucephillips 9y agoGreat. Though one of the complaints I have here is the same I have with Drucker, and the same that others have given: "Impact" is ill defined.
- edmondlau 9y agoYour observation is a key reason why taking the time to define your impact and to measure it is so important. As Drucker says, what gets measured gets improved. In business contexts, your engineering impact generally ties back to the business value you create (i.e. revenue and profit). If there is already some model for translating your area of work to revenue (e.g. increase users -> increase revenue, reduce fraud -> increase revenue) then that can also give another proxy metric to optimize for. So for example, when working on Google Search Quality, we would often just optimize for long clickthrough rates, knowing that strategically, the ads team would take care of turning returning searchers to revenue. It gets harder when you're working on areas like bigger bets (where you can have high impact but it is unknown for a long time) or in trying to understand an infrastructure investment in terms of its business value to the company. There, it may be sufficient to just know that something is of strategic value and then measure your impact in terms of those strategic goals.
- ashwinaj 9y agoHi Edmond, your book was great and I enjoyed reading it! I do have a question on your topic on high leverage work; as a startup how would you know what is high leverage work? You have talked about various tooling projects at Quora which turned out to be duds, but how would you know that beforehand without trying? I guess the same applies to your book...
- edmondlau 9y agoAwesome, I'm happy you enjoyed it! In some sense, it might actually be easier to tell at a startup because what matters at a startup is growth. That can be growth of revenue (if you already have a product to sell) or growth of users (if you need traffic first to sell, e.g. Quora). The highest-leverage work would then be the things that most directly lead to that growth. Sometimes, this will require talking with product managers or salespeople or users to understand what the biggest accelerators or roadblocks would be. So, for example, at Quip, I looked at data on how the product spread within teams and organizations, developed engagement metrics around it, and then built features to move those metrics. Working on some projects that end up failing is perfectly normal. What's important is to front-load as much of the risk as possible and to be explicit about the hypotheses required to make a project successful so that you can validate them early and, if necessary, change course. That's where some of the projects we worked on at Quora failed (e.g. topic groups, an infrastructure rewrite) -- we let ourselves be overly confident about what we knew and didn't invest the time to sanity check our hypotheses. For my book, validation played a huge role. Even before I started writing my book, I had written engineering-related answers on Quora for over two years and started to get a sense of what resonated with readers. That helped me build confidence that there would be demand for something in this space. Continued feedback and reviews during the writing process built on that confidence more.
- eej71 9y agoWould be interesting to hear more about the projects that failed. How big of a rewrite was it? How long did it take before the group or a manager recognized that the project was failing? How did the group deal with the failure in the social sense?
- inetknght 9y ago> Optimize for Learning An idealist, for sure... > Prioritize learning over profitability. ... but that doesn't sound very pragmatic. I love learning. My boss loves making the company profitable. Coming to a happy medium is where a lot of learning can happen if both of you let it. If one party's not on board, then it's going to end up being a problem.
- whistlerbrk 9y agoI really liked this post, and I'm again saddened to see 'take downs' in the comments (not solely addressing you). The author said "prioritize" not to sacrifice profitability in order to learn. By prioritizing learning you may very well increase profitability over the long term. See the recent Google Maps is a moat post.
- brucephillips 9y agoChallenging an idea is not a "take down".
- whistlerbrk 9y agoAt the time I posted there were 3 top level comments, all negative on the post.
- crispyambulance 9y ago> ... If one party's not on board, then it's going to end up being a problem. Yep, that's why he says prominently: "Change jobs if you have to." Idealism, IMHO, acts as a motivator and helps folks get through the obstacles that inevitably block progress.
- romanovcode 9y ago> Prioritize learning over profitability. This is idiotic advice. You can learn in big "boring" corps just like you can in hot startups but at the end of the day a job is about money.
- IronKettle 9y agoThis is totally an incomplete thought, and I'm not trying to be down on this author in particular: It's interesting to see a lot of management thoughts and colloquialisms slowly creep into the "other side" of software development (i.e. the actual developers) and become fairly well-tolerated. We still make fun of phrases like "paradigm" or "synergy", but we're all mostly on-board with phrases like "own <x>" or "growth mindset". You can see the author using the word "leverage" here repeatedly in the same way that we often chide managers for using words like "synergy". Interestingly the conversation around "effective engineers" has also shifted to really de-emphasize that technical ability - the best engineer is a good teammate, first and foremost (and I think a not-so-subtle implication also is that a good engineer is mostly extroverted as well). In the past decade or so, it seems like the "effective engineer" has become one who straddles that line between management and technical ability. I don't really have an opinion on this yet (I think there's good and bad, as with most things), but it's just fascinating to watch.
- pm90 9y agoI think you're being a little too pessimistic, although I do see where you're coming from. Technical jargon and vocabulary aren't created out of thin air: they are meant to efficiently and effectively convey certain facts and behaviors. Sometimes (perhaps many times?) there are co-opted and misused by certain people (many times managers, since they're further away from actual coding). The thing about engineer being a good teammate: I don't think it is about extroversion as much as realizing that modern software systems are very non-monolithic and thus require cooperation among many different services to work effectively. This means that the days when a person could write the entire thing by himself/herself is over, and a lot more co-operation is required among engineers to design and build effective systems. That cooperation requires a certain amount of communication skills (apart from stellar technical skills), but it doesn't mean that you have to be an extrovert.
- meddlepal 9y agoI think often lost from the whole introversion vs extroversion debate is that: 1. It's not a binary. It's a bell curve where many people fit near the middle and some are extreme outliers in either direction. I know personally that I am an introvert, but I confuse a lot of proclaimed extroverts who mistake me for being extroverted because I have a fairly gregarious and willing to try anything once personality. 2. Introvert / extrovert really has nothing to do with communication skills except that introverts appear to be bad at verbal communication usually because that skill isn't as practiced as extroverts. But good verbal communication is totally a developable skill rather than something innate to a person.
- yanilkr 9y agoThis is effective nonsense. Based on my personal experience, effective engineers I know do not follow a formula like this. This looks like a list of how to be teacher’s pet. A superficial need to be praised by others as effective only takes to “mediocre”.
- eitland 9y agoAlso it comes off as a way to build a career at the companys expense.
- ashwinaj 9y agoYou're forgetting the fact that the company is also building it's "career" off your's too. Don't believe me? Any invention that you have created at your workplace (patents etc.) is always held by your company, not you.
- eitland 9y agoThat's the deal though isn't it? They pay me real money - I do real work for them.
- ashwinaj 9y agoSo you're okay with the fact that they are kinda-sorta exploiting you (by not including you as a co-patent holder) but have reservations on employees utilizing company resources to further their career? That seems like a really raw deal to me. You might argue that you are "paid" to do this; not really, you can just coast on 9-5 and draw the same (or in the same ballpark) paycheck as someone who is busting his behind to invent something. Also when there is downsizing you might think that contributions is the only thing that matters, but it is demonstrably not (I'm speaking about regular companies not a small startup).
- barrkel 9y agoYou expend labour; they build capital. The capital you build produces returns long into the future, but you don't own any of that future income stream. Sooner or later, your sharpness and skills will decline, and your labour will be relatively worthless. The capital you helped build will continue to be valuable (presuming you did a good job). It's a poor deal if you're in a competitive market where there's another schmuck willing to do your job for just as cheap as you do it. But if you have pricing power, you'd be a complete fool not to either charge substantially more, or demand some ownership.
- ghrifter 9y agoWow yet another Github Markdown README about how to be good at X or a list of things of X
- nicodjimenez 9y agowho knew that Github would be used for "10 ways to do x" type of articles
- 0xdeadbeefbabe 9y agoPeople who applied the lessons of 10 ways to read the future.
- 0xdeadbeefbabe 9y agoWhat's so surprising about Markdown?
- jotux 9y agoIt's just someone's notes from reading a book.
- nicodjimenez 9y agoPretty good overview, although I was aghast when I saw that The Mythical Man Month was missing from the book list. The Effective Executive is also a timeless classic that's useful to anyone who manages anything.
- snoman 9y agoIt references the primary concept, and it also looks like much of the information from MMM is already distilled into this - which is not hard to do; MMM is a bit verbose if I recall correctly.
- apthnz 9y agoOn the "read code written by brilliant engineers" point, as someone just starting to learn Python, where would I find some?
- m3kw9 9y agoMaybe find a very well received project on GitHub and check out the author and see some of his code
- nemild 9y agoLots of different ways: - Find a function call you're making in a library and see how it works - Look through the top python libraries (see https://github.com/vinta/awesome-python https://github.com/vinta/awesome-python ) and pick a few of the simpler ones to flip through For reading code, some things that can be useful: - Flip through test suite and get tests running; then break some tests to see what's happening - Diagram out code on a piece of paper (file structure, data structure, stack trace for a popular call) - Discuss implementation with friends - For certain files, it's often valuable to rewrite yourself
- viraptor 9y agoAnything written by Kenneth Reitz https://github.com/kennethreitz https://github.com/kennethreitz
- edmondlau 9y agoIf there are engineers you highly respect on your team, their code is a great place to start. Otherwise, many top tech companies now open source software that they've written internally, oftentimes with their own websites. And there is also a growing trend for them to actually maintain the software they open source as opposed to just throwing it over the fence. Think of companies that have a strong engineering brand, and then just search for what open source software they're released. Pick whatever seems most aligned with your interests. Some examples: Google: https://opensource.google.com/projects/list/featured?language=python https://opensource.google.com/projects/list/featured?languag... Facebook: https://code.facebook.com/projects/#backend https://code.facebook.com/projects/#backend Stripe: https://stripe.com/open-source https://stripe.com/open-source Airbnb: http://airbnb.io/projects/ http://airbnb.io/projects/
- deleted 9y ago[deleted]
- vinceguidry 9y agoDoes this violate copyright? It appears to be a clear derivative work. I ask because this is something I'd love to see more of, but I'd be afraid of doing myself because I don't want to get a C&D.
- derekja 9y agoIs a book review a derivative work? The author of the book is in here politely answering questions rather than crying "you copied!" so the nice summary of his ideas must feel ok to him...
- dudul 9y agoI don't think the original notes do, but there is this comment by the owner of the gist: "FWIW: I didn't produce the content present here. I've just copy-pasted it from somewhere over the Internet, but I cannot remember exactly the original source. I was also not able to find the author's name, so I cannot give him/her the proper credit." How convenient? It was copy/pasted from somewhere, but oops, can't remember where or who wrote it, oh well, I'll just put it under my name :)
- makecheck 9y agoOn the topic of reading code “written by brilliant engineers”… Code bases can be so large that you might find brilliantly-written things intermixed with things that are not brilliant (and some of those parts may even have been added by the brilliant engineer on an off day). Therefore, it’s risky to just absorb an entire blob as Good without also understanding its history. An interesting side effect of languages/ecosystems with single coding styles enforced: bad changes to good code no longer stick out like a sore thumb! In my experience, developers with the discipline to write great code also typically write it in a consistently structured way, and it’s kind of useful that “warts” added by others over time usually won’t follow the structure/style and those warts will be easier to find and scrutinize.
- xstartup 9y agoPeople often don't realise the person who improved the codebase within a short span of time had years of experience in the domain. I know a class of engineers who are solving the EXACT same problem using the EXACT same method from from company to company. To someone from outside, it might appear like they are job hopping looking at their average time spent at a company.
- anichale 9y ago> coding styles enforced: bad changes to good code no longer stick out like a sore thumb! I can see the benefit of being able to identify smelly code immediately from poor code structure. However, I think that coding styles enforce consistency between good programmers who maintain their own coding style. A reviewer should be able to discern code quality - even with compliant code style - by how quickly it is to comprehend.
- Terr_ 9y agoThe effect can't last long though: The long-surviving codebase becomes such a mix of styles that it's more noise than signal, and even the good code appears as just another local inconsistency.
- beager 9y agoSomewhat unrelated, it would be great to have a Medium-style highlight feature for codebases, where you could onboard developers toward excellent practice by highlighting good code in a repository that consists of various levels of code.
- bharatmeda 9y agoI used to follow Edmond's detailed posts on Quora and that led me to buy his book. I am yet to complete but like it so far.
- bsder 9y ago> 80% of the impact comes from 20% of the work. This simply has no basis in reality nor research and it pains me to see it propagated. The old VLSI design koan is: "The first 90% of the project takes 90% of the schedule. The last 10% of the project also takes 90% of the schedule. 90% of the engineering occurs in the last 10% of the project."
- joshuamorton 9y agoYes it does. The 80/20 rule cleanly fits an exponential distribution. The assumption is then that the work to implement any given feature in a project follows an exponential , and this appears to hold reasonably true in practice.
- bsder 9y agoAll you did was move the question--why does this thing fit an exponential distribution? The birth project of agile--the Chrysler Comprehensive Compensation project--should have been a wonderful example of the 80/20 rule. They implemented the most important chunks of the project and got about 80% of the cases correct--totally awesome. Except--it wasn't. The value of the project was in handling all of the exceptional cases. And those cases started consuming VAST quantities of resource. 80/20 only works when you can interchangeably wipe out tasks without affecting the result. Most engineering is NOT like that. Analyzing the soil may not take very long when building a bridge, but you can't skip it.
- joshuamorton 9y agoAs far as I can see, what you described perfectly fits the 80/20 rule.
- noway421 9y agoThe exact proportion might differ and never is that, but the concept is conserved.
- valuearb 9y agohttp://www.crn.com/news/security/18821726/microsofts-ceo-80-20-rule-applies-to-bugs-not-just-features.htm http://www.crn.com/news/security/18821726/microsofts-ceo-80-... "About 20 percent of the bugs causes 80 percent of all errors, and--this is stunning to me--1 percent of bugs caused half of all errors."
- Yokohiii 9y ago> Reduce Operational Complexity If I hook everything into slack I have a simple interface that can cover and reflect all my needs!
- foopod 9y agoHang on.. What should I do first? + The most valuable thing? + The riskiest thing? + The simple thing?
- jrs235 9y agoYou should work first on the riskiest part of the [guesstimated] most valuable thing. Edit: [guesstimated]
- edmondlau 9y agoThey're orthogonal dimensions. My fault that this isn't clearer. Here's a simpler ordering of operations: 1. Start with the most valuable, highest-leverage thing you want to focus on. 2. Figure out what the riskiest bit of that thing is. Focus on de-risking it. 3. When you're de-risking (or more generally whenever you're just doing that thing), start simple. Beware of adding in unnecessary complexity.
- nostrademons 9y ago"Opportunity cost of working on wrong ideas can set back growth by years." I feel like this is spoken by someone who hasn't seen more than one technology cycle come and go. What I've observed - having started my career back in the Java-will-eat-the-desktop days and then adapted through webapps, big data, mobile, and now AI - is that the people who are best positioned to capitalize on an emerging technology wave are the ones who started working on it before anyone realized it was important, just because it was interesting to them. They're the ones who write the papers and software that everyone else evangelizes, and then get multi-million-$ signing bonuses or stock grants (or billions of dollars worth of cryptocurrency) when corporate interests catch on that this is a new technology wave. But at the time they start working on the idea, it's both useless and unlikely to work. You can make a decent living always being on the look out for a new technology wave and jumping on it as soon as it's clear that it's hot. I spent much of my 20s doing that, and made enough money doing so that I can take it a bit easier now. But it's exhausting, and you'll never be the one actually driving change. It's also usually not clear what's the "wrong idea" except in retrospect. DropBox is rsync with cloud storage and some pretty slick desktop app integration, done at a time when everybody thought that desktop apps were dead and Drew's Windows hacking skills were old news. But it's that familiarity with old technology that put him in a place to realize that new technology could make the old technology dramatically more useful, to the tune of a $10B company.
- brucephillips 9y ago"useless and unlikely to work" -/-> wrong
- nostrademons 9y agoBut without the benefit of hindsight, how do you tell the difference? When I look at some of the giant wins of the last major tech wave, often times the key factors in their success were external events that happened after the formation of the company. AirBnB benefitted massively from the housing bubble & financial crisis (3 years after formation), which created a large class of people who were desperate for income and whose primary residence was their primary income-producing asset. Uber had to try the idea multiple times before cell phone batteries became good enough to run navigation continuously in the car (2 years after formation), and took off because of the publicity of getting sued by San Francisco. WhatsApp took off after the addition of push notifications to iOS (~18 months after formation) made it feasible to use as a messenger rather than just a status update. All of these companies certainly did things to influence their success, in particular having a product on the market at the time the market changed to take advantage of the product. But for most of them the product was actually wrong in the sense that it was a complete failure in the market until that market changed. Brian Chesky's fond of calling AirBnB "the worst startup idea that actually worked". It's like the formula for success = preparedness + luck. This cribsheet does a good job at preparedness, but you have to acknowledge the role of luck if you want to actually capitalize on that preparedness, and being afraid to work on the wrong ideas will often shut you out of ideas that require some luck to work.
- throwme_1980 9y agocollection of recycled rubbish from everywhere, get things done fast, get paid, live a rich a life
- Blazespinnaker 9y agoLot of very selfish anti team ideas here. Shipping requires doing grunt work. That’s the person I want to work with and that’s the person I think is valuable.
- valuearb 9y agoName the things in the list that are anti-team or selfish, or avoid grunt-work. Being more productive would seem to benefit your team, no?
- sethammons 9y agoPerhaps I misread the post. I thought there were several points about putting your team first. I've found that this can mean doing grunt work or it can mean reducing siloed information by having them do grunt work. This is to say that helping the team, helping grow yourself, and helping to ship product are not mutually exclusive from each other.
- henrik_w 9y agoReally great book! The things that stood out for me: - Optimize for learning - Invest in time-saving tools - Shorten the debugging loop - Don’t sprint in the middle of a marathon - Recovery over prevention - Automate mechanics, not decision making - Make batch processes idempotent We read it in the book club at work a year ago, and I wrote a longer review of it here: https://henrikwarne.com/2017/01/15/book-review-the-effective-engineer/ https://henrikwarne.com/2017/01/15/book-review-the-effective...
- edmondlau 9y agoAwesome! Thanks for adding your notes to the discussion.
- golemiprague 9y agoToo many rules and things to follow, nobody in their right mind can do that, certainly not successful people. Need a list of maximum five thumb rules to follow, otherwise it is ineffective.
- andendau 9y agoI love all of Edmond Lau's stuff. I accidentally found one of his Google talks while trying to find something for my team when we started on fixing a massively underscaled tech stack. I bought the book read it and shared it with a few other engineers. Super valuable and a lesson I keep trying to teach to our organization is how worth it is to build better tooling.
- edmondlau 9y agoThank you! It means a lot to me hear its impact on you -- stories from readers are what keep me excited about doing this work.
- deleted 9y ago[deleted]
- swanson 9y agoMy most useful insight/takeaway from the book was about leverage and what activities you choose to do as you progress in your career: in six months you could ship 1x engineers worth of output (or maybe 2x or 3x if you are really great) -- or you could help hire and onboard 10 engineers and create 10x worth of output. Thinking more strategically about the most effective way to spend my own time and energy was easily worth the nominal cost of the book.
- partycoder 9y agoI think that the understanding of software engineering as an occupation is a bit oversimplified. While there are good chances most people will be working on web or mobile applications, there's much more going on. Compilers, cryptography, compression, operating systems, graphics, simulation, data retrieval, distributed systems, etc. To that you need to add machine learning and AI. I think it is hard to come up with a unified set of tactics/strategy to be an effective engineer at each part of this occupational spectrum. For example, some engineers, while learning, try to specialize themselves in an area while others try to become generalists. Both approaches can be valid depending on the role. Some engineers focus on applied science while others on theoretical science, some others just on empirical knowledge, processes and techniques. Again, the impact of this decision will largely depend on the role. Then, prioritization is a double edged sword. To do what is perceived as important is intuitively the right thing to do. But during learning it is harder to recognize what is important. This is how many people end up neglecting valuable learning.
- jyriand 9y agoIt's strange how obsessed software engineers are about methods of working. At a surface level it's just: sit down and write the code. But actually there are thousands of programming languages you can choose from; there are build tools, code standards, testing(to TDD or not to TDD) and mental models you have to wrap your head around before you even can start to consider yourself a decent programmer. It's fascinating, but at the same time I wish it was all simpler. I wonder if there are other occupations in the world that are so much focused on tools, paradigms and methodology as software engineering(investing and trading come in mind. And it's interesting that these notes use so much investing and business lingo).
- nine_k 9y agoIf it was simpler, it wont command such wages, and would be automated out sooner. Humans' current advantage is the ability to tackle complexity and uncertainty.
- thundergolfer 9y agoI think the comment you're replying to is implicitly making the point that some of the complexity is manufactured and needless.
- davidjnelson 9y agoAnother way to look at it is automation will free people up to solve more important problems.
- nine_k 9y agoYes, those who'll happen to be capable of that by the time.
- narag 9y agoIt's strange how obsessed software engineers are about methods of working. So you are surprised that a bunch of people whose work is to create mental models and automate them are obsessed with creating mental models of their own work and automate it? It's fascinating, but at the same time I wish it was all simpler. Actually it is, IMHO. A lot of the parafernalia around the job is useless obsession indeed. We're just that way for good or bad.
- rondysousa 9y ago(From the gist's account owner) FWIW: I didn't produce the content present on this gist. I've just copy-pasted it from somewhere over the Internet, but I cannot remember exactly the original source. I was also not able to find the author's name, so I cannot give him/her the proper credit.
- lazyasciiart 9y agoThis seems like something worth mentioning on the gist.
- yters 9y agoNext big thing is finding out the non-algorithmic capabilities of the human mind, and how to best utilize human in the loop.
- noway421 9y agoThe website is broken (sign up link not working) with ublock on. This is really unacceptable for a landing page.
- bra-ket 9y agoA combination of software engineering and domain expertise makes for a really effective engineer. As an example - if you work as an software engineer in finance learn about a few particular financial products at the same level or better than your users, get a masters in finance, applied math, accounting and whatnot. This has the added benefit of staying relevant in the market when you age, as software engineering becomes increasingly commoditized.
- rb1 9y agoNot one mention of using a spellchecker, surely that's high leverage: quick and easy, increases the quality of your output.
- jodrellblank 9y agosurely commenting on the spelling of something you understand is not a high priority, high leverage, effective use of your time?
- KKKKkkkk1 9y agoI work on a team in which a few people adopted the strategy of doing 20% of the work for 80% of the impact. That leaves the rest of us doing the remaining 80%. If the people doing most of the work are not getting the credit for it, how is it going to play out in the long run?
- afarrell 9y agoWhy does that 80% need to be done?
- jodrellblank 9y agoHow else do you get to 100% of the work done?
- afarrell 9y agoWhat I mean is that the number of pieces of work that can be done is some high multiple of the work that you can do. So find the projects that are in the top 20% of impact by starting with “why does this need to happen?” Of course if someone is only doing 20% of any given piece of work (say, never writing tests or refactoring or doing code review), then yea, that is a big problem.
- scrpn 9y agoI pwrsonally found that Refactoring often and unit testing don't play nicely together. A huge refactoring lead to a lot of rewriting of unit tests since they weren't compiling anymore. I was able to reuse test logic though.
- kapad 9y agoI just skimmed the article, but it seemed a lot like a rip off of "The Pragmatic Programmer" to me.
- jodrellblank 9y agoHigh leverage, compounding learning, exponential growth, high impact work, high priority, fast paced, focus on value, larger time blocks, ever deeper flow, prioritization for higher leverage, faster deployment, faster tools, shorter iterations, skyrocketing productivity, scale impact beyond confines, impact scaling, time saving, shorter loops, faster tests, shorter compiles, mastered tools... Does any of this seem a bit Shepard Tones to anyone else? https://www.youtube.com/watch?v=OsBanpBQj0k https://www.youtube.com/watch?v=OsBanpBQj0k (ever-ascending-tones audio illusion)