"The onset of the automobile was a revelation for access and personal liberty. But as time wore on and the proliferation of the automobile progressed, its marginal utility diminished — offering fewer & fewer benefits, and taking more & more in exchange. henry.codes/writing/a-we...

I don't, I clearly say that it is a lack of respect to want me to review code you didn't even bother to check yourself.
Review it yourself and come to me when you're sure you did your best to do it right the first time.

NixOS looks cool indeed!

Dreams of Autonomy told about Nix on MacOS, but you may make me want to have the whole OS experience!

www.youtube.com/watch?v=Z8BL...

A quick recap on what you enjoyed? 🙂

Interested too to go full Linux

A masterpiece. Thank you for reminding me why I enjoyed the web so much back when I started coding. It reminded me the lecture of resilient web design.

"convivial tools are sustainable, energy-efficient, local-first, and designed primarily to enhance the autonomy and creativity of their users" ✊🏽

Made my first article on the Toyota production system! thinking-people-system.house with the pull system: thinking-people-system.house/pull-system

I'm in!

In "The Toyota Way of Dantotsu Radical Quality Improvement", QA teams don’t just report defects—they help teams address root causes. They empower, rather than take responsibility away. That's the true value of QA.

And what about QA? Should we remove it entirely? No, but it can evolve: instead of just detecting defects, it can help improve quality within the flow.

Identifying autonomy zones and ensuring that production & inspection happen in the same place is key in a healthy environment. Developers should be able to check if the product is ok.

The downside is that it creates a bad reinforcing loop: the more QA is present, the less developers take ownership of quality—leading to an even greater need for QA. 🔄

Adding lead time in rework and lack of focus for everyone.