100 tweets on "software developer productivity" for this year's @threadapalooza

I’m attending @ApidaysHelsinki today and have few copies of ”Build: Elements of an Effective Software Organization” with me. Come say hi, if you’re interested in engineering effectiveness or developer productivy! #apidaysHelsinki @APIdaysGlobal

The 1st edition of the book ran out of print in a few days. The second edition is out in print and on Kindle! Really proud of how this turned out. This gem is the result of hours of feedback, editing and discussions. 👏

7 principles 9 ways I've learned to improve how you ship software First the 7 principles: 1. Speed When it comes to deploys speed is safety, and small is speed. The speed of shipping has massive compounding effects. If your deploy takes hours, you’re going to want to make damn sure there are no bugs, because if you find a critical bug right after a deploy goes live, then you have to wait another couple hours for your fix to go live.

The most popular browsers in each country. 2012 vs 2022

It takes years to build a reputation… ….and only one ChatGPT blog post to ruin it.

If looking for a design system for a new project React Aria is worth a look! Impressive how all of these components are decoupled from Adobe's own Spectrum Design system.

🎁 Before we put a bow on 2023, we wanted to thank our amazing customers and the team for another great year, during which we: · Shipped 9 major features · Welcomed a record number of new customers · … and much more! Check out our full year in review: swarmia.co/482bUAr

I also tend to dislike functions that accept a boolean/enum as an argument if they radically change the behavior of the function. Just write two functions!

This is the best LLM intro I've seen this far. 👌

Stately Studio 2.0 is our transition to the visual software modeling tool for every dev team, no matter which libraries/frameworks/languages you're using. We want to make it easy for everyone to understand & manage logic at any level of complexity. More coming soon 🚀

Put your last name in the GIF search and post the first one that pops up. 🍿

The fact that VSCode began as a web app, then became a desktop app, then became a web app again and then even got remote (ssh) functionality is a testament of how adaptive the codebase is. It's adaptive because they use dependency injection really well. You can replace, mix & match any part of VSCode, while keeping the main functionality (github.com/codingame/monaco-… is a testament to this). That was also why it was so easy to integrate VSCode with CodeSandbox and make it work in the browser. You can replace services like the FileService one by one with browser compatible versions. I'm also impressed with its performance. They're doing everything imperatively, which is a pain, but it does make it easier to ensure that you never do more DOM operations than you should. Because imperative UI is a pain, they've created a lot of primitives like virtualized lists, quickinput, etc with a good API to easily compose UIs Finally, the editor feels fast even with many extensions, because they run extensions in a separate thread. How does UI work then? The extension tells VSCode over the wire using the same primitives how UI should look, and VSCode renders those elements in a performant, consistent and accessible way. This is why Atom started to feel slower than VSCode after a while. It was not Atom that was slowing down, it was the extensions taking CPU from the main thread.

Being "affected" wasn't on my bingo card for 2023, but last week I was laid off along with the rest of the @partykit_io team. What I'll miss the most getting to work with my friends 💔 I'm open to new opportunities in the new year — DM me if you want to work together!

If you go into building custom GPTs with the expectation that your custom instructions and the data you upload to them will be leaked to anyone who tries hard enough, you'll make much better decisions about how to safely create them

abc123!42069

It always surprises me how a 5 min CI build feels like 100x faster than a 20 min one.

We've written a book! Yes, a real one. And no, it's not just an extended blog post created with ChatGPT. We're excited to introduce "Build – Elements of an Effective Software Organization." In light of the recent buzz in the development productivity space, particularly following the McKinsey report, we believed it was timely to share our insights on infusing greater transparency into engineering organizations. We discuss this through the lenses of Business Outcomes, Developer Productivity, and Developer Experience. This book is the culmination of incredible efforts by my colleagues @rmurphey, @APKoponen, @pinjaerika, Oskari Kallio, and many others. The first print edition has already been snapped up (save for the five upside-down copies I’m keeping as collectibles), but you can read it online until we restock the printed version: swarmia.com/build/

If the hard times make you softer towards other people, you've succeeded.

Thanks for having me, this was fun!