<?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 Moxley Stratton on Medium]]></title>
        <description><![CDATA[Stories by Moxley Stratton on Medium]]></description>
        <link>https://medium.com/@mstratton_49161?source=rss-fbfead7945da------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*YGZKVd8f92GjN7X_.</url>
            <title>Stories by Moxley Stratton on Medium</title>
            <link>https://medium.com/@mstratton_49161?source=rss-fbfead7945da------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:20:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mstratton_49161/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[Speed Up Coding With Atomic Tasks]]></title>
            <link>https://medium.com/@mstratton_49161/speed-up-coding-with-atomic-tasks-cb3d5667ec8c?source=rss-fbfead7945da------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb3d5667ec8c</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Moxley Stratton]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 15:25:10 GMT</pubDate>
            <atom:updated>2018-03-06T15:25:10.688Z</atom:updated>
            <content:encoded><![CDATA[<p>Do you want to speed up your software development? Want to code with less stress, without feeling stuck?</p><p>Maybe you’ve heard the advice, “commit often”. That is, commit your recent changes to source control often, without letting too much code change in between commits. Has that turned out to be more difficult than it sounds?</p><h3>Breaking Down The Problem</h3><p>The key reason why developers get bogged down on a problem is that they don’t think enough about breaking down the problem into individual steps. They think about the end goal, and start coding towards that goal almost immediately.</p><p>Next time you’re tasked with a problem, do start with the end goal in mind, but don’t start coding yet. Open a text editor or a note taking app and start writing a checklist. Write down the end goal first. Under that and indented one level, think of a task that needs to be completed before the end goal can be considered complete.</p><p>After you’ve written your first task, look at that task, and figure out how many areas of the codebase you’ll have to change to complete that task. We’ll call these areas “components”. How many components need to change? One? Two? Three? Four or more? If it’s more than one, consider breaking down the task into smaller tasks. If it’s more than two, definitely break it down.</p><p>For a task that is broken down so that it touches only one or two components, we call it an “atomic task”. It doesn’t get broken down any further.</p><p>Don’t worry about breaking all the tasks down to atomic tasks. Just break down the next few you can start working on. As you work on them, continually update and break down the next several tasks.</p><h3>Task Ordering</h3><p>Ordering tasks is key to making this strategy work. For example, make sure that task number one doesn’t depend on the completion of task number two. Re-order the tasks so that the earlier ones don’t depend on the later ones.</p><p>While coding, when you come across a piece of code you know needs to change later on, just add that to your task list, and put it in a reasonable order.</p><h3>The Task List</h3><p>I use the Markdown language to manage atomic tasks (I use Markdown for all kinds of things, including writing this blog post). Here’s an example of a programming problem, and some of the tasks involved:</p><pre>[ ] Implement pagination SRVC-1923<br> — [x] Move `FeatureListParams` and `FeatureListResult` to own module<br> — [x] Define `GroupsListParams` type<br> — [x] Define `FeatureListResult` type<br> — [x] Convert `fetchGroups()` to use authStore as argument<br> — [x] Convert `fetchGroups()` to use `FeatureFlagApi`<br> — [x] Integrate `FeatureListResult` with `GroupsStore`<br> — [x] Integrate `GroupsListParams` with `GroupsStore.fetchGroups()`<br> — [x] Integrate filters with `GroupsStore.fetchGroups()`<br> — [x] Eliminate `GroupsStore.fetchGroupsByName()`<br> — [x] Fix pagination fetch: not passing filters<br> — [x] Eliminate unnecessary mutations in Groups component<br> — [ ] Include request params in GroupListResult<br> — [ ] When the search query or filter changes, reset the page number to `1`<br> — [ ] DRY up multiple calls to `fetchGroups()`<br> — [ ] Use return value from `fetchGroups()` instead of using cached value.</pre><h3>Task Completion</h3><p>Upon completion of an atomic task, your project’s tests should pass. Everything should be green. Commit the task to source control. You can use the task description as your commit message.</p><p>Sometimes, I fall out of the habit of breaking down problems into atomic tasks. When that happens, I find myself slowing down, getting stuck more of the time, and making less-frequent commits. So, the next time you feel like you’re getting stuck, let that be a reminder to use atomic tasks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb3d5667ec8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>