- Complexity has to live somewhere. If you are lucky, it lives in well-defined places: in code where you decided a bit of complexity should go, in documentation that supports the code, and in training sessions for your engineers. You give it a place without trying to hide all of it; if you pretend complexity can be avoided altogether, it has nowhere to go, but it still doesn’t stop existing. ferd.ca/complexity-has-to-live-somewhere.html
- How do you ask good questions? Be highly specific, show that you are truly listening, and make it hard for the other person to give a vague answer. Offer a little of your own thinking first, so the other person is encouraged to answer with equal seriousness. marginalrevolution.com/marginalrevolution/2021/06/how-do-you-ask-good-questions.html
- New technology waves can make or break your business, but only some of the bumps in the water actually matter. The greatest sin of technology waves is missing an obvious wave and pretending it wasn’t real because of your ego. If you miss a wave, the single most important step is to swallow your pride and immediately take strides to catch up. blog.staysaasy.com/p/riding-technology-waves
- You don’t really understand software until you’ve watched it run, fail, and surprise you in production. And you don’t really learn to build it well until you’ve had to repair someone else’s broken pieces under pressure. That is what being oncall gives you: direct contact with reality. yaoyue.org/blog/2026-oncall
- A useful tool to understand how food gets traded around the world. ourworldindata.org/how-does-food-get-traded-around-the-world
What I’ve been reading (W27, 2026)
Complexity in software, asking better questions, riding technology waves, being oncall reality, and food-trade dependencies