<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Engineering on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/engineering/</link>
    <description>Recent content in Engineering on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 05 Mar 2025 10:55:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI-Native Development: What It Actually Means to Use These Tools Well</title>
      <link>https://blog.turboawesome.win/2025/03/ai-native-development-what-it-actually-means-to-use-these-tools-well/</link>
      <pubDate>Wed, 05 Mar 2025 10:55:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2025/03/ai-native-development-what-it-actually-means-to-use-these-tools-well/</guid>
      <description>AI coding tools have changed the texture of software development. Not by writing code for you, but by changing what&amp;#39;s worth doing yourself and what isn&amp;#39;t. A practitioner&amp;#39;s view of where the leverage actually is.</description>
    </item>
    <item>
      <title>Building with AI Coding Tools: What Actually Changes and What Doesn&#39;t</title>
      <link>https://blog.turboawesome.win/2025/01/building-with-ai-coding-tools-what-actually-changes-and-what-doesnt/</link>
      <pubDate>Wed, 22 Jan 2025 10:08:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2025/01/building-with-ai-coding-tools-what-actually-changes-and-what-doesnt/</guid>
      <description>A year into using AI coding assistants seriously: what they&amp;#39;ve changed about how I work, where they still fall short, and the habits that make the difference between AI as a demo and AI as a productivity multiplier.</description>
    </item>
    <item>
      <title>Cross-Team Technical Alignment at Scale</title>
      <link>https://blog.turboawesome.win/2024/11/cross-team-technical-alignment-at-scale/</link>
      <pubDate>Wed, 20 Nov 2024 10:30:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2024/11/cross-team-technical-alignment-at-scale/</guid>
      <description>Getting multiple engineering teams to agree on technical direction is hard. The approaches that work — architecture forums, decision records, working groups — and why lightweight coordination beats heavy governance.</description>
    </item>
    <item>
      <title>Writing RFCs for Wide Audiences</title>
      <link>https://blog.turboawesome.win/2024/08/writing-rfcs-for-wide-audiences/</link>
      <pubDate>Wed, 21 Aug 2024 09:45:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2024/08/writing-rfcs-for-wide-audiences/</guid>
      <description>RFCs that need sign-off from multiple teams or leadership require a different structure than internal team proposals. The writing changes when the audience includes people who don&amp;#39;t share your context.</description>
    </item>
    <item>
      <title>Engineering at Enterprise Scale: What Changes When the System Is Actually Big</title>
      <link>https://blog.turboawesome.win/2024/02/engineering-at-enterprise-scale-what-changes-when-the-system-is-actually-big/</link>
      <pubDate>Wed, 14 Feb 2024 10:22:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2024/02/engineering-at-enterprise-scale-what-changes-when-the-system-is-actually-big/</guid>
      <description>After a decade in financial technology — trading firms, institutions, a startup, a European fintech — joining a large US technology company. The technical and organisational delta.</description>
    </item>
    <item>
      <title>Eleven Years In: A Retrospective on Careers, Choices, and Compounding Knowledge</title>
      <link>https://blog.turboawesome.win/2023/11/eleven-years-in-a-retrospective-on-careers-choices-and-compounding-knowledge/</link>
      <pubDate>Wed, 15 Nov 2023 15:41:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2023/11/eleven-years-in-a-retrospective-on-careers-choices-and-compounding-knowledge/</guid>
      <description>Eleven years of software engineering across trading firms, financial institutions, startups, and large technology companies. What compounds, what doesn&amp;#39;t, and the decisions I&amp;#39;d make differently.</description>
    </item>
    <item>
      <title>Navigating Org Change as an Engineer</title>
      <link>https://blog.turboawesome.win/2023/08/navigating-org-change-as-an-engineer/</link>
      <pubDate>Wed, 16 Aug 2023 11:20:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2023/08/navigating-org-change-as-an-engineer/</guid>
      <description>Reorganisations, leadership changes, and strategy shifts are facts of life in growing companies. The engineers who navigate them well share some common practices — and some common misconceptions about what&amp;#39;s actually changing.</description>
    </item>
    <item>
      <title>Postmortems as a Learning Tool: Structure, Culture, and Follow-Through</title>
      <link>https://blog.turboawesome.win/2022/10/postmortems-as-a-learning-tool-structure-culture-and-follow-through/</link>
      <pubDate>Wed, 05 Oct 2022 11:27:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/10/postmortems-as-a-learning-tool-structure-culture-and-follow-through/</guid>
      <description>A postmortem that concludes with &amp;#39;be more careful&amp;#39; has failed. The structure and culture of blameless postmortems, and why follow-through is where most teams fall short.</description>
    </item>
    <item>
      <title>Engineering Roadmaps: Planning for Uncertainty</title>
      <link>https://blog.turboawesome.win/2022/02/engineering-roadmaps-planning-for-uncertainty/</link>
      <pubDate>Wed, 16 Feb 2022 09:30:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/02/engineering-roadmaps-planning-for-uncertainty/</guid>
      <description>Engineering roadmaps are commitments made under uncertainty. The planning practices that keep them honest — time horizon discipline, explicit uncertainty, and the difference between a roadmap and a plan.</description>
    </item>
    <item>
      <title>Technical Debt Is a Balance Sheet Item, Not a Moral Failing</title>
      <link>https://blog.turboawesome.win/2021/10/technical-debt-is-a-balance-sheet-item-not-a-moral-failing/</link>
      <pubDate>Wed, 06 Oct 2021 10:18:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/10/technical-debt-is-a-balance-sheet-item-not-a-moral-failing/</guid>
      <description>The language around technical debt is usually moral: &amp;#39;bad code&amp;#39;, &amp;#39;dirty shortcuts&amp;#39;, &amp;#39;cutting corners&amp;#39;. The financial metaphor it&amp;#39;s named after is actually more useful. Debt is a tool. Manage it like one.</description>
    </item>
    <item>
      <title>Hiring Senior Engineers: What the Interview Loop Can&#39;t Tell You</title>
      <link>https://blog.turboawesome.win/2021/07/hiring-senior-engineers-what-the-interview-loop-cant-tell-you/</link>
      <pubDate>Wed, 07 Jul 2021 14:02:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/07/hiring-senior-engineers-what-the-interview-loop-cant-tell-you/</guid>
      <description>After running hiring loops for senior engineers at the European fintech firm, the pattern was clear: the things that determined whether a hire was successful were almost never well-measured by our interview process.</description>
    </item>
    <item>
      <title>After the Startup: Joining a Larger Organisation Without Losing Your Mind</title>
      <link>https://blog.turboawesome.win/2021/03/after-the-startup-joining-a-larger-organisation-without-losing-your-mind/</link>
      <pubDate>Wed, 17 Mar 2021 09:11:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/03/after-the-startup-joining-a-larger-organisation-without-losing-your-mind/</guid>
      <description>Two years into a fast-moving startup, I joined a larger, more structured European financial technology firm. The culture delta was significant in both directions.</description>
    </item>
    <item>
      <title>Writing Technical RFCs That Actually Get Read</title>
      <link>https://blog.turboawesome.win/2021/02/writing-technical-rfcs-that-actually-get-read/</link>
      <pubDate>Wed, 24 Feb 2021 09:07:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/02/writing-technical-rfcs-that-actually-get-read/</guid>
      <description>Most technical RFCs fail at their primary purpose: creating alignment before building. The failures are almost always structural — missing context, buried decisions, or no clear ask. Here&amp;#39;s the format that worked.</description>
    </item>
    <item>
      <title>Engineering Velocity at a Startup: What Actually Made Us Fast</title>
      <link>https://blog.turboawesome.win/2021/02/engineering-velocity-at-a-startup-what-actually-made-us-fast/</link>
      <pubDate>Tue, 09 Feb 2021 13:41:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2021/02/engineering-velocity-at-a-startup-what-actually-made-us-fast/</guid>
      <description>After two years at a fast-moving fintech startup, the things that actually determined how quickly we shipped were not the tools or the process — they were much simpler and harder to fix than that.</description>
    </item>
    <item>
      <title>The Platform vs Product Tension in a Growing Startup</title>
      <link>https://blog.turboawesome.win/2020/08/the-platform-vs-product-tension-in-a-growing-startup/</link>
      <pubDate>Wed, 12 Aug 2020 10:45:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2020/08/the-platform-vs-product-tension-in-a-growing-startup/</guid>
      <description>Every startup engineering team eventually faces the platform question: invest in the foundation or keep shipping features? The tension is real, the tradeoffs are non-obvious, and the wrong answer in either direction is costly.</description>
    </item>
    <item>
      <title>What Big-Bank Engineering Taught Me About System Design</title>
      <link>https://blog.turboawesome.win/2018/08/what-big-bank-engineering-taught-me-about-system-design/</link>
      <pubDate>Thu, 23 Aug 2018 13:51:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2018/08/what-big-bank-engineering-taught-me-about-system-design/</guid>
      <description>Three years at a large financial institution changed how I think about failure, compliance, and the relationship between constraints and good design. Not all of the lessons are obvious.</description>
    </item>
  </channel>
</rss>
