--- title: Fundamentals of Trust in Engineering | daily.dev description: Engineering is fundamentally built on trust — the moment people stop checking your work. This piece explores how trust operates across five dimensions: with... canonical: https://daily.dev/posts/fundamentals-of-trust-in-engineering-mgjswyzfw twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Fundamentals of Trust in Engineering | daily.dev og:description: Engineering is fundamentally built on trust — the moment people stop checking your work. This piece explores how trust operates across five dimensions: with... og:url: https://daily.dev/posts/fundamentals-of-trust-in-engineering-mgjswyzfw og:image: https://api.daily.dev/og/posts/mGJswYzfW.png og:image:alt: Fundamentals of Trust in Engineering og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Fundamentals of Trust in Engineering **[iamluminousmen](https://daily.dev/sources/luminousmen)** · 10 min read · 1 upvotes · 0 comments ## Summary Engineering is fundamentally built on trust — the moment people stop checking your work. This piece explores how trust operates across five dimensions: with teammates (built through reliability and honesty, lost instantly with one lie), with managers (those trusted with ambiguity get high-leverage work and promotions), with tools and AI (trust as far as you can cheaply verify and survive being wrong), with third-party systems (dependency trust is transitive and you control none of it — use timeouts, circuit breakers, pinned versions), and with data (a dashboard nobody believes is worse than no dashboard). The core insight: trust is slow to earn, fast to lose, and worth more than almost any technical decision. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why do senior engineers get their PRs approved faster even for large changes? Senior engineers get faster PR approvals because reviewers have already built a mental model of them through past interactions. A reviewer skims the code and checks only the parts that worry them, because they've already 'reviewed the person' — they know this engineer tests edge cases, flags risky changes proactively, and doesn't claim something is done when it isn't. The first PR from anyone gets a full, slow, suspicious review. _Engineers navigating code review dynamics and team reputation find the broader conversation on daily.dev._ ### How should I decide how much to trust an LLM to write production code? Trust an LLM exactly as far as you can cheaply verify its output and survive it being wrong. An LLM writing a regex or a throwaway test is low-risk — you can read the output in seconds and a mistake causes no lasting damage. Letting an LLM quietly rewrite a financial calculation you won't check is high-risk — a wrong answer can sit undetected for months doing real damage. The same framework applies to compilers, ORMs, and autoscalers. _Developers calibrating AI tool use in production codebases track these trade-offs on daily.dev._ ### What are the real risks of transitive dependencies in software projects and how do I mitigate them? Transitive dependency trust is inherited but unverified — you audit almost none of the tree. Left-pad's removal broke half the internet's builds from eleven lines of code; Log4Shell forced every team to prove a negative over a weekend; the xz backdoor was inserted by an attacker who spent years earning maintainer trust through clean commits. Mitigations include timeouts, circuit breakers, pinned versions, and vendoring only the specific lines you actually use rather than importing an entire library. _Supply chain incidents like these surface quickly for developers watching the space on daily.dev._ ## Similar posts on daily.dev - [Trust Is the Real Deliverable](https://daily.dev/posts/trust-is-the-real-deliverable-fc1ktnkoz) · Atomic Spin · 0 upvotes · 0 comments - [Why engineers lose trust in AI-coding tools](https://daily.dev/posts/why-engineers-lose-trust-in-ai-coding-tools-kuan22f27) · LeadDev · 0 upvotes · 0 comments - [The Quiet Discipline of Great Engineering Teams](https://daily.dev/posts/the-quiet-discipline-of-great-engineering-teams-dlmkpcsx0) · Tech Lead Digest · 3 upvotes · 0 comments - [Building AI tools for people who don’t trust AI](https://daily.dev/posts/building-ai-tools-for-people-who-don-t-trust-ai-pcosdyqvp) · Medium · 0 upvotes · 0 comments --- Tags: [#career](https://daily.dev/tags/career), [#distributed-systems](https://daily.dev/tags/distributed-systems), [#data-engineering](https://daily.dev/tags/data-engineering), [#company-culture](https://daily.dev/tags/company-culture) [View this post on daily.dev](https://daily.dev/posts/fundamentals-of-trust-in-engineering-mgjswyzfw) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Fundamentals of Trust in Engineering","url":"https://daily.dev/posts/fundamentals-of-trust-in-engineering-mgjswyzfw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/fundamentals-of-trust-in-engineering-mgjswyzfw"},"datePublished":"2026-08-10T22:24:07.980Z","dateModified":"2026-09-14T08:05:53.438Z","description":"Engineering is fundamentally built on trust — the moment people stop checking your work. This piece explores how trust operates across five dimensions: with...","image":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","thumbnailUrl":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","isAccessibleForFree":true,"articleSection":"iamluminousmen","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"iamluminousmen","logo":"https://media.daily.dev/image/upload/s--hreDkl91--/f_auto,q_auto/v1779608564/logos/luminousmen","url":"https://daily.dev/sources/luminousmen"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/fundamentals-of-trust-in-engineering-mgjswyzfw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"career,distributed-systems,data-engineering,company-culture","timeRequired":"PT10M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"iamluminousmen","item":"https://daily.dev/sources/luminousmen"},{"@type":"ListItem","position":3,"name":"Fundamentals of Trust in Engineering"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/fundamentals-of-trust-in-engineering-mgjswyzfw#faq","mainEntity":[{"@type":"Question","name":"Why do senior engineers get their PRs approved faster even for large changes?","acceptedAnswer":{"@type":"Answer","text":"Senior engineers get faster PR approvals because reviewers have already built a mental model of them through past interactions. A reviewer skims the code and checks only the parts that worry them, because they've already 'reviewed the person' — they know this engineer tests edge cases, flags risky changes proactively, and doesn't claim something is done when it isn't. The first PR from anyone gets a full, slow, suspicious review. Engineers navigating code review dynamics and team reputation find the broader conversation on daily.dev."}},{"@type":"Question","name":"How should I decide how much to trust an LLM to write production code?","acceptedAnswer":{"@type":"Answer","text":"Trust an LLM exactly as far as you can cheaply verify its output and survive it being wrong. An LLM writing a regex or a throwaway test is low-risk — you can read the output in seconds and a mistake causes no lasting damage. Letting an LLM quietly rewrite a financial calculation you won't check is high-risk — a wrong answer can sit undetected for months doing real damage. The same framework applies to compilers, ORMs, and autoscalers. Developers calibrating AI tool use in production codebases track these trade-offs on daily.dev."}},{"@type":"Question","name":"What are the real risks of transitive dependencies in software projects and how do I mitigate them?","acceptedAnswer":{"@type":"Answer","text":"Transitive dependency trust is inherited but unverified — you audit almost none of the tree. Left-pad's removal broke half the internet's builds from eleven lines of code; Log4Shell forced every team to prove a negative over a weekend; the xz backdoor was inserted by an attacker who spent years earning maintainer trust through clean commits. Mitigations include timeouts, circuit breakers, pinned versions, and vendoring only the specific lines you actually use rather than importing an entire library. Supply chain incidents like these surface quickly for developers watching the space on daily.dev."}}]} ```