20 ms·
Rules of thumb for a 1x developer
- Traster 7y ago>Internal deadline: This is a target internal to the team that will not affect anybody outside of the team. Never in my life have I witnessed an internal deadline. If it came out of your mouth and someone heard it, well done, you've got yourself a soft-deadline. If you haven't said it out loud, it's an expected completion date, not a deadline.
- wirrbel 7y agoThis document provides, especially towards the end, some valuable opinions. The technology-advice is really bland or maybe overfitted to specific use cases.
- baylessj 7y agoAgreed. The general advice here is really useful. I am not clear on the benefit of the discussion on programming languages and specific tech though, that section seemed like an out of place admission of a lack of knowledge in an article that contained many useful tips.
- stefanchrobot 7y agoQuite surprising take on the languages. > When to use Python or Ruby > Python and Ruby seem to me to be pretty similar in that they’re scripting languages and dynamically typed and seemed like the greatest thing in the 00’s. You use them when speed is more important than legibility or debugging. I'd say you pick them when productivity and time to market is important. I personally find dynamic languages far more legible (unless you're doing metaprogramming-heavy stuff). > Haskell or Erlang maybe I would use if I were doing something that required a very elegant or mathematical functional approach without a lot of business logic. I think it's a mistake to throw these two into the same bag. I'd say Haskell is functional and comes from academia. Erlang is concurrent (with functional aspects) and comes from engineering background. You'd want to pick Erlang if you want to build scalable backend systems. > my guidelines for JS are: > Try to push as much logic as possible to the server. If the front end weren’t super complex, I would consider something like Phoenix instead which actually pushes everything to the server. Phoenix is a web framework for Elixir and Elixir is a Ruby-like syntax on top of the amazing Erlang VM, so this kind of contradicts the suggestion above. Either way, Phoenix LiveView might be a game changer when it's applicable and for people who don't find the whole JS thing very exciting.
- twic 7y ago> I personally find dynamic languages far more legible Maybe you're a 2xer though.
- mozey 7y ago"Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?" -Brian Kernighan Over time I've come to appreciate this sentiment. Banging out clever code super fast isn't that important... Spending some time up front thinking about types and architecture pays off in the long run. Especially for server side code. Far from being annoying, error messages from the compiler make me feel warm and fuzzy inside. On the other hand, for quickly prototyping user interfaces, some "stream of consciousness" Javascript might just be good enough.
- joelbluminator 7y agoSo every dynamic code is a "super fast" banged out clever code, and every static code is a well thought out architectural masterpiece right? Could you be more biased?
- gregoryl 7y agoDo you have something better to contribute? I'd like to hear it, rather than just hearing you being a bit upset :)
- AlexMoffat 7y agoObviously someone has hurt you in the past. Do you need to talk about it?
- wonderwonder 7y agoI very much like this quote. Used to work with a team of contractors out of Eastern Europe. They were exceptional programmers but wrote code using obscure language features and in such an odd way that now that they are gone, every time someone has to debug some of their code its a very frustrating process. There are definitely times to use 'clever' coding practices but nine times out of 10, just write it simply and focus on readability. Your team will thank you and you will thank yourself a couple years down the road.
- troelsSteegin 7y agoMy takeaway from this: 1) don't overthink a problem 2) observe norms 3) meet expectations. In other words, simply be reliable.
- MaxBarraclough 7y agoThis is poorly titled. A '1x developer' is by definition an average developer. The page is mostly listing basic knowledge that any developer, even a very junior one, should already have. If you aren't aware of the relative strengths and weaknesses of Java, C, and Python, you aren't a 1x developer, you're a trainee. Anyone know of any better articles truly targeted at '1x' developers? (This isn't snark, it's an invitation.)
- laumars 7y agoThe 1x / 10x memes need to die in my opinion.
- MaxBarraclough 7y agoAgreed. 1x should be a synonym for ordinary, but as we're seeing here, its meaning had drifted to refer to especially unskilled developers.
- deleted 7y ago[deleted]
- micael_dias 7y agoSo a frontend developer is a perpetual trainee in your opinion?
- MaxBarraclough 7y agoI'm talking about very basic background knowledge of general software engineering. Yes, a professional frontend developer should have at least an elementary understanding of the differences between the major programming languages. An expert frontend developer will necessarily be competent in many languages, and might be competent to, for instance, contribute code to the Qt project. I can see the value in the Project Management section of the article, as that's the sort of 'soft' topic that will be new to, say, a fresh graduate. If someone doesn't know the first thing about programming languages, though, they're a long way from the standard of a developer.
- pjc50 7y agoThis is cynical in a well-written way that matches my prejudices. I like it.
- paulcole 7y agoDidn’t realize that it was already time for the annual HN slogan contest.
- slim 7y agoyou win
- altonzheng 7y agoAlmost spit out my coffee.
- bearjaws 7y agoI hate the notion of "10x developer". It focuses on hiring the best person, rather than firing individuals who undermine the team. The reality is, there are some 1x developers, and some .5x developers. Even worse though are the -1x developers. So many times I see a corporate culture of firing = bad, so lets just try to find someone who is a "10x", when really all you need is to remove the people who cause more work for the organization. Its our job as managers to accept that we hired someone who is ineffective, damaging the team and that OUR hiring process failed to catch that. Then to deal with them (training, firing) and iterate on the hiring process to prevent the issue going forward.
- ses1984 7y agoI knew two 10x developers at my previous job. One of them was humble and a great mentor and elevated everyone around him. One was a grump who made everyone around him feel stupid. Imo toxicity is independent from productivity.
- justaguyhere 7y agoSame experience. I learned quite a bit simply by sitting next to an exceptionally good and exceptionally nice developer who was at least a decade older than the rest of the team and enjoyed helping others. He rarely got stressed even in crunch times and that put rest of the team at ease.
- abyssin 7y agoThe simple idea of this being possible, and picturing the scene in my head, gave me a lot of hope. I'm tired of the atmosphere of fear in the office, and I'm tired of how I participate in it.
- joelbluminator 7y agoWe need to look at the role more broadly, being a developer isn't just churning out code. A lot of young talented guys just follow their passion and hack away abstraction after abstraction instead of trying to see what the product really needs. So you could say they're amazingly productive, or you could say they actually provided very little value. And a toxic wreck can't be productive by definition; if you demoralise everyone around you reduce productivity! The fact some people can get away with is a bug in hiring.
- onion2k 7y agoThis article really puts me off working for Amazon.
- rb808 7y agoThe fact he did all this while at Amazon surely means the WLB is better than reputation?
- rezeroed 7y agoI only read the start. I'm not sure what I make of someone going from zero to Amazon. Is that normal?
- onion2k 7y agoAmazon recruit huge numbers of graduates, so obviously that's a yes. I think their graduate roles pay quite well too. But if this article is to be believed, they also do things like using 15 different languages on the tech stack (16 to choose from minus PHP because it's banned) and give you the idea that estimates are worthless. If your workplace is doing things like that it's a very bad sign in my opinion.
- rezeroed 7y agoI expected those graduates would have tech degrees, rather than "I picked up programming a few years out of college".
- akhilcacharya 7y ago> they also do things like using 15 different languages on the tech stack Teams have a lot of flexibility to choose the best tool for the job. It's not surprising that you'd have those options if you're tackling everything from UAV avionics to distributed systems to facial recognition.
- onion2k 7y agoIt's not surprising that you'd have those options if you're tackling everything from UAV avionics to distributed systems to facial recognition. Amazon as a company might use them all, but no Amazon team should be choosing between them all (well, they do in so far as you can immediately rule out lots of unsuitable languages for most projects). This guy has worked on two teams so far and appears to be suggesting he's made choices between 15 languages already. That either means the teams he's been on have used wild stacks with endless choice (a reason not to work there) or that he's not correct about the extent of choice he had (and if someone has 5 years at a company and they still don't know that's another reason not to work there).
- dave_aiello 7y agoThink of this essay as a barbell, in the investment sense of the word. The beginning and the end of it have some really good insights that can be generalized to a lot of technical / development work. The middle of the essay (Rules 4-16) are useful observations from Mickey's experience. (I don't know him; I am just trying to relate this paragraph of comments to his experience more explicitly.) This is not a bad thing. If you are a 1x developer yourself who is looking to improve, I think you want to read treatises like this and try to understand your fellow developer's perspective. Only truly brilliant developers can give generalized language and database platform advice. The other people who give valuable advice at this level are not developers, they are technology evangelists who have a track record of success helping real developers.
- vsareto 7y ago>One great example of this is the debacle of the Amazon internal wiki migration. Back in 2015, the Amazon InfoSec team banned PHP at the company. Oof. To be fair, Java is probably way easier to code review.
- Filligree 7y agoMuch depends on the Java. Having spent a lot of time on personal projects using the language, it doesn't deserve its reputation -- Java may 'require' an IDE to avoid spending too much time on boilerplate, but modern Java is a good language and the programming experience once you do have that IDE is one of the best, most effective I know. At the same time, it's absolutely possible for codebases to become "enterprisey" to the point where even the tiniest change takes weeks. Some of the libraries out there use absolutely horrifying patterns. If you're just coding for yourself, you can avoid those. In a company maybe not so much, and even though the company would be better off avoiding them, maybe they have old code remaining from when such things were considered good.
- The_Colonel 7y agoPeople really, really overrate the importance of a language. Java as a language is quite decent, but definitely not great. What makes it great is everything around it - from second to none JVM, range of state-of-the-art developer tools to the best library ecosystem.
- JackFr 7y agoI just had an coding interview where the interviewer was guiding me to create a class called “ResponseBuilderVisitorBuilder” Run away!!! (And I like Java!)
- jimbokun 7y agoAs long as you can avoid Spring, Java is a great development platform!
- AndrewUnmuted 7y agoI remember thinking that the internal wiki at anzn was one of it's best workplace features. This was something used by just about every team and rarely needed intervention from internal developers to operate smoothly. This was prior to the migration though. I can't imagine how much upheaval there was resulting from the migration, language considerations aside. This is probably one moment where tech concerns should have taken a back seat to company stability.
- noad 7y agoI used to get called a 10x developer, I was also called a rockstar and a ninja and a 100x dev and every other compliment that was hip. Then I hit 30. That type of talk stopped. Then I hit 40. Now I will not be considered for any entry level, mid level, or senior level software dev job anywhere in the United States, despite being very desperate and willing to relocate for anything. Doesn't matter. Too old. I'm supposed to be doing something else by now. Make a backup plan now.
- pmx 7y ago> despite being very desperate Could this be why? Desperation has a way of putting people off?
- goodpoint 7y agoWhy all the downvotes? Is HN only for the cool kids?
- jki275 7y agoI know plenty of devs who are 40+ and still writing code and getting paid well to do it. In fact I worked with a consultant who was over 60 not too long ago. I am almost certain there is something else going on here other than your age. In fact, I've never once been asked my age in an interview, and I'm a couple of years into my second career doing this after I retired from my first.
- swilliamsio 7y agoEven if the interviewers were concerned about your age, you'd never be asked how old you were in an interview. That's grounds for a discriminatory law suit basically anywhere in the world.
- LargeWu 7y agoOne can easily infer age based on career experience, college graduation date, etc.
- cellularmitosis 7y ago"To replace out MediaWiki with a Java-based alternative (XWiki) ended up taking a total fo 24 dev-years over 4+ calendar years for the team, not counting the interruptions to pretty much every other team at Amazon as their pages were getting constantly migrated and un-migrated" I would love to hear more about this. I'm guessing that's a cost of at least $4M? How was this approved? How did they allow it to continue for four years?
- stu2010 7y agoAmazon's total all-in cost per dev is almost certainly >$300k per year, so more like >$7 million if that's an accurate number. As far as how it gets approved, that's not enough money to really register at Amazon's scale. I've seen waste similar to that at companies much, much smaller than Amazon that goes entirely un-noticed.
- theli0nheart 7y ago> As far as how it gets approved, that's not enough money to really register at Amazon's scale. I've seen waste similar to that at companies much, much smaller than Amazon that goes entirely un-noticed. Maybe I'm being dense, but this still doesn't register for me. If 4+ calendar years of work for a single team continues with no noticeable progress, then there's an organizational issue, no matter the size of the company.
- WJW 7y agoOf course there is, but that's not the point. Every large organisation has organisational issues and nobody in the history of humanity has found a way of preventing them yet. The only thing you can do when the group sizes get large is to try and keep the problem under control relative to how bad it is at other large companies.
- theli0nheart 7y agoI'm lost; what specifically is not the point? As far as I could tell, the "reason" given by the OP for this waste was attributed to Amazon's scale. Could you explain how company size and broken corporate structure are correlated? Or explain why 20+ person-years of engineering time wasted isn't a symptom of broken corporate structure?
- jordanpg 7y ago> That’s all that Agile means to me. This is the most concise, honest summary of "agile" I've ever come across. Well put. The amount of person-hours spent bikeshedding about various sundry "agile" procedural details is absolutely breathtaking. A perpetual, real-life Dilbert punchline taken seriously by armies of *Managers.
- engrsrce 7y agoWell that's pretty naive. I've worked with some pretty good teams that wouldn't work any other way. I suspect you've only worked at places that abused agile as described here... https://ronjeffries.com/articles/language-of-hatred/ https://ronjeffries.com/articles/language-of-hatred/
- jordanpg 7y agoNo, I've worked in places where it works just fine. The point is that, at the end of the day, it boils down elaborate processes to break things up into two-week chunks of work. That's it. That's the bit I thought was a concise, excellent summary. Sometimes, for certain flavors of apps and tech and teams, that model works splendidly. Sometimes, it is silly administrative window dressing that is completely disconnected from the reality of what the team is doing. In my experience, it's usually the latter -- and the teams work just fine _in spite_ of the fact that everyone is pretending they are doing "scrum" or "agile". I'd say what is naive is the belief that such a closely scripted, narrowly defined workflow is a one-sized-fits-all solution to optimizing teams under all circumstances and contexts.
- romanows 7y agoAgile is the opposite of "closely scripted, narrowly defined workflow is a one-sized-fits-all solution to optimizing teams under all circumstances and contexts." You're thinking more of Scrum?
- engrsrce 7y ago"Elaborate processes" and "closely scripted, narrowly defined workflow" aren't adjectives I'd ever use for agile done well. And I've been doing it since we were allowed to call it eXtreme Programming. There's lots of "Dark Scrum" out there. Sounds like those are your experiences. They're not mine.
- nsfyn55 7y agoI don't think the author is a 1x programmer. He has learned the first secret of 10x programming. It's not about being a genius programmer. Its about being an efficiency expert and a problem solver. Soft skills play an outsized role here. I have seen immensely talented developers with hard skills for days manage to deliver nothing over long periods of time. Learning that rules are guidelines not religious artifacts handed to us via burning bush is a big step. I can't tell you how many programmers I've seen hobble their own productivity by having overly aggressive code reviews, strict style guidelines, or requiring more testing than is necessary. Being an outstanding software engineer is 99% knowing when to tenaciously stand your ground("storing state that way will not allow us to scale horizontally. It will save us a few hours now but in order to achieve our larger objectives will take 1000x the effort to unwind; we have to find another way") and when exerting control isn't helping("You can't put this simple, but incredibly important, time sensitive piece of software into production until it has been reviewed by our 6 committees, is re-written to use the companies globally enforced, yet questionably valuable style guideline, and has 113% code coverage")
- goalieca 7y agoHe's working at amazon so perhaps their talent pool is a little better than the average non-coastal company.
- jusssi 7y ago> #1 Rules are good Only when combined with "Rules are made to be broken". Nothing is worse than taking an arbitrary set of rules and turning it into a cult religion. Other than that and some of the programming language rules (such an opinionated topic) a rare, level headed treatment. Bookmarked for future quotation.
- deweller 7y ago> PHP is banned at Amazon due to security reasons, but its successor, Hack, runs a lot of.. Just to be clear, Hack is not PHP's successor. Hack is a fork of PHP developed by Facebook. Hack will not overtake PHP any time soon. PHP has had security issues in the past. Sure you can do stupid things with it if you want, but modern PHP is security conscious out of the box. Frameworks like Laravel make great default choices about security concerns.
- kumarvvr 7y agoA small question. Is PHP still a preferred platform for any sort of complex web development? I have never even looked at the php site or docs, but I am curious. In this day and age, is there a subset of Apps that PHP is suited for?
- The_Colonel 7y agoTraditional (non-SPA) web apps is where PHP is quite strong. Also depends on the team, if you have a PHP team and it's a web project, you probably want to use PHP.
- bzzzt 7y agoThat's the problem right? Nobody starts new non-SPA web app projects anymore.
- kumarvvr 7y agoThere are many new projects that involve Django / Drupal etc. I myself have spent a lot of time weighing in the pro's and cons of SPA vs. Non-SPA for a recent project. It's not like all new projects are SPAs.
- kamarg 7y agoPlenty of companies are building boring new PHP sites on Magento and making money without being SPAs. At least here in the Midwest, I've noticed quite a few non-tech companies moving their SPA sites away from being SPAs because it was the wrong technology choice for what the site does.
- mannykannot 7y agoRule 14: When to Write an End-toEnd Test 4. When your spacecraft needs to get the correct mission elapsed time from the launch vehicle. https://arstechnica.com/science/2020/02/boeing-acknowledges-gaps-in-its-starliner-software-testing/ https://arstechnica.com/science/2020/02/boeing-acknowledges-...
- codesections 7y agoI was very surprised to read > 90%, of what I learn at one job is completely useless for the next one. That has not been my experience at all (and I've had some pretty major job changes, including lawyer -> software developmer). If I had to put a number on it, I'd say more like 50% of what I've learned at each job is transferable. How about everyone else? Closer to 10% or 50%?
- alex4864 7y agoLikewise very surprised! I've found that Software Engineering as a field is great for knowledge transferring between jobs -- the ability to design and reason about systems transcends individual languages and tools. 50% sounds about right to me.
- kemiller2002 7y agoAlmost everything I learn on the job is transferable. I use anything I pick up to build associations with how other things work. If someone is throwing away 90% of what is learned, something is wrong.
- hycaria 7y agoveterinary medicine to software development is around 10% too, maybe less.
- jerf 7y agoI think there's a point of view component. If you think of it is "Today I learned how to use $PROPRIETARY_AMAZON_TOOL to set up a new project which will use $PAT to deploy to a $PROPRIETARY_AMAZON_INTERNAL_CLOUD and sets everything up to $PA_MONITORING and $PA_ALERTING in my... etc. etc. etc., you get the idea, then yes, you will feel like what you "learned" is not transferrable. On the other hand, if you look at it like "Today I learned some best practices for setting up a new industrial-strength projects through the particular manifestation of this tool, learned about setting up monitoring through the particular manifestation of this other tool,", etc. etc., then even though you may have learned via particular local tools, you also learned a lot of stuff that may be useful later. The question is, let's say you did change jobs and had to learn some new set of tools. Will you learn them faster than you learned the first set of tools? Will you find a new perspective on the issues from learning the new set of tools? The answer should generally be yes. This is broadly speaking why I expect a 5-year veteran to pick things up faster than a fresh grad; OK, sure, you've never "used git", but I expect you've used source control somewhere. You may not "know React", but I expect you to have used something similar enough that you just have to learn React qua React and are not also learning about cookies and the basics of the DOM, etc. Pretty much the first professional thing I ever did was writing what we would today call a "static site generator" in a tool called Frontier, in its custom programming language, more or less from scratch. On the one hand, completely useless skill, Frontier has been dead for over a decade and was fairly zombie-ish for a good 5-8 years before that. On the other hand... the HTML basics I learned are still mostly good (I think it's fair to say at this point my frameset tricks & skills are not that useful anymore...), and the general skill of knowing how to write a static site generator is almost even low-level trendy right now, even though I would have to write it in some other language, of course. I dunno what the exact transfer number is. 90% seems high, certainly, but 10% way too low. There's only a small number of tools that are so bad that while working with them, you learn almost nothing about the problem space you are working in because the quirks of the tool completely dominate, and even then I'd submit a lot of it is still attitude.
- maps7 7y agoI'm not sure how I should be reading the article so maybe it's going over my head. > Rule 10: When to make a microservice > I would use a microservice when I have a relatively small and simple chunk of code that needs to run every once in a while. Isn't this wrong? There's no reason a microservice should just run once in a while. It also creates a lot of complexity for a simple chunk of code.
- codingdave 7y agoMost of this article could be ripped to shreds based on its accuracy. But that isn't the point - he has developed a set of rules and guidance that work for your average developer just slinging code in an enterprise. And while yes, almost everything he says is "wrong" if we push the details... I can see that they are all "close enough" to build a workable framework for your basic 9-5 1x dev.
- hamburga 7y ago> almost everything he says is "wrong" if we push the details Author here. Part of the point was to expose my ignorance and get people to rip it to shreds. So have at it if you want. I've actually learned a good amount so far using this method.
- tumetab1 7y agoI think there's a hidden assumption that the author didn't expose. > when I have a relatively small and simple chunk of code that needs to run every once in a while. I think "run every once in a while" actually means stable requirements. I think the number of executions per time is irrelevant. Being stable is the important thing. My theory is that "run every once in a while" is substituting stable requirements because that's what I also see in organizations. What is execute a lot usually has an higher importance for business which also translates to unstable requirements.
- goalieca 7y agoSome might say that you should only write one when you need to scale across servers or teams. These projects where everything is a microservice and a single team manages 30 of them are kind of insane.
- Tade0 7y ago> At first it was pretty simple, but then we got a lot of new frontend requirements and in no time, managing the front-end state was a total nightmare If there's one thing I envy backend developers it's the fact that they don't receive even half the requirement changes the front-end does. But I would refrain from pushing as much logic to the server as possible - it's never the better experience for most users in comparison to striking a balance between having it all on the server vs the client.
- di4na 7y agoA slight point on Erlang: Erlang is good on business logic and not really good on making something "mathematically nice". It is more in the same place than the one you give to Go/Rust. Low latency good performance and great reliability (these things are linked) for web is a classic use of erlang or elixir.
- ken 7y ago> most – say, 90%, of what I learn at one job is completely useless for the next one This is the most surprising claim, to me. I would have flipped the ratios. Even the most radically different jobs I've had shared more than 10%. 90% of the facts that my boss tells me are useless for the next job, true, but 90% of what I learn are not the facts which are told to me.
- mmhsieh 7y agoGod must love us 1x-ers because He made so many of us!
- cyrialize 7y agoI've been a developer for about 3 years now. This is probably my own fault, but I feel pressured to be constantly doing something towards programming. I feel like I should either be reading a book or starting a project. I have 10+ programming books where I just finished reading one of them and I have way more unfinished projects than I could count. It's reassuring to see the push-back against the 10x developer idea, I'm starting to feel less guilty now when I spend my free time NOT on programming. Something that has also helped me out is picking a project to do, and ignoring everyone else's projects. I would always get pulled away with what I'm starting to work on because I see someone using a new technology or doing something unique. When I would see that I would change up my project because I felt it wasn't good enough or that it wouldn't make me a 10x developer. Now I'm just trying to focus on what makes me happy and what I find enjoyable to work on. I want to ask though - the author works at Amazon and considers himself a 1x developer. What does that mean for everyone else who doesn't work at Amazon or a FAANG company? Is a 1x developer at a FAANG company a 10x developer elsewhere?
- Bahamut 7y agoA 1x developer at one of the tier 1 tech companies is...just a 1x developer - doesn't really matter where you're at. Being a multiplier is not about just being technically proficient. It's about enabling your whole team to be more productive, and help getting to the right decisions, instead of decisions that might cost your team or coworkers huge amounts of extra work long term.
- cyrialize 7y ago> Being a multiplier is not about just being technically proficient. It's about enabling your whole team to be more productive, and help getting to the right decisions, instead of decisions that might cost your team or coworkers huge amounts of extra work long term. Thank you for this comment! I'll keep this in mind as I progress through my career. It's nice to know that it isn't just about being technical.
- Aeolun 7y agoAlso on getting your team to actually following those recommendations. I can be right every time, but still nobody wants to listen.
- aazaa 7y ago> And what I have found is that most – say, 90%, of what I learn at one job is completely useless for the next one. Then the problem isn't with what's being learned. The problem is that the author lacks a framework for generalizing and internalizing the lessons learned. Letting 90% of lessons learned on the job go to waste later in life is going to lead to a very difficult career path. Later... > Compounding is a pretty important concept that shows up in compound interest, in Moore’s Law, all over the place. It’s about virtuous cycles. And so in the limited flexible time that I have, I think the rule of thumb is to focus on things that could trigger a virtuous cycle. In other words, focus on activities that can capture more value from the 90% of wasted lessons. Writing, both publicly and privately, is an excellent way to do that. It seems the author may have an inkling but isn't saying it. Given there are only two posts on the blog, this could be the author's attempt to test the idea.
- Kwantuum 7y agoFrom the article: > So I’m going to try to bootstrap my software engineering longbeard wisdom in the following manner: > 1) Write out my inane thoughts on some software engineering topics. > 2) Share out my thoughts to people smarter than me and invite vicious critique. > 3) Update based on #2. > 4) Attempt to come up with a methodology for finding and prioritizing useful information to read about software engineering, or reflections based on new projects, and integrating into #1.
- fnord77 7y ago> Writing, both publicly and privately, is an excellent way to do that. Is there a right way to go about this? This is something I need to start doing, personally.
- Kwantuum 7y agoThere are only wrong ways to go about it, and you will only discover them by doing it.
- hamburga 7y agoOP here. You're spot on. Both in calling out that this is a solvable problem (not a fact of nature) and that writing is probably a pretty good way to get started. That was definitely the idea with putting up the blog. I came up with the 90% number not because I have any real data on this, but as a way to provoke myself to challenge some assumptions. Earlier on in my career, it was easier to tell myself the story that everything I learned, all the hours I spent doing stuff, were all part of a bigger narrative. That it would all build upon itself in a one-directional way. Even if I forgot specific facts, I'd still always be learning and growing in one way or another. I'd be developing critical thinking, learning how to learn, moving to higher levels of abstraction, pruning out useless knowledge and strengthening core insights. That kind of thing. That was actually a pretty useful mentality, and still is in a lot of ways. It gave me the confidence to do a bunch of career changes (like I think I mentioned in that section of the blog) because I did believe that I was drawing lessons from each successive career area to the next. And there was a lot of truth in that. However. At the end of the day, as a developer, I'm certainly not doing Leetcode or Kaggle all day. The majority of what I've spent my time learning has been very specific knowledge: learning the components and business logic in specific systems, getting comfortable with internal tools and processes, getting to become very familiar with some subset of all the company code, working with clients and dependent teams and internal customers. I do believe that being a tech giant can make the situation worse in that regard since the specific problems tend to be so narrow. But my hunch is that it's still the norm for developers. I'll put things in a different perspective. According to a lot of studies, doctors get worse at their jobs on average over time (link: https://hbr.org/2017/05/do-doctors-get-worse-as-they-get-older https://hbr.org/2017/05/do-doctors-get-worse-as-they-get-old...). Most of what they learn on a day-to-day basis is very specific, time-bound knowledge (specific patient info, office info) rather than general-purpose lessons about medicine. By going for the 90% number I was trying to push myself to consider that that sort of effect is the norm (in programming and elsewhere) in contrast to my earlier notions about "constant generalization." I think this number can be changed but like you mention, it requires an amount of deliberate effort like writing that just hasn't been baked into my usual routines.
- skywhopper 7y agoI'm somewhat perturbed that the entirety of the "DevOps" section is advice to get an SRE on your team because an SRE's job is to "be online after hours". That's an incredibly dismissive and reductive perspective on the expertise and insight that an SRE (or any ops staff) could bring to a project, and it sounds like this person--or maybe their entire team--is doing a really bad job of owning their own junk. I'll make a note to be extra wary of looking into any SRE jobs at Amazon if this is how they treat those positions.
- kakwa_ 7y agoThis is indeed an incredibly dismissive view, only seeing the SRE as the poor soul you offload responsibility of things running well in production, despite the fact he is likely to have far less insight on what might go wrong and means to fix things. Being basically in this position (but in a large follow-the-sun team, so I'm fortunate enough to not be paged at night), I can only underline the deep frustration such views can generate. Being paged every 10 minutes, being asked to fix things you have no control over, getting answers like "what? the server is overloaded? it's an infrastructure issue, not a bug in our code" and seeing developers cry when they get a ticket a day, when at the same time each SREs in the team is receiving a dozen, it can lead to some resentment. A saner approach is to have the SRE as the first line to filter bugs/alerts/tickets out, but being able to call a developer if required. The SRE can also be an active team member with more insight on production constrains and pain points and maybe system architecture recommendations for the whole team. Also, in my opinion, developers should be an active part of running things in production, otherwise the whole dev team can lose touch with reality and lose sight on how well or not things are actually running.
- mdszy 7y agoRules of thumb for a 1x developer: Stop with the 1x/10x bullshit and quit basing your self-worth on your ability to provide for an employer. Fuck sake.
- whateveracct 7y agoit's capitalist hypnosis
- chapium 7y agoThis notion that during non working hours I should still be working on side projects is absurd.
- qwerty456127 7y ago> I think of Go, Rust, Haskell, Erlang, Clojure, Kotlin, Scala as more hardcore languages. I can tell about Scala: it can be insane hardcore if you want, but it can also be just "a much better Java" as easily - the weird parts are easy to avoid and the normal parts work better. Unless you are a Java veteran and also plan to hire more developers, using Scala instead of Java will save you much time and effort. And Kotlin is, by design, kind of Scala minus the hardcore.
- solidasparagus 7y agoThe problem with Scala is the same as the problem with Lisp. It's too flexible and it ends up having a bunch of dialects. Sure you can only use a subset, but that doesn't fix the problem that the fragmentation makes it hard to find libraries and code examples that only use the subset of Scala you're comfortable with.
- overgard 7y agoWith rule #2, (knowledge not transferring), that's always a sign you're not working somewhere good, or you're in a role that will stunt your growth. You really should be able to transfer a lot of what you learn. If you're stuck with a bunch of proprietary gunk that does the same thing as open source, but worse, good engineering management knows to replace that stuff because it will inevitably drive talent away. Or at the very least rotate people through those roles. I know I've left jobs where I've been stuck maintaining legacy systems while the rest of the company moved on to open standards because if you do that for years it's like slow career suicide.
- austincheney 7y agoThere is so much that is wrong with this. Follow this advise only if you are currently employed and your employment is extremely safe because your employer is deemed essential or because they are financial strong in the current economy. For everybody else very carefully consider why an employer should hire you when the current economy is failing, programmers generally are very expensive and add very little value to the employer's revenue, and why you are a better value than the other 1000 developers that were just laid off. The economy is never going to be the same and the common suspicion moving forward is that software hiring/practice will also change to compensate. The article opens with having kids and so they cannot work more than 8 hours a day in a specified time slot. This is an absence of ambition and nothing else. Work-life balance takes some figuring out, which isn't avoidance. I have two white-collar careers in unrelated industries and kids. I have time for both jobs, coding on the side, spending time with my kids, helping my wife prepare dinner, and so forth. I am not unique with this regard. The bit about How to do Javascript is really bad advise. This is largely the story of my career in the corporate world as a JavaScript developer. The employer is mostly a Java shop because Java developers are easy to find since they are effectively mass-produced by universities. The Java developers have absolutely no idea what to do with any aspect of web technologies aside from Spring MVC. JavaScript is required by the business, so the Java developer fake it until they make it. They still have no idea what they are doing then give up and require a framework. Epic fail. Any other industry would call that an ethics violation, negligence, and that path would land you in a law suit or possibly in jail depending upon the product/industry. > So we went with vanilla JQuery. That makes me cry. The programming section is followed by a section on testing that almost makes me angry. Many of the use cases provided for writing tests explicitly mention low confidence on the part of the developer. Horrible advice. The things to test are features and use cases. The software does all that it promises or it doesn't and there should be enough automation to prove that. How you go about that depends upon the product. The security speaks like somebody who has absolutely no idea what security is. When you have absolutely no idea what security is or why the company would spend so much money on it I too would think everything about it is draconian and worthless. So many software developers seem to think they are well versed in security despite having no such experience, education, practice, interest, or credibility and I have never understood why.
- 7y ago
- imron 7y agoRules of Thumb for a 1x Developer During work hours stay away from: * HN * Facebook * Twitter * Reddit * Any other thing constantly distracting you and taking away your attention from your job Congratulations, you are now 3-10x developer.
- war1025 7y ago> Congratulations, you are now 3-10x developer. Congratulations. You are still getting paid the same. Boosts in productivity need to come with boosts in pay, otherwise the logical thing to do is to scale back your effort to a point where the amount you get done matches the amount you get paid for.
- jamespollack 7y agoexactly! if you're taking home the same salary whether you're creating massive value for the company, why bother?
- dang 7y agoSelf-respect?
- cambalache 7y agoIf you tie your self-respect on how useful are you to the company that pays you, you are fucked. For them you are just a number.
- discreteevent 7y agoSo is every professional you pay money to. But you will still recommend some and not others. When times get tight, those guys still make a living.
- cambalache 7y ago
- jeffrallen 7y agoI would like this guy as a colleague.
- cloverich 7y agoKudos for the open and honest assessment, I enjoyed reading it. Some feedback for your journey: Drop the focus on languages. Choose one (popular) language and focus on understanding it well. The best thing you can do, is find some open source project with high quality code in that language, and study it. Slowly, how long it takes does not matter. The end result is you will pick up best practices and styles you did not know exist. Concomitantly, study a few frameworks in your chosen language. Ex: If you select python and are doing web development, learn how Django and Flask work. Learn how the requests library or a forms library works. By reading good code, and studying frameworks and libraries that solve peoples real problems, you will build a foundation for how to put together higher quality and longer lasting code. That will not only make you better as a programmer, and better in your chosen language, but you'll start to find that a substantial portion of what you learn will start to transfer.
- Raphael_Amiard 7y ago> Drop the focus on languages. Choose one (popular) language and focus on understanding it well While I understand this advice, your mileage might vary. I had the exactly opposite approach and did learn a ton of different languages, on the end making it my area of expertise as a compiler developer and language designer. Of course that's niche, but knowing only one language will eventually become a blocking point for every developer, especially in the modern world.
- whateveracct 7y agoIf you are a 10x developer, you should either angle to get 10x the money or dial it down for your own benefit. Don't let some company get free value out of you!
- deleted 7y ago[deleted]
- dnautics 7y agoErlang (and elixir) are very unfairly bunched with Haskell since they are both functional languages; in practice they are functional in form and in the large, but they make compromises which really make them "a working person's language", not something to live in the ivory tower.
- alexandercrohde 7y ago>>> To replace out MediaWiki with a Java-based alternative (XWiki) ended up taking a total fo 24 dev-years over 4+ calendar years for the team He can call himself 1x, but if he can stop just 1 colossal failure like that he can easily become 10x.
- padseeker 7y agoI enjoyed reading this, although I should note that I agreed with the non-technical advice way more than the technical.
- kyberias 7y ago> I would use a microservice when I have a relatively small and simple chunk of code that needs to run every once in a while. Is this a joke? Why write such nonsense when you must know you don't know anything about the subject?
- technofiend 7y agoMaybe I'm being naive but I'm privately nursing this hope that at least for devops / SRE roles people do want folks with plenty of operational experience? I mean I still expect they'd want to see someone keeping up with tech stacks and facile in a modern language or two so the interviewee can fix issues and contribute enhancements but still is a depth of experience at some point really a hindrance rather than a help?
- alcover 7y ago> front end [..] consider something like Phoenix install = install Erlang + install Elixir + install Phoenix Well.. I'll stick to Node + vanilla JS
- mm89 7y agoInstalling something is easy, learning how to write Elixir/Phoenix/maybe Erlang is the hard part. Don't ever let "installation" prevent you from trying something, on Mac it's literally "brew install elixir" followed by a command to install phoenix framework.
- alcover 7y agoYou are right and that is what I meant. Sometimes though installation is a real pain. (For ex. OCaml/OPAM on Debian)
- 5cott0 7y agoI'm only a 3x developer but I'm still hardcore.
- 29athrowaway 7y agoYou become more productive by delegating work to the computer. The better you are at delegating work to the computer, the more productive you will be. Algorithms are elegant, data is not. If you are not careful, then data will leak into your program and you will end up with special cases for everything. When this happens, your job becomes a glorified data entry job. But you can be smarter than that and create abstractions over data that are reusable. And most likely that will involve types too.
- A21z 7y ago"Rule 11: Which database technology to choose: Choose SQL when you need to do ad hoc queries and/or you need support for ACID and transactions. Otherwise choose no-SQL" I think it should be the contrary: SQL by default, no-SQL if you have a specific need and know what you are doing.
- tikiman163 7y agoTo be completely frank, I'm seeing less and less reason to use traditional sql databases. MongoDB offers the ability to make sql queries and even has Acid transactions. Everything SQL can do, it does without slowing down when dealing with big data. The only thing it doesn't offer an efficient solution for is something SQL can't do either, and that's advanced search engine capabilities like Elasticsearch provides. Some people will argue that PostGreSQL is better in certain ways, but the argument really always comes down to 2 factors. Are you going to hit the cost efficiency performance limits of traditional SQL servers, and do you require advanced searching capabilities like graph queries or synonym matching. Even if both answers are No, I'd still argue for Mongo because it makes it easier to distribute Acid compliant coppies of the data by region, providing backup redundancy as well as fast responses in multiple regions.
- Youden 7y ago> MongoDB offers the ability to make sql queries and even has Acid transactions. Everything SQL can do, it does without slowing down when dealing with big data. The only thing it doesn't offer an efficient solution for is something SQL can't do either, and that's advanced search engine capabilities like Elasticsearch provides. You seem to be looking at this solely from a perspective of what kind of queries you can run but there's a lot more to it than that. For example how do you model and maintain relational data, which I'd argue is most data? Does MongoDB have support for foreign keys or something like them these days? A quick Google brings up DBRefs but these seem very soft.
- OOPMan 7y agoYou made the point I wanted to make without sarcasm. Thanks :-)
- freewilly1040 7y agoNot sure I entirely agree on rule 18. My current team probably cares about estimation more than any previous one I've been on, and it's functioned more to keep engineers aware of prioritization and what is blocking. The team leads have definitely made it a point of emphasis to not put pressure on finishing sprint tickets, though.
- danielovichdk 7y agoThis must be written by a developers with only very little experience. Generally very shallow advice and poor or no discussion on why.
- postalrat 7y agoExactly what the 1x developer is looking for.
- freewilly1040 7y agoIronically this comment is quite shallow and lacks any contribution to discussion
- OOPMan 7y ago"Rule 5: When to use Python or Ruby Python and Ruby seem to me to be pretty similar in that they’re scripting languages and dynamically typed and seemed like the greatest thing in the 00’s. You use them when speed is more important than legibility or debugging. And then Python for ML/AI applications." Eh? Speed? What kind of speed? Developer speed? Code speed? Why is legibility in Python/Ruby bad? Bad compared to what? Why is debugging in Python/Ruby bad? Bad compared to what? Frankly...this feels like a 0.5x article to me
- hamburga 7y agoOP here. I know that these rules of thumb gloss over some of the details, and it's this kind of ruthless criticism that I wanted to invite with posting this :) I'm coming from the perspective of a tech giant, where there are thousands (tens of thousands) of services, and it's often a huge challenge to trace the flow of data through any given system or API and pin down the cause of production issues. The static typing with Java gives us a lot more guarantees about the data flowing through systems, compared to Python. If I want to inspect some code or debug a production issue, static typing gives me a lot of guardrails. I can be sure that data coming in is of a particular shape, that null constraints are met, etc. Whereas (from what I can tell) it takes a lot of extra work (and more possibility of missing something) to do the same with Python or Ruby. But I haven't ever built a Python or Node service or whatever. That's what I meant by legibility and debugging speed. If you define legibility as "can understand the purpose of the code," I do think that Python can be way more legible since you've got so much less boilerplate.
- scooter_de 7y agoAs he said: He's a 1x developer.
- sufyanadam 7y ago> Rule 20: When somebody says Agile, push for Kanban, not Scrum... ...Scrum can easily mean that you’ll get pressured to work extra hours to complete something within that arbitary two-week horizon. This is very true. I've worked for over 12 years in the bay area in different software engineering teams at startups and found that scrum just leads to burnout and developer unhappiness and encourages team members to just do the minimum 'slap it together till it works' solution without thinking long-term on codebase stability, architecture and maintainability. By far the best development process that leads to high developer happiness, engagement, productivity and empowers them to go the extra mile to go above and beyond, and produce work that acts as a force-multiplier across the team, is what the author describes here as 'Kanban', also known as eXtreme programming. Most people from Pivotal Labs or Carbon Five or from a startup that adopted their process would recognize what the author describes as 'Kanban'.
- eastbayjake 7y agoTo be clear: XP and Kanban are different things. XP has prescribed engineering practices, most forcefully that development should be done via pair programming for continuous code review. Kanban prescribes no engineering practices and could be used in lots of non-engineering contexts (e.g., your marketing team could take all of their tasks, put them in a prioritized backlog, then track the progression of those tasks across Todo/Doing/Done/Blocked and that would still be Kanban). Kanban is great for teams in maintenance mode with a steady in/out of smaller tasks in their backlogs, but it's not great for helping your customers get an idea of when they might see a new product or feature. I do find it odd that people describe Scrum as "leading to burnout" or a "death march", and I'm guessing most people who do either have not worked in waterfall IT projects that preceded widespread Agile or they're part of "Agile" teams that do waterfall development in two-week chunks with daily standups. (Maybe both.) Scrum practiced well brings the essence of small-town democracy into the workplace. You have to work a late night the day before sprint release? You were in the room when the team agreed to the body of work that would be committed for delivery in this sprint. You just slapped it together until it works? You'll get to accommodate 0-point bugs in a future sprint, and perhaps you can have a conversation in your team's retrospective about why velocity went down that week. (Speaking of: how many other professions get to have a candid conversation with management about what's going well and not going well on a regular basis? Not many, it's a real privilege!) There are certainly deviations from this, but in my experience Scrum teams' problems are generally of their own making, and many of those problems are refined away over time as teams grow and better define their norms.
- beefbroccoli 7y ago> Try to push as much logic as possible to the server. If the front end weren’t super complex, I would consider something like Phoenix instead which actually pushes everything to the server. Sometimes you don't have or don't want a server, but still want to avoid the issue of wedding business logic to the UI. With web apps my strategy is to treat business logic as a separate library housed in the same project. I'll have a "SomeBusiness" directory and just import it across the project like I would a third party library.
- Shorel 7y agoI think nothing is truer than rule 16. "If you delegate all your IT security to the InfoSec, they will come up with Draconian rules"
- jb3689 7y agoHeck, writing this post is enough to be at least a 1.1x dev. I don't subscribe to the whole "x developer" thing, but this is an amazing list
- flavious 7y ago> Rule 20: When somebody says Agile, push for Kanban, not Scrum From my experience, scrum is better. The idea is that you can measure progress and you can learn from mistakes with scrum. Kanban doesn't help in that regard. Also, a good scrum master will tell you some things: - a successful sprint is one in which not all stories were finished, because the goal was ambitious - do not sweat over spill-overs; they happen all the time, it's not the end of the world as long as you work 8h/day really focused and give your best I know that in the US you got modern slavery with insame working and commuting hours, but life is decent in places like Europe.