Logo
Join the CTO Newsletter for free!
 
Amazing CTO Logo

Amazing CTO | More happiness and success
🚀 86.3

by Stephan Schmidt

Happy 🌞 Sunday,

Welcome to Stephans opinionated newsletter. This week’s insights

  • 🐞 Ladybird Web Browser will shatter the browser landscape
  • 🚢 Having a tech vision: The dream of an alpine waterway
  • 🧠 People are vastly overestimating generative AI

Developer Productivity - again, but with a 🪀YoYo!

This is from my Keynote at the T3 Engineering Leadership Summit in Berlin

Did you ever think about developer productivity? Did you ever wonder why we still talk about developer productivity in 2024? I was recently at the beach thinking about this. When I was CTO of a startup in 1999 we developed features as fast as today. Adding a form took the same time. Storing data to the database took the same effort.

We had so many productivity gains over the last decades though. We got Git which is much better and more productive than CVS/Subversion - especially with merging. We have much faster computers. SSDs are blazingly fast and Apple Silicon has great memory bandwidth. Compile times are more than 10x faster (2x just with a faster SSD) compared to 25 years ago. Running tests is faster. We have a better developer ecosystem. We have better frameworks and tools, like Redis. We have better programming languages like Typescript and Go. And existing ones like Java, Python and JavaScript evolved tremendously. Less code for faster development. Then we have Docker, easy CI/CD on GitHub and hosting in the cloud on AWS.

We should be developing a lot faster than before.

We are not. This is a mystery.

So I kept thinking. And thinking. And discovered the Productivity 🪀Yo-Yo Effect. Let me explain.

At the same time that we gained productivity, we added things that drained productivity. We could, as we had gained productivity. We got into Scrum with its many meetings. Developers have more meetings with more stakeholders than ever. We have too many tools, look at JavaScript bundlers and web frameworks. We have complex cloud setups, many CTOs I meet had and have misconfigured AWS setups. We have mobile with additional teams. And we have SPAs. It is no longer enough to add a new feature to one place in your code, you now have to change backend code, change the API, change the frontend SPA code, change the mobile iOS code and the Android code. And if your mobile app has its own API to the backend, you might need to change that too.

We added lots of unproductivity.

But one wonders, why did productivity stay flat, why did’t it go down and down and down.

The reason is simple. The Productivity 🪀Yo-Yo effect. We add as much unproductivity as we can, as a luxury to get other benefits than development speed. Until we feel bad or get pushback. Then we stop and do more productive things again. We give pushback to the many Scrum meetings. We drop them. We replaces SPAs with HTMX. We move back from Microservices to Moduliths. We replace iOS and Android apps with Flutter. We drop Typescript and move back to plain JavaScript.

The Productivity 🪀Yo-Yo Effect keeps developers at an acceptable productivity level.

So whatever you invest in developer productivity, keep the Productivity 🪀Yo-Yo Effect in mind!

Everything In one picture:

Productivity YoYo

Good reading, have a nice Sunday ❤️ and a great week,

Stephan
CTO-Coach and CTO-veteran

🎁

If you only read one thing

🚢 The dream of an alpine waterway (20 minute read)

What a vision. Building a waterway across the alps! It failed, of course. But the vision was great. At the T3 Leadership Summit, I had a discussion about how to get engineers in the office. If you have a grand vision that is inspiring, you will get the best engineers, and to do something great, they’ll work in the office. If you are another mobile app with a database backend, not so. Work on your vision. Work on your engineering vision! (The waterway is an engineering vision).

Most tech departments I look into lack a tech vision. Or have one which is outdated and never referenced. Have a great tech vision and you will attract great people. And do something that matters. Not another dating app.

https://blog.nationalmuseum.ch/en/2024/06/the-dream-of-an-alpine-waterway/

🚀

Stories I’ve enjoyed this week

🐞 Ladybird Web Browser becomes a non-profit with $1 Million from GitHub Founder (5 minute read)

This is huge. It will change the web landscape. Ladybird is a new browser without using Googles HTML engine like most others do. People said it can’t be done, one developer creating a new browser without using Chromes rendering engine. But Andreas proved them wrong. Now he got $1M in financing. Firefox dropped the ball a long time ago; they were more interested in having a nice life with high salaries, instead of driving their browser to new heights. Firefox squandered more than $6.000.000.000 in money. There has been no real innovation in browsers the last ten years. Ladybird will take up the ball and bring back innovation. The IE6 browser wars will be back. If you like it or not.

https://lunduke.locals.com/post/5812560/ladybird-web-browser-becomes-a-non-profit-with-1-million-from-github-founder

🧠 MIT robotics pioneer Rodney Brooks thinks people are vastly overestimating generative AI (22 minute read)

I do think people overestimate AI in the short run, and vastly underestimate AI in the 10 to 20 years time frame. AI will blow everything away.

https://techcrunch.com/2024/06/29/mit-robotics-pioneer-rodney-brooks-thinks-people-are-vastly-overestimating-generative-ai/?guccounter=1

dolt fetch Gets Much Faster (15 minute read)

Dolt is a database, and it is getting faster by using async co-routines. I recently wrote a small framework (ha!) for Inkmi that renders parts of a page in different go-routines, with the nice side effect of Go parking IO go-routines automatically. Nice. Which, in the end, reduces service times for a request. As shown in one of my last newsletters, this does decrease latency a lot and makes for a much better (faster) user experience. Not enough people leverage async page rendering, or async parallel work in general. Do your devs?

https://www.dolthub.com/blog/2024-05-08-dolt-new-puller/

Einstein and his peers were ‘irrationally resistant’ to black holes. This illustrated story explores why (10 minute read)

Once a physics professor at university told me, people don’t change their mind. Science only changes because these people die of old age. One physicist said about the proposal of black wholes, *“Various accidents may intervene to save the star [..] but I want more protection than that. I think there should be a law of Nature to prevent a star from behaving in this absurd way!” Engineers are sometimes like this—they have problems accepting new realities. This was when we moved from manual memory management with malloc/free to garbage collection in Java. And it happened when we moved from command hierarchies (“Tell me what to do!”) to Agile. And it will happen with AI.

https://www.bbc.com/future/article/20240619-why-albert-einstein-rejected-black-holes-singularities-illustrated-story

A Eulogy for DevOps (28 minute read)

A very long text on DevOps. Did it fail or not? Coming from a time with silos and huge gaps between operations and development, I would say it succeeded. Even if no one knows what DevOps means (like Agile). Developers today deploy on their own, and infrastructure as code is the standard. Development changed for the better. Even perhaps if DevOps never achieved, what it was set out to do. The movement is gone and has folded into mainstream-as they always do.

https://matduggan.com/a-eulogy-for-devops/

Join the CTO newsletter!
Impressum