22 ms·
How to be a -10x Engineer
- trash_cat 4y agoExcellent manual when it doesn't matter if you pretend to work or do the work and the outcome is the same.
- dt3ft 4y agoMock everything until original code no longer executes (which was supposed to be tested): this one hits close to home. If everything is mocked, what are you testing really? Gah.
- arnejenssen 4y agoYou mean a 1/10*x engineer?
- maayank 4y ago"Explain code in private messages. Write wikis that nobody uses." What the reasonable alternative though? What's the happy medium?
- anilakar 4y agoWhen a coworker does not understand what a function call does, you add a verbose enough comment directly to the code.
- ejb999 4y ago>>Explain code in private messages. ...and this is the natural result of the 'no comments allowed in the code' nazi's that seem to permeate lots of organizations. For the life of me I could never understand that particular bandwagon. I for one love it when I go back into my code after a few years and a few well placed comments remind me why I did what I did last time I worked on it.
- Ensorceled 4y agoI took over leadership of a project where the previous CTO was a "code should be self documenting" proponent and enforced a comment limit with a precommit hook. I think I made some of the developers cry when I asked why there were so few comments.
- ejb999 4y agoeven worse, I worked on a project where you were not allowed to have comments in code, but if you really felt a need to explain something, you could put it in the projects readme.md, referencing the file and line number and why you did what you did. Talk about a bone-headed outcome of claiming 'we don't allow comments in our code' mentality.
- Ensorceled 4y agoOMG. I fell afoul of commenting AND coding "standards" when I used Duff's device in an embedded system and my comment was something like. /* Using Duff's device see <reference> for speed and code size */ The poor developer assigned to replace it with "better code" had an impossible task because they couldn't find anything to replace it that wasn't either much slower or much bigger.
- nyob 4y agoI would suggest you to read Clean Code by Robert C. Martin. There's a whole chapter about comments in the book.
- ssrc 4y agoI try to write informative comments. That said, 99% of the comments I see are * Useless, like "locks the mutex" before a mutex.lock(). * Contrary to the code, like "This parameter contains the proc name without the instance" and then the parameter does contain the instance. * Dubious, like it's not obvious what the comment means nor if what you are doing follows the comment or not. Worst thing is when the code and the comment contradict and there's no good reason to trust one over the other in what the code should do (never go to sea with two chronometers). I suppose it depends on the codebase you are working on. If it's your own code the likelihood of you agreeing with the comment increases, ofc.
- Frotag 4y agoZero effort solution is to have permanent group chats so background info like discussions on requirements are searchable.
- flumpcakes 4y ago> Ask your team to perform tasks that resemble work. Common examples include presentations, diagrams, and ticket management. I'm as salty as the next guy, but in my experience it has been the sub-par employees who are the ones that don't do this. Ticket management is not busy work, it's a necessity for everyone to keep updated. Presentations and diagrams are tools to communicate. I can safely say that by far the most waste I've ever seen has always come down to poor communication rather than anything actually business or technical related.
- flippinburgers 4y agoI think there is a balance but yeah it isn't good if no record of "where we are" exists.
- steveBK123 4y agoYes but I think people overestimate how automatable this actually is. Where we are context depends on if the audience is - * The next developer to pick up the task where you left off * Your technical lead asking for update * Your manager needing an update for his manager * Product management wanting to know where we are on some feature * End users wanting to know when the bug fix / feature they asked for will be in their hands Everywhere I have worked, we had multiple apps/ticketing systems/etc all trying to roll up / slice & dice data to get to the above. In the end it just turns into talking to management pinging the next level below them for adhoc status. Why? Because product is too ignorant to open Jira nor maintain status themselves. Because management above the line manager level is apparently incapable of opening Jira either, let alone 2-3 levels up. Also no one wants to hire real project managers anymore to maintain all the different views & send the weekly updates they demand to receive.
- steveBK123 4y agoAnd remember, all of the above is a symptom of being in an organization where someone more important than you says "I don't have time to look at <insert reporting system>, tell me what the status of <deliverable> is". Fixing this from the bottom up is better accomplished via updating ones resume & LinkedIn profile.
- bayesian_horse 4y agoNormally that role is called a "manager".
- barrysteve 4y agoNice conceptual bulwark against the mythical negative engineer. It makes sense to balance out the normal 10x tropes.
- lifeisstillgood 4y ago>>> inconspicuously waste others’ time, write lengthy messages/documents and share as widely as possible. Welcome all opinions and aim for engagement. Mostly spot on but I am not sure of this one - well written notes / emails about technical issues and some of the trade offs or desired outcomes are really useful - they actually help "align" people. Think more "Linus rant" than "CEO powerpoint" but the idea is there
- Jolter 4y agoSharing those too widely is hugely counterproductive though. It will engage people who have no business with it. It’s what Yammer does to an organization — introduces all the disadvantages of Twitter with few of the benefits.
- saltypepperfox 4y agoOmg, I knew a PM/Architect combo who fit the bill. Scary how quick they came to mind.
- hardwaregeek 4y agoThis does underline a key point. Avoid unnecessary perf hits in your workflow. The whole Interstellar meme of "this little maneuver is gonna cost us 10 years" is very much true. I've worked on high performance teams that did the wrong thing strategically and it ended up effectively slowing down their pace massively. It doesn't matter how fast you're running if you're running in the wrong direction.
- DiscourseFan 4y agoA friend of mine accidentally wiped out over 100k hours of other researcher's computing operations the other day, does that make him a -100,000x engineer?
- regularjack 4y agoIf that data would be wiped by a fire instead, would you call that fire a -100,000x a engineer? Accidents happen, the fault lies on whoever did not backup the data.
- DiscourseFan 4y agoI suppose the author of the article would, though.
- drewcoo 4y agoWhoever is responsible for backups but didn't set them up might be. The person who wiped out the data should be thanked for uncovering the serious problem.
- ilyt 4y agoNope, only the person that didn't thought about backups of that.
- ok123456 4y agoNo. You'd call him unemployed.
- lightbendover 4y agoProbably not, unless they did that in their first hour of employment.
- agentultra 4y agoI don't agree that writing and communicating designs, plans, and discussing problems or solutions is a waste of time. Our job isn't to blast code out and not talk to anyone (unless you're the sole developer on a project, but even then you should still write). Writing is thinking! Thinking is our job. Code is the artifact.
- mkl95 4y ago> Make undebuggable programs. Plaster layers of abstraction over everything. Write spaghetti code. Make everything sensitive to initial conditions. Avoid pure functions. Use dependencies liberally. Say “it works on my machine” whenever possible. A lot of legacy software is like this. I wonder how many billions it costs the economy per year.
- perceptronas 4y agoIts extremely hard to argue for debuggability. I always try to prioritize how easy is it to test the said feature and understand it. However, during reviews of other engineers PR, I am always met with criticism that there is no need. "Instead of localhost, this can be tested on staging" and etc.
- solarkraft 4y agoDebuggability is a top factor for how long development will take. How is it hard to argue for?
- quickthrower2 4y agoOnly for developers who want to thoroughly test and check their work.
- edgyquant 4y ago>Instead of localhost, this can be tested on stagin No, it must pass a preview before being merged into staging
- bdcravens 4y agoThe more difficult situation is the legacy software with all of those problems that actually makes money.
- hermannj314 4y agoI got burned out and lost a few years of my life due to a job like this. We had two things: a. Poor systems and poor communication permeated the IT department b. IT was viewed as a cost center so no amount of heroic intervention was ever rewarded proportionately to business impact. It was Sisyphean. If you are in a situation like this, please run away. You can't win - either the free market will destroy your employer, or your employer will destroy you.
- baal80spam 4y ago> IT was viewed as a cost center Serious question: isn't it always?
- NortySpock 4y agoNot if the people who develop valuable new product features are embedded directly in your IT department. Basically, if IT + Product Development are in the same financial "bucket", IT can be viewed as directly supporting product development.
- theery 4y ago"Hold 10 engineers hostage in a technical discussion." Oh how I don't miss working in an office. Avoiding work, overthinking things, and overbuilding.
- Dowwie 4y ago> Attract bright engineers and waste their potential. Undersell the difficulty of the project to management; oversell the project’s usefulness. Tell management it’s “almost complete” until they scrap it. People at every level of the organization, from the top-down, have done this since forever. The -10x engineer will choose a language that they're fascinated by, but have no production experience with, and then spend most of the budget building libraries that they assumed already existed in the ecosystem. "Almost complete" becomes "almost ready to start".
- cowmoo728 4y agoRDD (Resume Driven Development) The desire to add $TECHNOLOGY to run a relatively small site even though it will likely never scale beyond what a single postgres instance running on a mac mini can handle.
- koboll 4y agoUnbelievably frustrating to be a junior or mid level engineer working with a senior dev who does this, watching it happen, maybe even arguing back and being overruled.
- photochemsyn 4y agoA lot of these look like Goldilocks problems, e.g. > "Waste 400 hours of engineering on bad architecture: Give zero consideration to how your system design will evolve over time. Alternatively, drive your team obsess over architecture decisions so that they don’t have time to test their hypotheses." A complex project with many people working on it in different teams calls for modularization and well-defined interfaces, so working out the architecture up-front does matter, and changing it down the line will have huge costs. Staged progession is the answer, probably, which is why you'd want to have a meeting where everyone agrees, "this is the architecture we're going with, now everyone go build the modularized widgets that fit into this architecture, here are the stable interfaces to build to." Screw that up and you end up with tons of wasted effort, but dithering around and never making a decision is no better. Some of the other stuff relates to the 'build team spirit' corporate mentality which is kind of culturally variable - some people love it and some people hate it. Minimal is better, IMO. Then there's the 'basic technical proficiency' category of problems, e.g. recompliling the entire collection of source code every time you make a lttle change because the build configuration in the makefiles is incorrect etc. That's probably the easiest category to fix, some people just have holes in their knowledge and those can be filled. Here is where the company jerk is a major liability, though - you want people who can teach others how to improve their workflows without engaging in any condescending / egomaniacal / prima donna behavior.
- pablok2 4y agoThis is hilarious, good ol' irony
- tourgen 4y ago[dead]
- Kon-Peki 4y agoI've seen the other side. 2/3rds of the devs I work with have no idea where the money in their paychecks comes from, and couldn't care less. TLDR: customers don't pay for beautiful, elegant code dealing with the happy path only.
- poulpy123 4y agoNo need for all that, it's natural for me
- swader999 4y agoThese are valid points in the article and the comments. But people can change and it's very very rare you run into people that want to work in ways that upset everyone. The lead has to persuade the dev that this is counter productive and not acceptable. And of course sometimes this doesn't work and they need to go.
- blantonl 4y agoI love the skunkworks reference. Every time I see something like this in a 3 person startup, I just want to grab someone by the neck and tell them: "Bro, your mobile app redesign to Flutter is not a 'skunkworks' project. Unless you are Lockheed Martin, or Boeing, and the project will approach a trillion dollars of spend, has the capability to eliminate millions of human lives, and requires 1000 security managers and 25,000 Top Secret/SCI employees you ain't doing no 'skunkworks'" Cracks me up.
- amelius 4y agoThis holds more for managers than for engineers, in my experience.
- m3kw9 4y agoMost of us are guilty on at least one of these to a certain extent
- benknight87 4y agoyeah this is why I always work solo. Microservices built by small teams where everyone has a distinct role.
- articsputnik 4y agoIn that context, I love giving complete responsibility to a small, integrated team of designers and programmers. They define their tasks, adjust the scope, and work together to build vertical slices of the product one at a time. This completely differs from other methodologies, where managers chop up the work and programmers act like ticket-takers. Instead of having 10x engineers, make the team 10x. Shape Up (https://basecamp.com/shapeup/0.3-chapter-01#making-teams-responsible https://basecamp.com/shapeup/0.3-chapter-01#making-teams-res...) by Basecamp is the best resource I've seen on that topic.
- rc_mob 4y agoFrom my experience the lowest productivity engineers are the ones that just never talk. I understand being an introvert but we all chat about things we have passion for. Anyways ive seen so many "programmers" that sit silently in meetings and also just do not produce good code. Usually they produce bad code that I have to revert.
- francisofascii 4y agoThat description sounds more like a 0x or -1x engineer. Consider yourself fortunate to having never worked with someone who is closer to -10x.
- Aperocky 4y agoI have corrected design (that fortunately were not implemented yet) where an API were to make parallel calls to the same table, and after all of them returns, calculate the pagination via combination and math. I replaced it with an index, it was a pretty straightforward index as well, imagine the pain if the original design was somehow implemented.
- TAKEMYMONEY 4y agoCan we go back to calling it "changing" instead of "pivoting" again?
- commandlinefan 4y ago> Decide that existing solutions aren’t quite what you need But > Add dependencies that demand 400 hours of maintenance. These suggestions conflict with each other - if you're one of these "don't ever write code if somebody wrote something somewhat similar" types, you're also the one adding terabytes of dependencies that have varying levels of documentation and stop being supported at arbitrary points in the future.
- zeteo 4y agoPeople can have off days or struggle with certain tasks, but that doesn't mean they are intentionally harming the productivity of the team. In many cases they just need support, guidance or an opportunity to learn. It's highly likely that everyone initially joins the company with positive intentions. However, exposure to cynicism and witch-hunting, such as labeling someone a "-10x engineer," can lead some people to become disillusioned and potentially adopt harmful behaviors intentionally. This can create a vicious cycle indeed.
- senko 4y agoGood list. Should be called "How to be a -10x Manager" though, since the majority of the bad decisions listed there are under the manager's purview. Reminds me of the CIA sabotage field manual: https://www.hsdl.org/c/abstract/?docid=750070 https://www.hsdl.org/c/abstract/?docid=750070 On another note, many of the items there are "create pointless X". It's actually a thin line between "important X" and "pointless X" and many people will disagree where it actually lies (as evidenced in the comments here).
- zippergz 4y ago"Change requirements as far into development as possible. To avoid blame, obfuscate requirements from the start." -> "Refuse to change course even though new information came to light. To avoid blame, display extreme confidence in the requirements even though there are still unknowns."
- f0e4c2f7 4y agoIn David Graeber's book Bullshit Jobs he categorizes this type into a phylum of "bullshit generator"
- tadzikpk 4y agoOh, you forgot “publish a service with undocumented limitations that others are required to use”. You can easily achieve -10x that way!
- eschneider 4y agoMeetings are a huge opportunity to either value-add or value-subtract and a little planning can go a long way. Some pointers: * Have an agenda and circulate it along with the invite. Let people know what you want to discuss so they can prepare. * Know what outcome you want from a meeting and let people know in the invite. Again, it lets them come prepared and even better, make pre-meeting suggestions. * Think about who needs to be involved. Do you really need everyone, or just one or two people. Again, agenda lets folks know if they can contribute or if someone else needs to be pulled in. It's not that meetings are bad, but bad meetings waste lots of people's time. Good meetings save time. Oh, and write down meeting minutes and publish results. The person you're recording this for is usually yourself. :>
- bradwood 4y agoWhat about the 0.01x Engineer? Much easier to achieve I think: do as little as possible without getting caught.
- surement 4y agobasically the 0x engineers the article talks about wrt opportunity cost
- _oyks 4y ago"Don’t settle for dead-weight." - amazing
- yunwal 4y agoMost of these are either management issues or written as if the person is acting in bad faith. But there are plenty of engineers who are 1) smart 2) driven, and 3) well-meaning that still find themselves in this position One time I found myself in this position was overseeing an infrastructure migration for scaling reasons. The goal was to have it done before we hit scaling limits, and we had a team of 2 people and a fairly complex architecture. From the start, I suspected it might be difficult to do with the current staffing, even after extensive planning, but I underestimated what the costs would be to not completing the project on time. I was told by my manager that completing the project before hitting scaling limits was life or death for the company (it wasn’t, I know this because the sales team didn’t hit their targets and we survived). I now realize this was my manager attempting to motivate me to take on a tough project, rather than real truth. Had I pushed back harder, inquired about company financials, this would have been exposed as not true. While we eventually ended up completing the project, we completed our largest phase of hiring while in limbo between 2 architectures. The company became disorganized, accepting large amounts of tech debt as it was tough for new hires to understand what the “correct” thing to do was, and many people ended up adding to the legacy architecture in cases where they didn’t need to. It was a mistake that likely cost millions, even tens of millions in my eyes. The correct thing to do, of course, was just to insist that we couldn’t scale until we trained or hired more people to help. Limiting growth is often seen as unacceptable in startup culture, but IMO should be considered more often.
- sebringj 4y agoI might be skipping the competence part but personally my performance has been directly correlated to how much I care about my team/org. My attention is focused and goal oriented in a proactive way when I do care but passive and reactive when I just want a paycheck. I don't have good advice to spot how people care so its not super helpful but people that don't attempt to help in hairy situations or seem withdrawn from conversations are probably not on the good end of things.
- liamN 4y ago> To ensure developers are context-switching, recompilation should take at least 20 seconds. So true. But only 20 seconds? The project im working on takes 20 MINUTES to compile for any code change. I constantly forget about it while trying to get something else done in the mean time. It frequently takes whole days to track down and verify simple issues.
- atoav 4y agoI think as engineers we have to realize a few things: 1. Unless you are working alone and for yourself good communications are more important than most engineers will admit. The thing is: the quality of communication does not necessarily correlate with the quantity or the duration of it. And depending what role you play, you might not need a lot of communication in order to get a clear picture, while others might need more (for you: unnecessary) communiation to get on the same page. The drummer of my band always used to say there shouldn't be that much discussion about what we are playing, which is super easy to say if you don't need to harmonically integrate with other instrumentalists. 2. Every single one of us is in danger of dialing the degree of complexity too far, or not far enough. Every single one of us is in danger of doing things a certain way because we try to make them nice, while that makes them technically unmaintainable. Code is communication as well. Communication with your collegues or yourself in the future. Good code is efficient, reliable and communicates well. Sometimes we have to sacrifice a little bit of one for the other, but clear code and e.g. efficient code should not be seen as opposites, but as a multidimensional problem to which there are solutions that work better on both fronts and solutions that suck on both fronts. 3. Context. Many engineers I have met have a hard time explaining some concept or problem in a way that it is understandable. Either they dive in way to hard and assume everybody knows what they know or they will start explaining it and get side-tracked and end up talking about something entirely else. Giving someone a clear image of where we are and then zooming in on the detail in well-sized steps is a skill I wish more people had. This skill also helps when debugging, because you will check your zoomed-out-priors first and then bifurcate the problem space as you zoom in.
- yuppie_scum 4y agoAs a manager, I’d rather have a 1x engineer who spends that x doing exactly what I want/need.
- lispisok 4y agosigh. The 10x engineer has become tech's most toxic concepts and devs are its victims, yet we keep bringing it up constantly. Every time it's brought up it's a new variation that's either bad or good but always different than the original proposal of the BEST programmers are 10x more productive than the WORST developers from a paper in 1968. All that is come of it is devs arguing about a hypothetical programmer is and made management even more insufferable. The idea is only hurting you, quit bringing it up, when it is brought up point out it's a bad concept and move on.
- 2OEH8eoCRo0 4y agoI thought so until I met one. He knew what our team lead wanted before he wanted it and would already have it done, along with all of his assigned work. He would take initiative and build tools that the whole team could use and be more effective with. He had a huge impact on me.
- jackblemming 4y agoThat just sounds like a developer who had worked on a similar project before, which would obviously look like some kind of genius vs those starting from scratch.
- 2OEH8eoCRo0 4y agoNegative. He came from working in startups to working in defense. The work could not have been any more different. He was initially unfamiliar with most of the tools and processes that we used.
- varjag 4y agoSeconded. I was lucky to work with one at my first job, which helped to calibrate expectations and set standards for myself.
- justin_oaks 4y agoTo be fair, you're the one bringing up the 10x engineer. The article only mentions it for the sake of contrasting it with -10x engineers: "+10x engineers may be mythical, but -10x engineers exist." And that's all that was said about it. I agree that arguments for and against are tiring, so let's talk about the article instead! I've definitely seen engineers who have been net negative in productivity. They've distracted me from my work, introduced bugs that have had severe effects on the production environment, and have produced code that had to be thrown away and completely rewritten. Luckily, the items in the article aren't commonly seen all in one person, but they are great ways to lose productivity and negatively affect others in the company.
- CTmystery 4y ago> To inconspicuously waste others’ time, write lengthy messages/documents and share as widely as possible. I transitioned from startups (for 10 years) to a large company (for 5 years). Part of that move was adjusting from a culture of no lengthy documents to a culture full of lengthy documents, and I would never want to go back. Having explicit documentation in writing, where folks can debate the merit of ideas is so so much better than having it living in a few people's heads, unable to be critiqued. Edit: add a word.
- afterburner 4y agoI guess you're lucky enough to be in a large company where the majority of people actually read and properly understand what has been written. I've had plenty of experience with supposedly senior people fundamentally misunderstanding core concepts of the technical work.
- martialg 4y ago10x engineer is a good meme, but a bad classifier
- taink 4y agoDon't forget your basic organization sabotage field manual: https://archive.org/details/SimpleSabotageFieldManualStrategicServicesProvisional/page/n31/mode/2up https://archive.org/details/SimpleSabotageFieldManualStrateg...
- cbreynoldson 4y agoArticle's points shouldn't be taken as seriously as the general message: be just as aware of the invisible, negative forces that hinder employees as you are of the positive forces which stellar employees bring. Yin and yang. Important to note that there are also 10x environments that make everyone in them 10x as effective.
- patrakov 4y agoThe title contains an arithmetic error. What the article describes is a combination of 20 strategies (and explicitly advises to combine them!), each of which would have produced a -10x engineer. The result, therefore, is a -200x engineer.
- quietthrow 4y agoDoes it bother anybody that he is promoting his own article by posting it? I have seen this and many other comments by this user as what seems like a funnel to book time with him and eventually be a paying customer. I am not sure how I feel about this.
- dgs_sgd 4y agoI think it's fine as long as the content is suitable for hackernews
- surprisetalk 4y agoI've been writing/posting a lot lately because I got laid off recently :) Honestly, I've just been yearning to meet new people who love making things. It's super fun chatting with strangers on the phone! EDIT: Actually, if y'all have extra money lying around, consider donating to my AIDS/Lifecycle campaign :) Improve living conditions for people with HIV/AIDS [1] https://giving.aidslifecycle.org/participant/taylor https://giving.aidslifecycle.org/participant/taylor
- deleted 4y ago[deleted]
- didip 4y agoThis whole thing about company/team culture is that it is random. Even when you are at the best team, culture-wise and productivity-wise, accept that this will not last. All it takes is for 1 person to arrive/depart to ruin the culture. Just do your best and bounce when it's time. You cannot move Mount Fuji with a teaspoon.
- cowmoo728 4y agoone other to add: claim high-value projects/tasks, but don't finish them. when another team starts working on the same problem, schedule a meeting over their head and tell the other team's director level that you're already working on it and it's a waste of resources for multiple teams to work on this simultaneously.
- vardump 4y agoJust need to put two of these -10x engineers working together. The results should be amazing!
- larsrc 4y agoMissing: Start migrating the code base to new technologies/frameworks early, but never finish it. Though that might actually end up costing more that 400 hours of wasted time.
- nico 4y agoJust had a conversation about this. Let’s let AI do all the busy work for us. I personally just want to think deeply, share ideas and connect with people. I don’t want to be forced to do any meetings, presentations, tickets, code, documents… I do want to produce some of those things, as long as I feel like they help me in what I want to do. I want AI to do all the shit I don’t want to do. I still want to work, interact with people, feel needed and feel connected. Just not forced to waste my time.
- EchoReflection 4y agoseems like that article is/was kind of a sick joke. i feel like reading an article about "how to waste your time/other people's time" is...a waste of time.
- jsutter909 4y ago[flagged]
- KronisLV 4y agoI actually wrote an article a little bit like this one, a tongue in cheek piece called "The Unethical Developer's Guide to Personal Success": https://blog.kronis.dev/articles/the-unethical-developers-guide-to-personal-success https://blog.kronis.dev/articles/the-unethical-developers-gu... In short, software development should most of the time be treated as a group activity and you should consider how the output of your own work affects those around you. While you might not feel like documenting your decisions is a wise use of time, it could help others down the line. The same goes for choosing the simplest solution that works well vs going out and writing lots of "clever" code. Things like the ways how we communicate, how much nitpicking vs accepting "good enough" solutions all compount and have a pretty great effect on the output of others.
- chasd00 4y ago-10x software engineer is someone who refuses to recognize and learn from their mistakes and also refuses to learn anything new or different.
- irrational 4y agoWho is the 1x engineer that all of these 10x, 100x, 1000x, -10x things are based off of?
- herbcso 4y agoWait, was this NOT a belated April Fool's joke?
- sawyna 4y agoFunny enough I have been dealing with this situation at work exactly right now. It is insanely annoying to be in such an environment. Obviously, I'm the odd man out for saying a project can be done by 1-2 engs in a month. This said project is being currently done by 10 engs who are all writing boilerplate code since two months. The management is not taking responsibility and I can't believe everything that is said in the post is fairly accurate.
- garunski 4y agopro tip: post to the company general channel and ask who thinks there are people like that here? and what proof do you have?
- ocimbote 4y agoHow to be a 1/10x engineer?
- deleted 4y ago[deleted]
- ryukoposting 4y ago> Trap 10 engineers in a futile skunkworks project. This is the business model of roughly 7 out of 10 startups.
- stan_kirdey 4y ago... -> hallucinate your answers to the team mates, as if you are an LLM
- deleted 4y ago[deleted]
- jiggawatts 4y agoI'm nodding along to this list because I've been consulting with a large government department that has dozens of programmers with the effective output of maybe... two? Three at the most. They tick just about every item on that list. Staggering inefficiencies everywhere, duplicated work, duplicated codebases, etc, etc... The worst thing about these problems is that they compound, often exponentially or at least quadratically. Slow builds mean bug fixes take longer. Longer bug fix times means they can't all be fixed to meet deadlines. That means that they now have to be prioritised, which incurs management overheads and shuffling things around in spreadsheets. This then delays things further, which means even critical requirements (security!) get dropped on the floor. The inevitable consequence is that things are constantly breaking in production, and everyone spends half their time fighting fires. Fires that were marked as a "low-priority" smell of smoke six months ago. Productive staff see the writing on the wall, quit, leaving only the unproductive staff that "couldn't get a job elsewhere". The snowball builds rapidly from here into an avalanche of badness.
- ornornor 4y agoI worked in such a place. Worst job I’ve ever had, extremely toxic culture, I ended up burning out and quitting. It took me 18 months to recover from my 3 years nightmare there. Never again.
- ipaddr 4y ago"Introduce subtle randomness into your tests so that they succeed/fail without cause." That reminds me I have one of these in the wild. Hope to resolve it one day...
- kevin_thibedeau 4y agoI had some of my code handed over to a subcontractor once. My boss found a design issue in code review that caused me some initial blowback but I pulled out commit logs and the correct code I wrote had been changed on purpose to be "less naive" by someone at the sub. They broke the code in precisely the way my implementation was meant to guard against. They went out of business soon after that incident.
- Nevermark 4y agoSome curious and easily distractible engineers have trouble making progress, but generally don’t cause harm. They basically work sideways to the direction of best effect. However if there are two of them, their product is negative. Or perhaps I am perceiving a dysfunctional pattern that really isn’t there. Yet, even if they are imaginary, their impact is real.
- nith3n 4y agoAs a platform team leader that caters to other engineers within the organisation, extensive documentation is what enabled me and my team to be productive. I answer almost all questions posed to me with a simple have you read this (confluence link )
- resonant123 4y agosow distrust in ur team by taking credit in your teams work amirite?
- firatsarlar 4y agoWhat is X -> baseline of this hype !_? And is this a linear function ? X does 10 things - what things ? - 2X does 20 thing ? --> linear .. There is no 10X engineer, there is authentic, lover engineer for me .. Lets skip comparing us each other, in right place, right will, and a little love every dev is 10X. Rest, never ending run, never ending desire, never ending darkness.
- black_13 4y ago[dead]
- watters 4y agoThese examples could variously describe median (or worse) product managers, eng managers/directors/VPs, and program managers.
- hiruthikj 4y agoLol
- dzonga 4y agoyou could've simply said how to be an engineering manager at big org
- thewileyone 4y agoSeen many of these rise to managerial ranks where they kick up their -10x work into high gear to make up for imposter syndrome.
- biosboiii 4y agoYou forgot the most crucial part to making a career in big corps: After you fucked everything up "rescue" the project with witnesses.
- ilyt 4y agoAnd get promotion over guy that didn't pushed broken shit on production in the first place.
- sublinear 4y agoGot it. The -10x engineer is bad management who are in turn bad because the rest of the business is completely illiterate about anything even slightly technical.
- version_five 4y agoThat was roughly my takeaway, as well as personal experience. Even if there's an actual engineer operating at <= 0×, it's still mostly a management problem. There may be rare cases when someone is quietly subversive, where it would clearly be that ICs fault.
- sshine 4y ago> the rest of the business is completely illiterate about anything even slightly technical It is that moment of realization that you're entirely responsible for the fate of the company, and you either think "I better tread carefully" or "This should be rewritten in Rust."
- weego 4y ago"We need a new build system that's built on streams"
- nickpeterson 4y agoRust may still be a bit too pragmatic, perhaps you could use a language you wrote yourself?
- the_sleaze9 4y ago"Aaaand that's the container address orchestrator -- it's written in Haskell by that one guy a few years ago."
- ilyt 4y ago"We wait for it to break for last 3 years just to have excuse to run k8s"
- dividedbyzero 4y agoThis reads a lot like one of those WW2 low-risk sabotage manuals.
- rvba 4y agoThis looks like the behavior of management in a company where I worked. The business was relatively 'boring' - core product would move slowly. But management kept hiring bad people and losing talent. At some point the ship started to slow down. Those smart people quit to competitors and even some launched their own company that is growing fast. No bad employee was ever fired, their tasks were just allocated to the few good ones. Who started to quit en masse.
- Manjuuu 4y agoThat's a perfect metaphor.
- wmanley 4y agoI see what you mean: https://regmedia.co.uk/2021/01/05/simple_sabotage_field_manual.pdf https://regmedia.co.uk/2021/01/05/simple_sabotage_field_manu...
- ZooCow 4y agoOSS Simple Sabotage Field Manual https://archive.org/details/SimpleSabotageFieldManual/page/n17/mode/1up?view=theater https://archive.org/details/SimpleSabotageFieldManual/page/n... Pages 28-32 are the most referenced but the rest is interesting too.
- deleted 4y ago[deleted]
- VulgarExigency 4y agoThanks for sharing! I'll start putting everything here in practice immediately. Some of these are already widely practiced at the company I work for, though, so I probably won't stand out too much.
- JCharante 4y ago> Mock function calls until no original code runs. This one hurt personally. I didn't write it, we maintain it, but we have no time to go back and write real tests.
- VulgarExigency 4y agoAs I've become more experienced as a programmer, I've grown to hate unit tests that rely on mocks. They don't test a damn thing and they calcify code by making it a chore to update, since you have to update all the useless tests that don't do anything too.
- Manjuuu 4y agoThe "don't rock boats" is really what can slowly destroy companies. The -nx engineers know a lot of other -nx engineers that can come onboard until the stable boat just sinks.
- HPsquared 4y agoTo extend the boat analogy, I suppose it's impossible to know the stability of a boat without rocking it a bit.
- TrackerFF 4y agoIt's not that bad engineers only socialize with other bad engineers - but rather that many naïve and inexperienced engineers are much too kind, and will try to onboard every friend or relative they know, without ever having worked with them - they're basically vouching people blindly. This is something I've seen myself: Clueless manager hires the wrong man for the job -> wrong man is utterly clueless on how things work, what needs to be done, and flounders around for a couple of months -> wrong man decides that, hey, I know this one guy that seems to know his sh!t, let's get him onboard. Just fast-track him through the process. Turns out the new guy is also wrong man for the job, and doesn't know what to do. So now they're two (wrong) guys doing busywork while the ship is sinking.
- duxup 4y agoSometimes things just need to fail naturally and some rando on a mission to “rock the boat” is a net negative. Picking your fights is an important thing to learn too, throwing a fit over everything “wrong” can be terrible for everyone… even if you’re right every time.
- AnimalMuppet 4y agoPeople have limited bandwidth. Especially, it takes a lot longer to fix something than it does to just point out that it's broken. You can be right in every problem you point out, but if you point them out all at once, nobody can fix all that. Pick one and point it out (preferably also suggesting a path to fixing it), and then work with people to get it fixed. Keep your mouth shut about the others while this is going on.
- noobcoder 4y agoFrankly there's a kernel of truth in here. We've all worked with that one engineer who seems to have a knack for creating chaos and confusion. But let's not forget, it's also important to acknowledge the value of a good -1x engineer - they're the ones who make us appreciate the +1x engineers even more!
- DonHopkins 4y agoHere's Lars Brinkhoff studying to become a 10x programmer: https://twitter.com/larsbrinkhoff/status/1642569175657771009 https://twitter.com/larsbrinkhoff/status/1642569175657771009
- fvdessen 4y agoGood list but it's It's missing: - "use an new, different and exciting technology for each new project, however small"
- bdcravens 4y agoThe self-appointed "10xers" see this as a sign of greatness.
- nailer 4y ago- Add cool new tech to projects you're working on with ten other people. Ensure only one other person knows. - Name all your variables 'data'. - Copy and paste everywhere. People will think they've fixed a bug, and they have, but you've got seven slightly different copies of the function that needed fixing and now there's six left. - Take a project that's using one of those 'prettier' 'black' style tools to avoid bike-shedding discussions about linting. Change the options because you prefer different ones. Start a bike-shedding discussion about linting. - Use multiple divs for a single circle-shaped avatar.
- surement 4y ago> Name all your variables 'data'. Name a class "Entity" and make everything else derive from it. Write code that can't be deleted, ever.
- deafpolygon 4y agoEvery micro-managing managers ever.
- medo-bear 4y agoif 10x engineer writes in lisp, then that must mean that -10x engineer writes in forth
- rpastuszak 4y agoNormalize and support deviance: https://danluu.com/wat/ https://danluu.com/wat/
- davedx 4y ago> Trap 10 engineers in a futile skunkworks project. LOL, I thought I was cynical
- d--b 4y agoA lot of toxic negativity in that post. Sure bad engineers exist, but you know what is even worse than the -10x engineer: the contagious jerk. https://www.inc.com/jessica-stillman/studies-being-a-jerk-is-contagious.html https://www.inc.com/jessica-stillman/studies-being-a-jerk-is... Yep being an asshole spreads like a disease within organizations. Avoid these guys like the plague.
- infamouscow 4y agoStupidity is a moral failure. Derision of the stupid is morally justified: https://www.youtube.com/watch?v=ww47bR86wSc https://www.youtube.com/watch?v=ww47bR86wSc The study you linked assumes the actors are not stupid.
- surprisetalk 4y agoAuthor here. I don't want to empower jerks. Anything particular I should change? Or is the structure of the essay too cynical overall?
- s-j 4y agoThe article is good at making a point of what is bad and for the fun of it. However, it is not successful at compassionately explaining what one should strive to instead as there is no simple negation of the points being made.
- jerf 4y agoIt is not the responsibility of a person pointing out problems to also solve them. Granted, pointing out problems is generally much easier than solving them, and correspondingly less valuable. As I like to say, stand up, spin around, and point at something randomly. You're pointing at a problem of some sort. But that still does not incur a responsibility to someone pointing out a problem to also solve it. It's a popular idea for some reason but not one that can stand up to scrutiny of any kind.
- 4y ago
- tetromino_ 4y ago> To ensure developers are context-switching, recompilation should take at least 20 seconds. I'm now wondering what languages and projects the author has worked on if they expect compilation to take less than 20 seconds. Maybe small-ish golang projects? I don't remember the last time I worked on something interesting where recompilation was always under a minute...
- fedeb95 4y agothe real problem is build time with the windows filesystem (in my case). switching to wsl2 you get under 20 sec. pretty easily, and most projects > 20 seconds are fixable (that is, if someone fixes it). Deploy time, on the other hand...
- flippinburgers 4y agoWhat is your measure of interesting? Of "medium" sized? Go probably compiles 15K lines/sec.
- wazzaps 4y agoI worked hard on my previous project to achieve a 5sec build-run-test cycle for a medium-sized embedded C project (we don't have monster workstations, just some i7-10xxx/16GiB PCs). Thinking about proper modularization, runtime code (hot-re)loading, and eliminating single-point-of-recompilation for header files goes a long way. The gamedev industry figured this out a long time ago, see Handmade Hero's Hot reloading[0]. Also, an interactive shell (we use IPython) with all of the compiling and debugging utilities you need is easily a 5x efficiency boost, e.g. I can run `./devshell.py <NAME_OF_TARGET>`, then `run('foo', 'bar')` and the script will compile, upload, and re-execute the `foo` and `bar` modules. Makes onboarding much easier too. [0]: https://www.youtube.com/watch?v=Pax5jIz6m_Q https://www.youtube.com/watch?v=Pax5jIz6m_Q
- hardware2win 4y agoC# compiler has like tens of milions lines of code and it compiles in a minute or two So you either worked on the biggest codebases in the world Or youre doing CPP :)
- 4y ago
- vrglvrglvrgl 4y ago[dead]
- havblue 4y agoI've seen engineers who are good candidates for -10x... The moral of this story is, of course, if people are submitting work that creates more work, you must push back against them. Part of the issue is that intelligent people can be better at justifying work that wastes everyone's time. So if you're in a leadership position you really need to make sure people have their eyes on the prize and that they aren't padding their resume or needlessly doing tasks that worked at their previous job.
- darepublic 4y agoBike shed the crap out of everything in pr review (I have been guilty of this)
- londons_explore 4y agoI find it is always best to keep reviews minimal, and any review comments should generally be "this isn't ideal - consider doing it this other way next time - but LGTM". Sure, the end result is a less perfect codebase. But considering code isn't the end goal - a working product with happy users is the end goal - imperfect code can be the right way to achieve that. And besides, all code that is still in production in 5 years is probably due a rewrite anyway - now that the company has pivoted a few times, the product has evolved, and the use cases aren't what they originally were. The computing landscape will also have evolved (eg. new language versions, new library versions, new hardware with different strengths and weaknesses, etc)
- the_sleaze9 4y agoThere's a balance here, and for me it comes down to whether or not I'll be able to remember all of the narrow edge cases that this particular piece of code will introduce. Will braces around if statements matter when QA comes back with a regression 4 weeks from now or when Product has a new feature request? Probably not, so a "LGTM with a nit" is warranted. Adding a json request body to this GET request? Yeah, I'll have to remember that little bit of quirkiness, and quite frankly if the team member is adding bodies to GETs, I can't rely on them to remember that quirk or solve anything after that. So while that is technically a "style choice" since it does work, that's a blocked PR until Requested Changes are made.
- Jolter 4y agoWe must work in vastly different businesses. In five years, my company will still be selling similar products to the same customers — likely the same product’s successor model, and the code we write today may very well be the maintained legacy code then. To me, your approach sounds like hell because it means each line of that imperfect code will have caused a bug and/or forced a refactor commit.
- highmastdon 4y agoWouldn’t this be a x/10 engineer?