<?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 Growing Developers on Medium]]></title>
        <description><![CDATA[Stories by Growing Developers on Medium]]></description>
        <link>https://medium.com/@growdevelopers?source=rss-c0df1454029------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9xbvXnKHrH5sxdRu.png</url>
            <title>Stories by Growing Developers on Medium</title>
            <link>https://medium.com/@growdevelopers?source=rss-c0df1454029------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:07:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@growdevelopers/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[Shuhari for Developers]]></title>
            <link>https://medium.com/@growdevelopers/shuhari-for-developers-85638a88b95d?source=rss-c0df1454029------2</link>
            <guid isPermaLink="false">https://medium.com/p/85638a88b95d</guid>
            <dc:creator><![CDATA[Growing Developers]]></dc:creator>
            <pubDate>Sun, 05 Jan 2014 23:20:47 GMT</pubDate>
            <atom:updated>2014-01-05T23:20:47.081Z</atom:updated>
            <content:encoded><![CDATA[<h4>An introduction to ability-centered self reflection</h4><p>There are many competing competence models, with the <a href="https://en.wikipedia.org/wiki/Dreyfus_model_of_skill_acquisition">Dreyfus model</a> being one of the most common. While I find it useful, it’s complexity can make it inaccessible. While Dreyfus has 5 distinct stages of competence, shuhari has three:</p><ul><li>Shu: Protect, Obey, Follow.</li><li>Ha: Detach, Digress, Challenge</li><li>Ri: Leave, Separate, Transcend</li></ul><p>When considering software, I map these to:</p><ul><li>Shu: I build working software using prescribed syntax, patterns, libraries, protocols, and frameworks. Creating my own alternatives is primarily a learning exercise.</li><li>Ha: While building software, I differentiate between alternative syntax, patterns, libraries, protocols, and frameworks. When I create a new alternative it sometimes provides a distinct advantage to existing alternatives.</li><li>Ri: I intuitively select a reasonable choice from a pool of alternatives. When I create new alternatives they often provide a distinct advantage to existing alternatives.</li></ul><p>While having these words is an excellent starting point, it is valuable to consider possible pitfalls we encounter as we attempt to review our abilities on this scale. Some common ones are:</p><ul><li>Blindness to existing alternatives.</li><li>Misjudging the value of our creations.</li><li>Assessing at the right abstraction level.</li></ul><p>These are all addressable, and should not stand in your way of accurate self-reflection.</p><h4>Open Your Eyes to Alternatives</h4><p>When beginning as a developer, it is good to become highly proficient at a small set of complementary things. Take care to ensure this competence does not hinder your further development. Once you’ve gained some degree of competence; whether a language, library, pattern, protocol, or framework; begin to examine the popular alternatives. As you do, gauge your reaction:</p><ul><li>Which parts of my reaction are tied to how I feel about the unknown and uncertainty in general?</li><li>What are two or three distinct advantages this provides over the tool I know and understand?</li><li>What are two or three distinct advantages the tool I know and understand has over this new tool?</li></ul><p>If you are struggling to answer these questions it is possible you need to spend more time exploring the alternative before deciding its merit. As you do this over and over you are building the expertise you need to attain Ha. If you rarely do this, you will likely remain at Shu for quite some time.</p><h4>Shift Your Ego</h4><p>There are few things we tie more closely to our self worth than the things we create. Quite often we are proud of something we did and despise it merely hours later. Shifting your ego from what you built to how you performed while building it provides a more realistic appraisal of your abilities.</p><ul><li>Recognize the value of creating something. Spending time on a task is something to be proud of; regardless of the quality of the end result.</li><li>Acknowledge what you did well while you were working. Did you write <a href="http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html">beautiful commits</a>? Remain <a href="https://en.wikipedia.org/wiki/Pomodoro_Technique">distraction free</a>? Stay tenacious in the face of a difficult bug? As you reflect upon your work process, recall what worked well and do more of it next time.</li></ul><p>Taking pride in the work at hand is an excellent technique to keep you focused on improvement as opposed to getting mired in whether the resulting code is terrible or awesome. It can also make it easier to take feedback.</p><h4>Focus On Important Skills</h4><p>Building successful software is complex. There’s users needs, business concerns, code, infrastructure, etc. Each of these could be divided into a half-dozen or more subdomains without too much effort. The subdomains could then be broken down further, I’m sure. Every single one of us will have a different breakdown of the skills and abilities that are important to us. I would recommend writing down a few dozen skills at varying levels of abstraction. Then for each skill answer the following questions:</p><ul><li>What do I enjoy doing?</li><li>What am I good at?</li><li>What are people willing to pay for?</li></ul><p>Once you’ve answered these questions discard any skills that have zero yesses. Follow this up by pruning out low-yes skills until you have about a dozen remaining. This is now your skill portfolio. Review and reshuffle whenever you feel like it.</p><p>Your competence as a developer is your responsibility. Being aware of where you stand is a powerful tool for fueling your growth. Good luck out there and keep learning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85638a88b95d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a Personal Learning Plan]]></title>
            <link>https://medium.com/@growdevelopers/designing-a-personal-learning-plan-3755e953e85e?source=rss-c0df1454029------2</link>
            <guid isPermaLink="false">https://medium.com/p/3755e953e85e</guid>
            <dc:creator><![CDATA[Growing Developers]]></dc:creator>
            <pubDate>Tue, 19 Nov 2013 22:33:00 GMT</pubDate>
            <atom:updated>2013-11-19T22:33:00.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*ZAYSAHUVn_RTuvNxrWlhrw.jpeg" /><figcaption>Photo by http://www.flickr.com/photos/cmuffins/</figcaption></figure><h4>Plans are worthless, but planning is everything.</h4><p>We all have different paths along <a href="http://chimera.labs.oreilly.com/books/1234000001813/ch03.html">the long road</a>, and it’s often difficult to find the best path. We have different goals and different constraints. Some of us want to specialize in consumer-facing mobile apps; others want to rethink the cryptographical underpinnings of our networking protocols, and still others want to write code to provide a safe driving experience for those of us who plummet down the highway in a metal container going 80 miles an hour.</p><p>This is OK; there’s tons of room for different passions in the technology field. The constraints in what you can accomplish as a programmer have less to do with availability of meaningful problems and more to do with the resources you have available to accomplish these objectives.</p><p>This is why it’s critically important for each of us to design our own personal learning plan. It’s incredibly easy to say “I want to build mobile apps!” or “I want to develop embedded systems applications!” and never make any progress in these goals.</p><p>To start building my plan, I asked myself a few questions:</p><ol><li>What do I enjoy doing?</li><li>What do I want to be significantly better at in 3 months?</li><li>What are resources I could leverage to help accomplish these goals?</li></ol><p>Each week, I then set small, achievable goals that will take me a step closer to my goals by creating a 1 ~ 3 item list that starts with “This week I intend to…”</p><p>At the end of the week, I reflect on the intentions and set new ones. For intentions I didn’t follow through on, I default to *not* choosing them for next time. Instead, I ask myself:</p><ol><li>Why did I not follow through with that intention?</li><li>What does this failure to follow through mean about my long term goals?</li></ol><p>By following this lightweight planning and reflection strategy, I’ve found it’s become much easier for me to intentionally improve my skills as a programmer. Hopefully it’ll also help you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3755e953e85e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why is Growing Developers  a Private, For Pay Community?]]></title>
            <link>https://medium.com/@growdevelopers/why-is-growing-developers-a-private-for-pay-community-23a9de730c4f?source=rss-c0df1454029------2</link>
            <guid isPermaLink="false">https://medium.com/p/23a9de730c4f</guid>
            <dc:creator><![CDATA[Growing Developers]]></dc:creator>
            <pubDate>Thu, 14 Nov 2013 18:25:12 GMT</pubDate>
            <atom:updated>2013-11-14T18:25:12.787Z</atom:updated>
            <content:encoded><![CDATA[<h4>Or, Why Don’t We Just Use Stack Overflow?</h4><p>There are many great places to ask questions and get answers on the Internet: Stack Overflow, Reddit’s numerous language specific sub-reddits, Quora, etc. are all amazing.</p><p>So why bother paying for Growing Developers? Here are two reasons:</p><ol><li>Questions and conversations are better than answers</li><li>Safety is better than availability</li></ol><h4>Questions and Conversations over Answers</h4><p>Growing Developers is all about thinking and learning. This means we <a href="http://kiriakakis.net/comics/mused/a-day-at-the-park">value questions more than we value answers</a>.</p><p>That isn’t to say that we won’t try to answer your questions. It just means we value the thinking behind a question and having a conversation that educates over providing an answer that solves your immediate problem. Stack Overflow is really really good at providing answers, so use the right tool for the job, right?</p><h4>Safety Over Availability</h4><p>Growing Developers is committed to being a safe place for becoming a better programmer. This means we’re <a href="http://www.zeespencer.com/articles/structure-and-space/">creating an environment</a> where:</p><ol><li>People are comfortable <a href="http://chimera.labs.oreilly.com/books/1234000001813/ch02.html#expose_your_ignorance">exposing their ignorance</a></li><li>Everyone is treated with respect and dignity; regardless of preferred text editor, programming language, gender, sexual orientation, socioeconomic status, etc.</li></ol><p>I believe the only way to achieve these goals is to make the community the customer; not the advertisers or potential investors.</p><p>If you’re interested in being one of the first members of the Growing Developers community, send me an email at <a href="/service/mailto:zee@growingdevelopers.com">zee@growingdevelopers.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23a9de730c4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>