<?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 Steven Michael Thomas on Medium]]></title>
        <description><![CDATA[Stories by Steven Michael Thomas on Medium]]></description>
        <link>https://medium.com/@stevenwhatevr?source=rss-9d56bf9cc27f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*nPkyTv9f9wvPY1_a.jpeg</url>
            <title>Stories by Steven Michael Thomas on Medium</title>
            <link>https://medium.com/@stevenwhatevr?source=rss-9d56bf9cc27f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:01:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stevenwhatevr/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[In pursuit of singularities]]></title>
            <link>https://medium.com/@stevenwhatevr/in-pursuit-of-singularities-2d638d043bc1?source=rss-9d56bf9cc27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d638d043bc1</guid>
            <category><![CDATA[science]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Steven Michael Thomas]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 10:34:10 GMT</pubDate>
            <atom:updated>2017-10-17T12:40:15.482Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>The state of the universe, after the Big Bang, will not depend on anything that may have happened before, because the deterministic laws that govern the universe will break down in the Big Bang. The universe will evolve from the Big Bang, completely independently of what it was like before.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gaAjLXhcOvOSfKllxMSG9g.jpeg" /></figure><p>Throughout life we go through cycles of comfort and discomfort, typically correlated to how much we know about our current situation.</p><p>I try to position major decisions as singularities in my life. It is impossible to know what lies ahead, but the not-knowing creates a sense of excitement at the possibility. The not-knowing becomes a beacon for recognizing learning and growth.</p><p>When I look back at the past few years the singularities have become more difficult to recognize. My decisions are more calculated and the <em>impossible-to-know changes</em> more typically manifest as <em>risk-free incremental upside</em>. I continue to learn things, but I’m filling buckets of knowledge rather than creating new buckets. I think fondly of new worlds I could dive into, but then I quickly wonder “how, and why?”.</p><p>I wonder if this shift is a symptom of getting older, or developing mastery, or over-specialization. But I think it is more likely that it is safer, and more comfortable to avoid change. <strong>Things are good right now so why make a change?</strong></p><h4>Change is hard</h4><p>Change is hard, because you do not know where change will lead you. It is easy to avoid disruptive changes and assume that the outcome will be negative, or at least that the process of alteration is enough to warrant avoidance. But there is a beauty in not knowing, in relinquishing control of an aspect of your life, and creating a situation where you cannot know what will happen next.</p><p>An aversion to change focuses on the burden of the process. If we look at the Big Bang it immediately becomes clear that the process of not-knowing can present limitless possibility. From an unmeasurably dense and small mass came everything that we know. Evidence of this surrounds us every day, but still we shy away from difficult change.</p><p>Going into each of these decisions it’s easy to know what you’re providing in terms of inputs — where you’re at, reasoning for making the decision, things you hope will happen as a result of the decision — but the actual result is nearly impossible to know due to the limitless external factors that may influence the outcome.</p><p>As result, all you can do is <strong>make decisions</strong>, and dive into the unknown. I feeling a longing for risk, failure, and uncomfortable growth, so for the next while I’m going to focus on these three things to ensure that they remain a part of my life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d638d043bc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Becoming the best developer in the ‘world’]]></title>
            <link>https://medium.com/@stevenwhatevr/becoming-the-best-developer-in-the-world-363e6f838dc0?source=rss-9d56bf9cc27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/363e6f838dc0</guid>
            <category><![CDATA[ux-skills]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Steven Michael Thomas]]></dc:creator>
            <pubDate>Thu, 29 Sep 2016 14:17:31 GMT</pubDate>
            <atom:updated>2016-10-23T22:51:15.553Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FlpUVxmpF-8-uXwOYhQnDw.jpeg" /><figcaption>Illustration by <a href="https://www.instagram.com/nadiabmad/">Nadia Alam</a></figcaption></figure><p>Along with the monolithic rise in front end development has come an exponential growth in the libraries, frameworks, transpilers, and pre- and post-processors used to do our jobs. For juniors and veterans alike, the plethora of choice can be problematic when figuring out how to create impactful work.</p><p>It feels like the industry as a whole suffers from a collective sort of <a href="http://www.urbandictionary.com/define.php?term=fomo">FOMO</a>. <a href="https://medium.com/@housecor/browserify-vs-webpack-b3d7ca08a0a9#.9ie6r0vr6">Still using Browserify</a>? If you don’t switch to Webpack you are basically dead. Writing JS in ES5? If you don’t learn ES6 and start using Babel tomorrow the apocalypse will be your fault. And 😂 you’re still using Babel?<a href="https://medium.com/@basarat/typescript-won-a4e0dfde4b08#.wtjt4nsir"> Typescript won</a>, duh.</p><h3>Becoming your best in a world of infinite options</h3><p>If you are now feeling nervous about your future as a developer, don’t worry. Yes, change is rapid, winners are fleeting, and figuring out the right tool for your project is increasingly difficult to determine (in an industry of <a href="http://99percentinvisible.org/episode/on-average/">one size fits all solutions</a>).</p><p>Despite all of this, you can still become the best developer in the ‘world’ by putting the following into practice:</p><h3>1. Redefine your world</h3><p>The first step to becoming the best in the world is to throw away your idea of what ‘world’ means.</p><blockquote>The secret to being the best in the world is to make the ‘world’ smaller. — <a href="http://sethgodin.typepad.com/seths_blog/2009/02/make-the-world-smaller.html">Seth Godin</a></blockquote><p>In other words, stop trying to learn everything. When you find something that you’re passionate about, go deep! Maybe it’s accessibility, maybe it’s writing CSS at scale, or maybe you love making websites for local coffee shops. Whatever it is, make this your world, and focus 80% of your learning here. Use the remaining 20% to be aware of industry trends to keep yourself resilient to fundamental shifts.</p><p>At Shopify, some people are dedicated to modern Javascript development, while others may focus on image optimization, web performance, developing UI patterns, and many other specializations. All of these people have successful careers as developers despite not knowing everything.</p><h3>2. Focus on fundamentals</h3><p>In a world where we have <a href="https://medium.com/shopify-ux/how-to-learn-web-frameworks-9d447cb71e68#.70anjmm3k">layer upon layer of abstraction</a>, the best thing I can suggest is to cut through these layers and understand the fundamentals.</p><p>Learning about React and Flux architecture is great, and extremely valuable, but without a <a href="https://www.amazon.ca/gp/product/1593275846/ref=as_li_tf_tl?ie=UTF8&amp;camp=15121&amp;creative=330641&amp;creativeASIN=1593275846&amp;linkCode=as2&amp;tag=medium0a-20">solid foundational knowledge about Javascript</a>, or functional programming, you may find yourself hitting walls when it comes to debugging, or understanding how to design a larger application.</p><p>In the same way, something like Ruby on Rails allows for incredibly expressive application development, but without some understanding of Ruby, <a href="https://www.amazon.ca/gp/product/0321721330/ref=as_li_tf_tl?ie=UTF8&amp;camp=15121&amp;creative=330641&amp;creativeASIN=0321721330&amp;linkCode=as2&amp;tag=medium0a-20">object-oriented programming</a>, or <a href="https://www.amazon.ca/gp/product/0201633612/ref=as_li_qf_sp_asin_tl?ie=UTF8&amp;camp=15121&amp;creative=330641&amp;creativeASIN=0201633612&amp;linkCode=as2&amp;tag=medium0a-20">basic design patterns</a>, you’ll hit walls once you move beyond the basics.</p><h3>3. Understand why companies hire developers</h3><p>At the start of every day, remind yourself why you got hired:</p><blockquote>The person who has decided to bring on one more engineer is not doing it because they love having a geek around the room, they are doing it because adding the geek allows them to complete a project (or projects) which will add revenue or decrease costs. — <a href="http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/">Kalzumeus</a></blockquote><p>Your success as a developer is not determined by the tools that you use, or even the style of your code, it is the business impact that your code has on the company or project you’re working on. A reductionist analogy could be that if developer A writes beautiful code that results in $10 in additional value, and developer B writes abhorrent code that results in $100 in additional value, developer B is a better developer.</p><p>On Shopify’s growth team we talk about this a lot — everyone on the growth team is obsessed with one single goal (growth!!); what they bring to the table to help achieve this goal depends on their background (code, design, etc).</p><h3>The power of focus</h3><p>Becoming a developer means assuming a life of continuous learning and growth. With this also comes the reality that there will never be enough time to learn all of the things. But hopefully by keeping these few points in mind the journey ahead can be more focused and impactful.</p><p>Originally published on <a href="http://stevenmichaelthomas.com/blogs/articles/becoming-the-best-developer-in-the-world">Steven Michael Thomas’ blog about learning web development</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=363e6f838dc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So you want to be a front end developer]]></title>
            <link>https://medium.com/@stevenwhatevr/so-you-want-to-be-a-front-end-devleoper-f8be110f1d5f?source=rss-9d56bf9cc27f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8be110f1d5f</guid>
            <category><![CDATA[ux-skills]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Steven Michael Thomas]]></dc:creator>
            <pubDate>Tue, 17 Nov 2015 12:08:41 GMT</pubDate>
            <atom:updated>2016-10-23T22:50:15.875Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>So you want to be a front end developer — A practical guide to growth for junior developers</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ijh8RMb6Yj5OLK4YtKzKcQ.jpeg" /><figcaption>Illustrations by <a href="https://dribbble.com/nadiaalam">Nadia Alam</a></figcaption></figure><p>Front end development has seen a huge rise in the past several years. Javascript continues to widen the gap as the <a href="http://githut.info/">most used language on Github</a>, and job openings are abundant. It’s no wonder that in tandem with this ascent, we’ve seen a massive increase in the number of lofty-promise-learning-programs — bootcamps, tutorials, crash courses and everything in between. The cycle is natural for any booming industry, and it breaks down as follows:</p><ol><li>There is huge demand for front-end developers. Companies are scrambling to find competent people to fill roles, and they’re paying top dollar.</li><li>Other companies see this demand, and create educational resources to help “bootstrap” people’s careers. They promise a quick-fix solution to learning about web development that will set you up for an epic amount of success.</li><li>The pitch is appealing, so a lot of people do it. Bootcamps and online learning resources are selling like hotcakes — it has quickly become a multi-billion dollar industry.</li></ol><p>The net result is a huge pool of extremely junior talent. Most students walk away with a portfolio site and a few javascript demos, but lack any deep understanding of development that would allow them to tackle real-world problems that working developers face every day.</p><p>The intention of me writing this is not to negate the benefits of these learning programs — as a self-taught developer before these programs existed, I’m sure that my life would have been much easier if these resources were available to me when I was getting started. They are a great way to get your feet wet and to begin the learning process. However, they are only the beginning.</p><p><strong>Okay, so what now?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WSFF9LP8GkQs0HwiT8GVaA.jpeg" /></figure><p>For those of you who have recently completed one of these programs, and are now part of the ever-growing pool of junior developers, you may ask yourself — what now? With so many options for learning the basic skills, I wanted to look at some next steps to transition from a hot-blooded junior dev, to a highly employable intermediate.</p><p>The following are a few things that went a long way towards helping me bridge the gap between the early days of my learning, to being a competent and productive developer:</p><p><strong>Read books</strong></p><p>To obtain a deep understanding of the front-end languages (Javascript, CSS and HTML), reading hyper-focused tutorials aren’t going to cut it — you need to read books. Early on in my learning, I remember reading <a href="http://amzn.to/1N8R82Y">Javascript Patterns</a> and having absolutely no idea what anything meant. But as I continued to learn, bits in the book started to make sense. I used it as a reference, which helped to ensure that I was writing code in ways that made sense. After a while, I was able to understand the book entirely, and even form opinions on some of the content.</p><p>For budding front-ends, I’d recommend <a href="http://amzn.to/1N8RKpm">Eloquent Javascript</a>, <a href="https://smacss.com/">SMACSS</a>, and <a href="http://amzn.to/1N8RV3U">HTML and CSS: Design and Build Websites</a>; but don’t stop there.</p><p><strong>Go to meetups</strong></p><p>Meetups serve as an excellent reminder that you’re not alone. Tap into your community’s expertise by just showing up at meetups to learn more about web development. Like reading a reference book, you may feel like a fish out of water for a while, but the secret truth of it is that developers are a reasonably nice bunch of people, and almost everyone has been in your shoes at some point. So, find some meetups, show up, ask questions, and listen. Eventually things will start to make sense.</p><p><strong>Open Source</strong></p><p>This can be a daunting one for all levels of developers, but if you’re developing for the web, I can almost guarantee that you’re using open-source software.<strong> </strong>Open source software is software that can be freely used, shared and <em>changed </em>by anyone. So, where to start? Think of a tool that you use — say… <a href="https://github.com/jquery/jquery">jQuery</a> or <a href="https://github.com/twbs/bootstrap">Bootstrap</a>, and start looking through <a href="https://github.com/twbs/bootstrap/issues">issues on Github</a>. Is there something that you think could be better with either of these? Create an issue, or better yet, submit a change. The worst thing that will happen is your change will get rejected, but the important part is that you’re giving back, and getting real-world feedback.</p><p><strong>Find a junior job, internship or hybrid role</strong></p><p>This may seem like an obvious one, but the important thing to remember here is to keep all options open. Finding a junior job or internship that will be worth your while can be difficult. Remember that getting your foot in the door is important, but if you’re working as a junior or intern, make sure that there’s a clear roadmap for a career beyond this. There are a lot of great companies that aim to mentor and grow their junior staff, but many others are happy to keep them around as workhorses to do the jobs that others don’t want to do — it’s more about cheap labour than growing the next generation of developers.</p><p>The other option when looking for work is to find a hybrid role. One of my first dev jobs was as a <em>Web Producer</em> which basically meant that I pasted things into a Wordpress site, and occasionally dabbled in adding small new features to an existing site. It wasn’t terribly riveting, but it was a less-pressured way to work my way into a full-time development role.</p><p><strong>Start a project</strong></p><p>I cannot stress this one enough. Solving real problems for something that you care about is the absolute best way to become a better developer. Rather than dealing with unknowns, you can work towards solving specific problems.</p><p>The first lines of production code that I wrote were a result of entering a <a href="http://startupweekend.org/">Startup Weekend</a> contest with a friend who had an idea to create an <a href="http://getvetter.com/">employee suggestion box app</a>. The process was terrifying, but we had a clear idea of what we wanted our app to do, so I hacked and fussed with code until it sort of did it. This was a horribly messy process, and to be frank, the initial code was terrible, but I learned a huge amount in a short period of time. Working with real customers was a huge drive too, as we had to manage their expectations vs. a side project without customers where uptime doesn’t really matter. After running this business for about 8 months, I was able to land my first full-time development job.</p><p><strong>Never stop learning</strong></p><p>I hope that these points will help to accelerate your learning, but they are by no means holistic or all-encompassing. The incredible thing about front-end development is that things are constantly changing, so there should never be a time when you finish learning. This means that no matter how many books you read, meetups you attend, or projects you work on, the learning process has to continue if you want to remain relevant.</p><p>There is a huge amount of opportunity in front-end development, and a huge number of people vying for the same jobs that you’re looking at. But if you passionately pursue the items listed here, you’re sure to cement yourself as an intermediate developer and land yourself in an incredibly rewarding career.</p><p><strong>Background</strong></p><p><em>I am writing this from a place of empathy. I began my career working in the film industry with zero coding experience. On a whim, I moved to Taiwan and worked an extremely tedious copywriting job. I started to poke away at web development before entering a startup competition with a friend as the lead developer 😮. From there, I managed to get a few freelance contracts before landing my first pseudo-development role as a Web Producer. I scraped together enough sample code to get a job at a few agencies. I had the tremendous opportunity to work at </em><a href="https://medium.com/u/f4fb344380e6"><em>MetaLab</em></a><em> during this time, which really catalyzed my journey towards become a good developer — </em><a href="https://medium.com/u/e16144bf7849"><em>Jason Webster</em></a><em> was an incredible mentor and I am forever indebted to his patience. For the past few years I’ve been working at Shopify where I’ve been able to grow exponentially, and I’m now working as a Lead Front End Developer. I mention all of this because it’s important to note that it hasn’t been a smooth journey. There were several years when I felt like I truly had no idea what I was doing, but with enough tenacity, I was able to figure things out.</em></p><p>Illustrations by <a href="https://dribbble.com/nadiaalam">Nadia Alam</a></p><p>Originally published on <a href="http://stevenmichaelthomas.com/blogs/articles/so-you-want-to-be-a-front-end-developer-a-practical-guide-to-growth-for-junior-developers">Steven Michael Thomas’s Blog about web development</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8be110f1d5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>