Fundamentals of Trust in Engineering 0 ▲ Luminousmen Blog - Python, Data Engineering & Machine Learning 102 days ago · Tech · hide · Fediverse post We usually talk about engineering like it's a technical discipline. We focus on the technical aspects — algorithms, data structures, distributed systems, the right partition key, etc. It's not wrong to think about it this way, but underneath it tells a different story. Engineering is Based on Trust. I don't mean that in some philosophical sense. I mean it quite literally. Everything you'd point to as "the work" — the architecture diagram, the CI/CD pipeline, the on-call rotation, the promo packet — is really a stand in for the questions of who and what you can rely on. Underneath, trust is one specific thing: the moment people stop checking your work. It's permission to not be verified — a teammate who reads less of your code, a manager who double-checks less of your work, a user who keeps clicking without re-reading the terms. Almost everything fast in engineering runs on it. Without that permission even good code gets second-guessed and Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town