Human DevOps: Friday 15th March - How to be a Happier Software Engineer


As a lifelong coder and professional software geek, I've always been interested in the systems we use to build software. Lately, I've realised that these systems are often social — much more so than technical. Consequently, I've connected with the great and the good in the world of what I'm calling "humane software development". For me, this work is spearheaded by the work that Matthew Skelton and Manuel Pais have done with Team Topologies. Since the end of last year, I've been an official Team Topologies advocate, and since then I've started working with the core team on bringing the message of Team Topologies to a wider audience.

A key part of what makes Team Topologies so useful is the notion that Conway's Law is unavoidable. In other words, we build what our organisation, to some extent, allows us to build. Therefore, we can influence not only what we build but also how we build it by paying close attention to the teams we use to build the software and sensing how much stress they are under.

Therefore, part of my work is to understand, at an individual level, how I can improve my team's situation every day. Part of it is through hosting talks such as next week's Amsterdam Fast Flow Meetup. Some of it for me is through writing and connection.

Therefore, I've been exploring the social, organizational, and emotional side of building software. What makes us want to build it, and how can we do it together more effectively? When reading about this, it's easy to get very theoretical and as a practical, engineering type, I want solutions. Therefore, this week I wrote "How to be a Happier Software Engineer".

This post summarises where I'm going with this newsletter better than anything and hopefully gives you some practical tips on how we can have more fun and get more done at work.

If you're interested in how to be a happy software engineer, or how to make those around you happier, or basically looking to get more done and have more fun at work - then stick with me. If not, please click unsubscribe below and you won't hear from me again!

Many thanks and have a great weekend.

-- Richard


How to be a Happier Software Engineer

Published on March 12, 2024

It is incredibly powerful to realise that a single engineer can influence a team’s overall happiness and, by extension, their own happiness. But it can be frustrating sometimes can’t it? Sometimes, people just don’t get it, and sometimes, they don’t get you. Do you remember when you just built stuff? That feeling you get when… Read More »How to be a Happier Software Engineer

Read more...

The Human Software

Software systems rule our world. My regular newsletter explores the human factors that make software engineering so unique, so difficult, so important and all consuming.

Read more from The Human Software
The Human Software 283 - The Social Sciences and Conway's Law

Greg Wilson of Software Carpentry fame knows how to write a headline. His recent talk Cocaine and Conway's Law is a mine of brilliant ideas and books to add to your reading list. They talk invested me immediately through his excoriation of Mark Andreessen's "Techno Optimist Manifesto" as a part of the Peter Thiel/Elon Musk narrative - work harder and longer, fix all problems via tech. Conway's Law, for those who are unfamiliar is the implicit link between social organisation of a company and...

Human Software 282 - IT Failures Cost Lives

The Horizon Post Office Scandal is one of the biggest IT failures in recent times, directly responsible for thirteen of the wrongly accused taking their own lives after prosecutions were brought against them. There is a highly technical deep dive into the findings made by Computer Weekly in this incredible Corecursive podcast episode. It is worth a detailed listen if you want to understand how this could come about and what systemic failings caused it to be covered up for so long. Software...

The Human Software 281 - When Does Change Happen?

Working in software you get to see some pretty stupid stuff. And I mean crazy, stupid stuff. Decisions that float down from on high from multiple disparate spheres of influence - sales teams, other business units or just vice-presidents with a Great New Idea[tm] or a pet project. The narrative goes a little like this - the important people get to make choices and us techies have to live with consequences them. Sometimes these decisions are on a whim, an industry hype, a desperate attempt to...