<?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 Alex Skorulis on Medium]]></title>
        <description><![CDATA[Stories by Alex Skorulis on Medium]]></description>
        <link>https://medium.com/@skorulis?source=rss-ea44cbb465f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*uIin5z6zSOEgDeL6.</url>
            <title>Stories by Alex Skorulis on Medium</title>
            <link>https://medium.com/@skorulis?source=rss-ea44cbb465f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:50:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@skorulis/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[One Week Wonders: A Coding Odyssey]]></title>
            <link>https://medium.com/@skorulis/one-week-wonders-a-coding-odyssey-6175d911a69b?source=rss-ea44cbb465f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6175d911a69b</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Alex Skorulis]]></dc:creator>
            <pubDate>Sun, 19 Nov 2023 05:29:28 GMT</pubDate>
            <atom:updated>2023-11-19T05:29:28.790Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve long had an issue with completing projects, despite ample time to work on my side projects and great intentions, they always find their way into a pile of legacy code never to be looked at again. A combination of scope creep, unexpected challenges and a lack of necessity sap my motivation until I first delay and then finally abandon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BKxitfu_nMiGXTmqGAUKwQ.png" /></figure><p>In order to avoid falling into the same patterns I’ve crafted a plan to tackle a sequence of coding projects, each lasting just one week. This endeavour promises not only to deliver projects but also to cultivate a sense of accomplishment and efficiency. First up let’s look at the rules.</p><h3>Weekly Coding Rules</h3><ol><li><strong>Strict One-Week Limit</strong>: The core principle is completing each project within a seven-day timeframe. Coding starts on Monday and must be ready for release on Sunday. (Due to app store reviews the actual release may happen in the following week). Planning and research can happen at any time.</li><li><strong>Project readiness: </strong>Before starting on a project it must have a clearly defined scope and objectives. Necessary research and background exploration should be conducted to ensure a foundational understanding of the technologies involved. Additionally, dependencies and potential challenges should be identified and addressed proactively. This pre-flight preparation is not about over-planning but about laying a sturdy groundwork, allowing for a focused and productive week of coding. Striking the right balance between readiness and agility is key, ensuring that each project is poised for success within the confines of the one-week timeframe</li><li><strong>Project Complexity: </strong>The initial scope of the project needs to be reasonable to complete in one week. If the idea requires learning new technologies this needs to be factored in and the scope reduced.</li><li><strong>Project diversity: </strong>This exercise should not turn into a single project broken into week long tasks and projects should not build on top of previous work. Each week is designed to stand independently, this intentional isolation ensures that the success of one project is not contingent on the completion of another. This modular approach prevents any one project from becoming a motivation bottleneck.<br>This is not to completely rule out using a week to enhance a previous project, but there must be a break between doing so and the enhancement should be planned after the original project is delivered.</li><li><strong>Project deliverables: </strong>An integral part of the ‘One-Week Wonders’ coding philosophy is the definition of a clear and concise deliverable at the end of the week. Each project must outline tangible goals and outcomes, ensuring a well-defined roadmap for implementation within the one-week timeframe. In keeping with the above topic of diversity, the deliverables do not need to be purely production code. Documentation, blog posts and learnings are all tangible outputs.</li></ol><h3>The Blueprint</h3><ol><li>Projects are planned in advance. The plans for future projects will continue to evolve over time.</li><li>On each Monday a project will be selected and coding will begin. On Sunday coding will stop and the resulting product will be released.</li><li>Part of the release of the release will involve a retrospective about how well the project went.</li></ol><h3>Challenges and Mitigations</h3><p>Given the extremely short timescales and high demands burnout is a real possibility. The recognition and acceptance of the possibility of missed deadlines play a crucial role in mitigating burnout. Setting this as an expectation serves as a buffer against the relentless pressure that can lead to burnout. Life happens and there will be weeks where it simply isn’t possible to deliver.</p><h3>Enhancing Motivation</h3><p>The allure of the One-Week Wonders lies not just in the completion of projects but in the transformative power it holds over motivation. Completing a project every week acts as a perpetual catalyst and a constant source of achievement that propels me forward. This relentless pace ensures that the coding spark remains ablaze, infusing each project with a sense of urgency and purpose. The structured nature of the plan, with predefined rules acts as a compass guiding my efforts to give me a clear objective to focus on which will help me ignore external distractions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6175d911a69b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>