There has been more discussion recently on the concept of a “10x engineer”. 10x engineers are, (from Quora) “the top tier of engineers that are 10x more productive than the average” Productivity I have observed that some people are able to get 10 times more done than me. However, I’d argue that individual productivity is... Read more »
In Praise of “Normal” Engineers
Software engineer Charity Majors challenges the "10x engineer" myth, arguing that true productivity lies in team performance, not individual brilliance. She encourages building workplaces where "normal" engineers can thrive. Are we focusing too much on hiring "the best" instead of the right people?
All the best engineering advice I stole from non-technical people
As I focus on becoming a better manager of engineers, I have been reflecting more and more on the advice that produced a 10X boost in my…
AI makes weak engineers less harmful
Like other kinds of puzzle-solving, software engineering ability is strongly heavy-tailed. The strongest engineers produce way more useful output than the average, and the weakest engineers often are actively net-negative: instead of moving projects along, they create problems that their colleagues have to spend time solving. That’s why many tech companies try to build a small, ludicrously well-paid team instead of a large team of more average engineers, and why so far this seems to be a winning strategy.
The 10 Best Practices for Remote Software Engineering
At face value, when we think of developer productivity we might think of effectiveness in time management, communication, and task completion.14 Although we are drawn to personal workflow or time management tools, and learning secrets to improving our productivity, ironically this quest for the holy grail can sometimes take us off course and be a detriment to our productivity. The problem is that accomplishing tasks or having a filled up schedule does not necessarily equate to productivity. Creating a formulaic working strategy, as was common in the last century, does not either.a,8,13 Productivity is less a quality that can be easily measured,b controlled, or improved directly with tools, but instead is a human element that manifests from developer happiness.
Doing nothing at work
Many engineers should be doing less work. I don’t necessarily mean producing less code or fewer changes, but literally working fewer hours in the day. When they do work, they should be working at a slower pace. I like to aim to be running at 80% utilization by default: unless I have a high-pressure project going on, I spend 20% of my workday away from the computer.
Undervalued Software Engineering Skills: Writing Well
I have been coaching several experienced software engineers to further grow professionally, since transitioning [https://blog.pragmaticengineer.com/things-ive-learned-transitioning-from-engineer-to-engineering-manager/] to being an engineering manager. I have noticed a few skills that people often underestimate the importance of developing. Skills that add a
The engineering manager's attention budget
Every Engineering Manager has 5 jobs - most distribute their 100 'attention points' across only 2-3 of them
Pure and impure software engineering
Why do solo game developers tend to get into fights with big tech engineers? Why do high-profile external hires to large companies often fizzle out? Why is AI-assisted development amazing for some engineers and completely useless for others?
The Biggest Mistake I See Engineers Make
Throughout my career, the biggest mistake I see engineers make is doing too much work on their own before looping in others. I’ve experienced this mistake as both an IC and a manager. As an IC, it’s a mistake I made many, many times early in my ow...
The Productivity Is Real. The Scaling Isn't.
What running an AI agent team taught me about why organizations can't do what one person can.
Engineering managers have a new job description
Why engineering managers are expected to be hands-on again and how AI tools are making it possible to stay technically sharp while still leading.
Does AI Actually Boost Developer Productivity? (100k Devs Study) - Yegor Denisov-Blanch, Stanford
Making 20% Time Work | begriffs.com
Following Google’s lead many companies have instituted “20% time” for their employees. This is one day per week in which employees can work on projects of their own choosing. The practice keeps developers motivated and sharp, produces tools to solve company problems, and in the best case creates open source which builds prestige and helps recruitment.
one of the reasons why I'm critical of "bigger models will solve this" is that cranking the output velocity of technician work sharpens the need for process work, which is the domain of expertise. process is incredibly hard to get right. most fields are bad at it. and it's *gaining* importance.
Ed
when it comes to LLMs, I have been trying to beat the technician/expert drum. LLMs are becoming master technicians, but they obviously lack integrative capabilities to deploy expertise. but I'm starting to realize that a lot of people don't understand, or don't value the difference.
daniel: "I don't think we need 10x developers to build great things. I think we need 10x teams – groups of people who care about the same problem, who iterate together, and who make each other better" 🤍
daniel r(ooooooh) 👻
wrote a few words on why I think @npmx.dev might be going places
