A breakdown of what software development teams actually cost, what they need to generate to be financially viable, and why most organizations have no visibility into either number.
How teams build – Linear
AI usage patterns in software teams: who is adopting AI, how it reshapes where teams spend their time, and how much more they ship.
A Guide to Measuring Engineering Team Performance
“You can’t manage what you can’t measure.” While software development practices constantly change, there will always be a tier of truly top engineering teams who stand above…
Reasons to hire inexperienced engineers
There are many reasons to consider hiring inexperienced software engineers into your team, beyond the commonly discussed factors of cost and social responsibility. Hire to maximise team effectiveness; not to maximise team size. Adding more people increases the communication and synchronisation overhead in the team. Growing a team has rapidly diminishing returns. However, adding the... Read more »
Habits of High-Functioning Teams
I often struggle to explain what it means to be part of a high-functioning software team. Sure, there are mountains of literature, and an entire genre of LinkedIn thought leadership that professes all kinds of guidelines and heuristics about what makes teams work, but in my experience, it’s hard to internalize these ideas and follow someone else’s model if you’ve never seen what good looks like.
The $70B Open Source Software Paradox
It’s no news that over the last 10-15 years, particularly noticeable in the last 5 years, the enterprise software industry has gradually transformed from complex, expensive, closed-source (proprietary) software stacks to extensible/configurable,...
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?
Theory and Memory: Two Forces Shaping Software Team Knowledge
How insights from cognitive science and social psychology explain why software knowledge is so hard to preserve
The developer’s dilemma
When it comes to making money, software developers are an odd bunch. Developers produce code, and code is in high demand. At a glance, it…
Why AI Makes Things Worse for Enterprise Teams, by Paul Ford
Why are so few engineering teams reaping the benefits of AI? On this week’s episode, Paul presents Rich with the findings from a recent report from CircleCI and
Laws of Software Engineering
A collection of principles and patterns that shape software systems, teams, and decisions.
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.
Augment Code Pricing - Plans for Teams and Enterprise
Simple, transparent pricing for AI-powered development. Plans for individuals, teams, and enterprise.
Why Open Source Software / Free Software (OSS/FS, FOSS, or FLOSS)? Look at the Numbers!
This paper provides quantitative data that, in many cases, open source software / free software is equal to or superior to their proprietary competition. The paper examines market share, reliability, performance, scalability, scaleability, security, and total cost of ownership; it also comments on non-quantitative issues and unnecessary fears.
5 ways open source software companies make money
A guide on how to evaluate the long-term sustainability of the business behind any open-source software you are using (or considering working on yourself).
What We Know We Don't Know: Empirical Software Engineering
Empirical Software Engineering is the study of what actually works in programming. Instead of trusting our instincts we collect data, run studies, and peer-review our results. This talk is all about how we empirically find the facts in software and some of the challenges we face, with a particular focus on software defects and productivity. Talk doesn’t seem to be online yet; in the meantime, you can see a recording of an older version of the talk here.
Open Source is a cost-allocation system
Because the right to use the software is not tied to payment, the license does not connect the people who benefit, the people who decide, and the people who bear the costs. Projects have to build those connections deliberately through governance.
