https://blog-dev.simpleenough.net/tags/organization/Recent content in Organization on Simple Enough BlogHugoenFri, 20 Feb 2026 10:00:00 +0100https://blog-dev.simpleenough.net/blog/chargecognitiveci/Fri, 20 Feb 2026 10:00:00 +0100https://blog-dev.simpleenough.net/blog/chargecognitiveci/<h2 id="i-the-real-cost-of-a-bad-ci-workflow-cognitive-load" class="heading">I. The Real Cost of a Bad CI Workflow: Cognitive Load<a href="#i-the-real-cost-of-a-bad-ci-workflow-cognitive-load" aria-labelledby="i-the-real-cost-of-a-bad-ci-workflow-cognitive-load"> <!-- <i class="fas fa-link anchor"></i> --> <svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512"><use href="#fas-link"></use></svg>&nbsp; </a> </h2> <p>People talk a lot about CI pipeline performance.<br> We measure minutes.<br> We optimize caches.<br> We parallelize.</p> <p>But the real cost of a bad CI workflow is not machine time.</p> <p>It is <strong>cognitive load</strong>.</p> <p>And it is far more expensive.</p> <hr> <h2 id="ii-the-invisible-problem" class="heading">II. The Invisible Problem<a href="#ii-the-invisible-problem" aria-labelledby="ii-the-invisible-problem"> <!-- <i class="fas fa-link anchor"></i> --> <svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512"><use href="#fas-link"></use></svg>&nbsp; </a> </h2> <p>An inefficient CI pipeline is visible:</p>https://blog-dev.simpleenough.net/blog/organization_frontend/Fri, 05 Sep 2025 12:09:45 +0200https://blog-dev.simpleenough.net/blog/organization_frontend/<h2 id="i-why-organize-your-frontend-project" class="heading">I. Why Organize Your Frontend Project?<a href="#i-why-organize-your-frontend-project" aria-labelledby="i-why-organize-your-frontend-project"> <!-- <i class="fas fa-link anchor"></i> --> <svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512"><use href="#fas-link"></use></svg>&nbsp; </a> </h2> <p>When you&rsquo;re starting with web development, it&rsquo;s common to place all your files in one folder. However, <strong>good organization</strong> quickly becomes essential as the project grows, whether for:</p> <ul> <li>Navigating your codebase easily.</li> <li>Collaborating effectively with other developers.</li> <li>Making maintenance and updates easier.</li> <li>Saving time in the long run.</li> </ul> <hr> <h2 id="ii-recommended-structure-for-a-simple-project" class="heading">II. Recommended Structure for a Simple Project<a href="#ii-recommended-structure-for-a-simple-project" aria-labelledby="ii-recommended-structure-for-a-simple-project"> <!-- <i class="fas fa-link anchor"></i> --> <svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512"><use href="#fas-link"></use></svg>&nbsp; </a> </h2> <p>Here’s a classic, clean structure for an HTML/CSS/JS project without a framework:</p>