<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aramide Otenaike on Medium]]></title>
        <description><![CDATA[Stories by Aramide Otenaike on Medium]]></description>
        <link>https://medium.com/@aramideotenaike?source=rss-3b3725b11ff1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wZz3uaO72IZ0Xcjrh8Tg-g.jpeg</url>
            <title>Stories by Aramide Otenaike on Medium</title>
            <link>https://medium.com/@aramideotenaike?source=rss-3b3725b11ff1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:55:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aramideotenaike/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Software Planning and Documentation]]></title>
            <link>https://medium.com/@aramideotenaike/software-planning-and-documentation-ea871c402185?source=rss-3b3725b11ff1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea871c402185</guid>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Aramide Otenaike]]></dc:creator>
            <pubDate>Thu, 28 Aug 2025 10:20:25 GMT</pubDate>
            <atom:updated>2025-08-28T10:20:25.551Z</atom:updated>
            <content:encoded><![CDATA[<p>A personal guide to building software with clarity and direction.</p><p>When I first started digging into how to build personal projects, my instinct was to jump straight into code. But as I read more, I realized something important: <strong><em>building software without a plan is a lot like trying to build a house without a blueprint.</em></strong></p><p>Sure, you could start hammering walls together, but eventually you’d forget where the bathroom should go, or realize the kitchen has no door. That’s where <strong>documentation</strong> comes in — it’s the blueprint.</p><p>Documentation answers two simple but powerful questions:</p><ol><li><strong>What should the product be like?</strong></li><li><strong>How are we going to build it?</strong></li></ol><p><strong><em>The What</em></strong>: <strong>Product Documentation</strong></p><p>This is the architect’s drawing. It captures the vision of the product: what it does, how it feels, and the qualities it must have.</p><ul><li><strong>Functional Requirements</strong> → The “rooms” in the house. Each one has a clear purpose: bedroom, kitchen, bathroom. In software terms, these are the features.</li><li><strong>Non-Functional Requirements</strong> → The things that make the house livable: solid walls, good lighting, safe wiring. In software, this is performance, security, usability, scalability.</li><li><strong>UX Documentation</strong> → The lifestyle of the people who’ll live there. Who are they (personas)? How do they use the space (scenarios)? What are their daily needs (user stories)?</li><li><strong>Architecture &amp; Design Docs</strong> → The actual floor plan: how the rooms connect, what materials to use. For software, that’s system structure, tech stack, diagrams.</li><li><strong>Testing Documentation</strong> → The safety checks before move-in. Test plans and cases to confirm the house (or app) is fit to use.</li></ul><p>This is the <strong>vision</strong> of the product, captured in writing.</p><p><strong><em>The How</em>:</strong> <strong>Process Documentation</strong></p><p>If product documentation is the blueprint, process documentation is the <strong>construction schedule.</strong> It tells you how the work gets done.</p><ul><li><strong>Roadmaps</strong> → Like a building timeline: foundation first, then walls, then roof. In software, that’s strategy, technology, and release plans.</li><li><strong>Metrics</strong> → The inspection points. Are we on schedule? Is the foundation stable? For software, this means tracking progress and quality.</li><li><strong>Standards</strong> → Building codes. Rules everyone follows to keep things safe and consistent. In software, that’s coding guidelines, testing practices, and version control rules.</li></ul><p>This is the <strong>playbook</strong> that guides the process.</p><h3>Why It Matters</h3><p>When building alone, it feels tempting to skip documentation. After all, it’s just me — why bother writing things down?</p><p>But then I imagine myself six months later, staring at old code I barely remember, asking: <em>“What was I trying to do here again?”</em> That’s when documentation stops feeling like extra work and starts feeling like insurance.</p><p>It’s not just paperwork — it’s the difference between a fragile shack and a house that can grow into a mansion if needed.</p><p>That’s why I’m keeping these notes. Not just for today, but for<strong> future me</strong>. A kind of personal blueprint library I can return to whenever a new idea comes along.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea871c402185" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>