<?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 Jon Barker on Medium]]></title>
        <description><![CDATA[Stories by Jon Barker on Medium]]></description>
        <link>https://medium.com/@jon_92408?source=rss-3165cfff25fe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*BbjesVICsSlC1y3wsQHs9w.jpeg</url>
            <title>Stories by Jon Barker on Medium</title>
            <link>https://medium.com/@jon_92408?source=rss-3165cfff25fe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:56:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jon_92408/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[Refactoring CSS]]></title>
            <link>https://medium.com/inktrap/refactoring-css-61ef64601ebb?source=rss-3165cfff25fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/61ef64601ebb</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[sass]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Jon Barker]]></dc:creator>
            <pubDate>Wed, 25 Sep 2019 11:31:02 GMT</pubDate>
            <atom:updated>2019-09-25T11:31:02.724Z</atom:updated>
            <content:encoded><![CDATA[<h4>What to keep in mind when thinking about refactoring your CSS</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mnEV1SDJ52G8sXu0" /><figcaption>Photo by <a href="https://unsplash.com/@clemono2?utm_source=medium&amp;utm_medium=referral">Clem Onojeghuo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As developers, we work in an industry that has a luxury not afforded to many others. We can edit things that have already been published.</p><p>In many other industries retroactively changing things is incredibly difficult. A writer can’t take their book off the shelves and rework a sentence. An artist can’t remove layers of paint to improve the layer beneath, and a construction company can’t build a new floor off-site and slot it back in when it’s ready.</p><p>Us developers? We can iterate internally on the design, on the frontend or backend, and then continue to push changes once the product is live.</p><p>This is a <em>very</em> good thing.</p><p>Because, no matter how careful we may be, we’re almost certainly going to come across code that we look at and think, “this could be better.” At which point you and your team might decide it’s time to improve it.</p><h3>It’s worth noting…</h3><blockquote>“An ounce of prevention is worth a pound of cure.” — <em>Benjamin Franklin</em></blockquote><p>Even though the idea of a refactor sits over most mature products it doesn’t mean you should code with a we’ll-rewrite-it-later-anyway mindset.</p><p>Having a <a href="https://sass-guidelin.es/">style guide</a>, an outline of the project, a plan for approaching it, a proper <a href="https://zellwk.com/blog/css-architecture-3/">directory structure</a>, and <a href="https://snipcart.com/blog/organize-css-modular-architecture">naming convention</a> are still important. Having these in place is what stops a quick refactor from becoming a complete overhaul.</p><blockquote>“Everyone knows that debugging is twice as hard as writing a program in the first place. So if you’re as clever as you can be when you write it, how will you ever debug it? “— Brian Kernighan, The Elements of Programming Style</blockquote><p>Refactoring can be difficult and is often tagged on as kind of an afterthought. The truth is, just like accessibility and responsiveness, it should be planned and approached as part of the <em>main </em>work. Not an extension to the project.</p><h3>Why would I have to refactor?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mb1dKSfnTOS6xE1P" /><figcaption>A CSS Mess. A CESS, if you will.</figcaption></figure><p>As we mentioned at the beginning, we can constantly iterate on the work we do. Because of this, our job continues after pushing to production, and the codebase can grow larger and larger. We can keep the code as clean as possible along the way, but with enough “quick changes”, pulls and merges, things can get messy.</p><p>Let’s take the following fictitious example:</p><p>A website has a blog section with a nice card layout. The CSS (if using BEM )might look something like this:</p><pre>/* _blog-post.scss */</pre><pre>.blog-post {}</pre><pre>.blog-post__header {}</pre><pre>.blog-post__title {}</pre><pre>.blog-post__image {}</pre><pre>.blog-post__footer {}</pre><p>The product changes and you’re asked to add a news section. It has a similar layout and style. You don’t want to give a news-article the same class as a blog post. So you make another file:</p><pre>/* _news-article.scss */</pre><pre>.news-article {}</pre><pre>.news-article__header {}</pre><pre>.news-article__title {}</pre><pre>.news-article__image {}</pre><pre>.news-article__footer {}</pre><p>You could be asked for a similar events section, but let’s leave it as it is. Now we have the problem of unnecessary duplicate code. What we probably want is to remove the above files and have something more like:</p><pre>/* _post.scss */</pre><pre>.post {</pre><pre>    &amp;__header {}</pre><pre>    &amp;__title {}</pre><pre>    &amp;__image {}</pre><pre>    &amp;__footer {}</pre><pre>    &amp;.post--blog {<br>        /* Modifier stuff here */<br>    }<br>}</pre><p>But of course, CSS is finicky and operates globally. When a new developer comes to this CSS they might be scared of changing it for fear of it breaking something elsewhere. On top of that, they might be working to a deadline, or maybe they’ll say “I’ll come back to this later”, but never will.</p><p>These little things add up over time and might result in your team deciding on a refactor.</p><h3>When and when not to refactor</h3><p>Maybe you’re thinking, why would I even touch this if it works? And that’s a very important and necessary question because you might not need to. The following isn’t an exhaustive list, but just an idea of things that may sway you one way or the other.</p><h4>When it might be time to refactor</h4><ul><li>Your CSS is excessively large.</li><li>Hinders performance in some way (large load time, layout breaks in specific use cases)</li><li>Developers spend time working <em>around</em> the code, not with it.</li><li>You want to increase the readability for newcomers.</li><li>You work in a very large team and refactoring now means you’re saving a little time for a lot of people.</li><li>A specific issue has been raised by multiple people.</li><li>The refactoring will be quick.</li></ul><h4>When it might not be necessary</h4><ul><li>A rewrite or re-design is coming up, and it will be easier to write from scratch.</li><li>The CSS “looks bad”, but no developer has had an issue with it. And no user has reported any</li><li>The CSS <em>is </em>bad but belongs to an element or component that won’t be touched. Take for example a footer which isn’t going to change. If a developer had some initial problems, but it’s finished and works, it might be worth focusing your attention on a different part of the site.</li></ul><p>Of course, whether something is worthy of a refactor is your choice. The above are just indicators I’ve learned of. So you decide it’s time, now what?</p><h3>Refactoring “on the move”</h3><p>This should be your first port of call. These are small pieces of tidying up that are more relaxed and less arduous than a full-on refactor.</p><p>It involves going over your .css or .scss files and combing them for classes that hold the same style declarations or have declarations that override each other. You should add comments to rules that don’t make immediate sense or seem to be unused. For instance, the class might not appear in the HTML but is added later by JavaScript. For example:</p><pre>.faq {<br>     &amp;.is-expanded {<br>        /* Toggled when user clicks on element */<br>    }<br>}</pre><p>Of course, doing this manually might take a while, so use a <a href="https://atom.io/packages/linter">Linter</a>. You can tweak your config and be warned upfront about things like duplicate declarations or empty selectors.</p><p>You can also get some valuable information about your CSS using <a href="https://cssstats.com/">CSS Stats</a>. This site can provide valuable information about the inline and linked CSS you’re using. You can get size comparisons to popular libraries. Declaration counts for layout, spacing etc, it shows a specificity graph… And the number of unique declarations for things like colour or font sizes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sk1oV64e2PoIO9sTxQYgvA.png" /></figure><p>Take the stats with a grain of salt, and have a general idea of the codebase you’re working on. Because having 40 unique colour declarations might seem like a lot for a standard marketing site, but for online clothes stores with colour swatches these results wouldn’t be so surprising.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QDU__D3iYs0iq6qOkG6cPQ.png" /></figure><p>When used properly the stats can be very insightful and can be used to weed out unnecessary rules. If your <a href="https://medium.com/inktrap/metamorphosis-converting-your-design-files-into-a-design-system-63172f8c71f">design system</a> lists 7 different sizes in its type scale and you have 30+, maybe it’s time to refactor those declarations into a single class or remove the declarations that are never actually applied.</p><h3>The “component refactor”</h3><p>This is the refactor that is done with one specific element or component in mind. For example, you’ve decided to tackle the header because multiple devs have had problems adding to it or modifying it.</p><p>The thought of diving straight in and making everything better for a lot of people can be motivating. But slow down and ask yourself or amongst your team the following questions:</p><h4><strong>What <em>really </em>needs to be refactored?</strong></h4><p>Let’s imagine we have a large messy footer that has some unused CSS and a bunch of hacks.</p><p>It might seem like an ideal candidate, but if it’s a part of the site that works, no users have reported a problem and it isn’t due to be updated for a while it can most likely be pushed to the back of the queue.</p><p>Maybe you have a nav that has many different variations or states might be better as a target. Maybe it’s snowballing and developers keep adding more classes with more specific rules to override it’s already specific selectors. Or perhaps we know that the client wants to add more states in a coming update. Or, you’ve finally dropped support for an older browser and you can use newer features like flexbox and rewrite the hacky float filled CSS from before.</p><h4>Is the refactor short enough?</h4><p>A refactor of a whole page might take longer than you think. You might be well served to set a smaller goal. Rather than tackling a whole page, how about just the buttons, or forms? Having smaller targets means you can demo the improvement more quickly, and be back on other projects/dev work faster than if you were tackling something huge like the home page. You should always have the end goal in sight. Refactor, move on, repeat.</p><h4>Where shall I do my “refactoring”?</h4><p>Basically, anywhere but the project it came from. CodePen, jsFiddle, a playground HTML file in your dev environment.</p><p>The main point is that it should be built away from your old stale codebase, though could import the grid if absolutely necessary. Refactoring in this way means that we rework our component away from all the conflicts or overwrites that were causing it to be messy in the first place. We can build it and test it in a new sterile environment, knowing that when it’s complete and reincorporated into the site we can identify more easily where the conflicts come in.</p><h4>How should I implement the refactored code?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cEF12X1m-kt5dJcu" /><figcaption>In Isolation 👀</figcaption></figure><p>Once this is done, you can swap out your old nav for the new one. At this point, there will likely be some conflicts with the old CSS. So what do we do?</p><p>We need need to write some <strong>hacky</strong> CSS now to help preserve our sanity later. This sounds counterproductive, but it’s actually a good strategy when refactoring. We can isolate, signpost and write this “quick fix” CSS until our refactored component looks as it should, then as the old CSS is removed and these conflicts disappear we can remove these hacks. Let’s look at a practical example with a nav.</p><ul><li><strong>Step 1</strong>: We’ve refactored the nav in isolation. It follows all best practices and is ready to replace the old clunky one. We swap out the HTML and import our new .scss file.</li><li><strong>Step 2</strong>: We’ve brought it in, but it doesn’t look right. The styling for the colour and font size are off because of the specificity of some older badly written code.</li></ul><pre>/* _links.scss (old) */</pre><pre>header &gt; nav li a {<br>    color: blue;<br>    display: inline-block;<br>    padding: 0 0 0 10px;<br>    font-size: 12px;<br>}</pre><pre>/* _new-nav.scss (new) */</pre><pre>.nav__link {<br>    padding-left: 10px;<br>    color: red;<br>    font-size: 14px;<br>}</pre><ul><li><strong>Step 3</strong>: We code to fix the problem, <strong>but </strong>we do so away from our clean CSS. In a well-commented, appropriately named file reserved solely for “bad” code (fixes.scss, hacks.scss, shame.scss or temporary.scss would all work).</li></ul><pre>/* _fixes.scss */</pre><pre>/*<br>Add !important declarations to the .nav__link class because more specific code from _links.scss is overwriting the colour and font-size.<br>*/</pre><pre>.nav__link {<br>    color: red !important;<br>    font-size: 14px !important;<br>}</pre><ul><li><strong>Step 4</strong>: Now we “attack” the bad CSS. We go in and remove the old stale CSS that was conflicting with our shiny new nav.</li><li><strong>Step 5</strong>: Now we can remove our fixes CSS for that specific conflict.</li><li><strong>Step 6</strong>: Repeat until old CSS and hacky CSS are removed.</li><li><strong>Step 7</strong>: Marvel at the beauty you have created.</li></ul><p>Harry Roberts explains this approach thoroughly in his talk from the WeAreDeveloper’s Conference in 2017.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FfvTryZjGyg8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DfvTryZjGyg8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FfvTryZjGyg8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/12e47fe36bd3728871a4ab3a7e2f3940/href">https://medium.com/media/12e47fe36bd3728871a4ab3a7e2f3940/href</a></iframe><h3>Conclusion</h3><p>The need for a refactor can be kept at bay by improving as you are going along and introducing useful build tools like linters, or products like <a href="https://cssstats.com/">CSS stats</a> into your workflow. But when and if a refactor is necessary, it should be approached methodically and as carefully planned out and iterated on as the actual product itself. Hopefully, the information above can help you better prepare.</p><blockquote>Feel differently? Have anything to add, agree, disagree? If you’ve got any feedback we’d love to hear from you — please leave a comment here, or drop us a line on Twitter. We’re <a href="https://twitter.com/InktrapDesign">@InktrapDesign</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61ef64601ebb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inktrap/refactoring-css-61ef64601ebb">Refactoring CSS</a> was originally published in <a href="https://medium.com/inktrap">Inktrap</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 ways learning programming is like learning a foreign language]]></title>
            <link>https://medium.com/inktrap/5-ways-learning-programming-is-like-learning-a-foreign-language-281dc35148ca?source=rss-3165cfff25fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/281dc35148ca</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[language]]></category>
            <dc:creator><![CDATA[Jon Barker]]></dc:creator>
            <pubDate>Wed, 11 Sep 2019 10:56:01 GMT</pubDate>
            <atom:updated>2019-09-11T10:56:01.551Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 ways learning to program is like learning a foreign language</h3><figure><img alt="A book to learn Spanish with the title “Fluent City”" src="https://cdn-images-1.medium.com/max/1024/0*4xDTSuic8fisstlP" /><figcaption>On the train to Fluent City | Photo by <a href="https://unsplash.com/@danielcgold?utm_source=medium&amp;utm_medium=referral">Dan Gold</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Summer is coming to an end, and a few members of the Inktrap team are trying to up their language game as their final holidays approach. Spanish, French, German and Arabic are being thrown around the office. But they’re not the only language we can hear in the room. What about JavaScript and PHP?</p><p>We started to wonder how similar learning a programming language is to a spoken language. Turns out, in our opinion, the process is pretty similar.</p><h4>You learn the concepts first, not the specifics</h4><p>Learning your first foreign language is difficult. It’s arguable that you actually learn more about <em>your own</em> language at this stage. Your native language is innate, you don’t really think about what you’re saying, it just comes out.</p><p>Then you begin to question yourself and end up asking, “why are we on a bus, but in a car?”. It feels like you’re losing your sanity. You question everything you’re saying in both your native and target language.</p><p>Programming is just the same, it’s less about the specifics and more about knowing what constructs are universal across multiple languages. Once these are understood, the knowledge is transferable.</p><p>In spoken languages, it’s things like pronouns, verbs, adverbs, and adjectives. In programming, it’s variables, conditionals, while loops and classes.</p><h4>“The more you know, the more you know you don’t know.” — Aristotle</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eqYtHKksS8bmfUoY" /><figcaption>Photo by <a href="https://unsplash.com/@isaacmsmith?utm_source=medium&amp;utm_medium=referral">Isaac Smith</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As you learn more and more you’ll find that you need to put in more effort to see an increase in your proficiency. Once the building blocks are out of the way you really need to dig deep to understand the nitty-gritty stuff.</p><p>With a spoken language, you start to see how much is really ahead of you when you try to do something beyond ordering a coffee. You bump into a native speaker and it dawns on you how many words you can’t recall immediately. Or how often you use incorrect grammar.</p><p>With any kind of development, you realise how much there is to learn when you go from <a href="https://medium.com/inktrap/why-side-projects-are-great-for-business-e679889cfcda">building a small side project</a> or website to working on a fully-fledged application with users and testing and feedback.</p><p>It may sometimes seem like you’re coming to terms with a concept, only for it to fork off into two additional things you need to learn. The <strong>most</strong> important thing is to not be dissuaded. As the French would say, “petit à petit l’oiseau fait son nid”. Or in English, “little by little, the bird makes its nest”.</p><h4>An IDE or good code editor will help</h4><p>Creating websites or software in a helpful IDE (Integrated Development Environment, like <a href="https://www.jetbrains.com/webstorm/">Webstorm</a>) is like speaking in your target language with an extremely useful assistant on hand.</p><p>They will show you where things are and provide you with shortcuts. If you type some code and make an error (kind of like preparing a speech), they’ll point it out and say “hey, watch out for that.”</p><p>You’ll be able to see your mistakes and make note of the ones you make the most often. They’ll help you clean up your code or if you were learning a language — your sentences, and point to the function (verb) you’re looking for.</p><p>You wouldn’t disregard help from a friend, don’t shun help from your computer.</p><h4>You learn by doing, not by learning</h4><p>It’s obvious that the key to learning a spoken language is by getting out there and practising. The same applies to learning a programming language. You will never fully understand all the little quirks of either if you don’t get out there and start making something with them.</p><p>You can’t read <em>JavaScript: The Good Parts </em>and expect to be able to immediately write something as renowned as <a href="https://vuejs.org/">Vue.js</a>. You can’t read about a language’s grammar and travel to its respective country and expect to hold a conversation straight off the plane.</p><p>Learning either is a practical, rather than an academic endeavour.</p><h4>In the end, you’re still crafting a story.</h4><p>So what is the purpose of learning all these words and structures and concepts anyway? It’s not just to proudly boast that you’ve learnt something well enough to be proficient in it.</p><p>In both cases, it’s to craft stories. It’s about making something or saying something that’s relatable or enjoyable for the person on the receiving end.</p><p>This is more apparent of course with spoken languages, but the end goal with programming or web development is the same. You’re not just storing cookies, you’re giving them an experience. Maybe you’re creating an enjoyable onboarding flow, or making a difficult process easier, as we did with current client<a href="https://www.farill.io/"> Farillio</a>, that makes handling legal documents easier.</p><p>All in all, the end result, as usual, is a connection with a person.</p><blockquote>Feel differently? Have anything to add, or just want to tell us about your awesome language skills? If you’ve got any feedback we’d love to hear from you — please leave a comment here, or drop us a line on Twitter. We’re <a href="https://twitter.com/InktrapDesign">@InktrapDesign</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=281dc35148ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inktrap/5-ways-learning-programming-is-like-learning-a-foreign-language-281dc35148ca">5 ways learning programming is like learning a foreign language</a> was originally published in <a href="https://medium.com/inktrap">Inktrap</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting a new job as a self-taught developer]]></title>
            <link>https://medium.com/inktrap/starting-a-new-job-as-a-self-taught-developer-dcd173e7d3c3?source=rss-3165cfff25fe------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcd173e7d3c3</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Jon Barker]]></dc:creator>
            <pubDate>Mon, 08 Apr 2019 16:23:31 GMT</pubDate>
            <atom:updated>2019-04-09T14:20:28.187Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to handle those first-day feelings</h4><p>Entering the world of web development as a self-taught professional is pretty scary. Mostly because web development isn’t a job that easily instils confidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5hCUtmsssUlHMEJK098K1g.jpeg" /></figure><p>For one, your self-assurance can be shaken by a seemingly untraceable bug or typo. This means your first few years of learning are plagued by a constant hum of “am I doing this right?”, which is occasionally broken by sporadic bouts of “I am the best” plunging right back to, “I know nothing.” For these reasons, accepting a job in an agency (or anywhere, really) can feel daunting.</p><p>You’re in a place where you <em>feel</em> as though your new colleagues know everything, whilst you’re still uncertain if you could write the DOCTYPE properly without your editor doing it for you. In your mind, your use of StackOverflow is a weakness. If you were as good as your peers you’d have all that knowledge at your fingertips. Just like they do… right?</p><p>Of course not. And, while these feelings of inadequacy can seem overwhelming, it’s important to face them head on and remind yourself that, although these emotions are valid, they needn’t generate the kind of angst they’re capable of.</p><p>Keep the following in mind so you can walk through the door excited for a realm of new possibilities:</p><h4>You were hired for a reason</h4><p>At some point, before you got the call or the e-mail offering you the position, the team sat around as a whole and decided that your competencies and attitude meant that you’re a good fit for the role.</p><p>They did this knowing everything that you had told them during the interview. Unless you told an enormous lie, they were fully aware of your current skillset. They were also aware of the skills that you’re looking to improve and felt strongly that you’d be able to pick up any necessary skills during your employment.</p><p>They <em>have</em> met you. They know what you’re capable of. They know what kind of person they want in this role. Trust in their judgement.</p><h4>You should be proud of how far you’ve come</h4><p>You have, through your own initiative, learnt a relatively complex range of skills to the point that a group of people have decided to offer you a position within their company.</p><p>The invitation to interview was not something that fell into your lap by accident. You earned the opportunity to be there. Believe it or not, this is a feat that should be acknowledged. (Mostly by you, but external acknowledgement is always nice too).</p><h4>You have things to learn and many (many) problems to solve</h4><p>You do not, and cannot, know everything. The same goes for your new found colleagues. You <em>will</em> see them looking at StackOverflow. You’ll see them watching tutorials. You’ll ask them a question, and they won’t know the answer. What separates a good developer from an average one is that a good developer is always ready to find a solution.</p><p>You should be comfortable with the idea of saying “I don’t know, but I’ll find out.” Learning is fun. It helps us grow whether personally or professionally, and we get to experience that little rush when a solution is found to a problem that previously seemed unsolvable. You’re not going to know the answer to <em>a lot</em> of questions throughout your career, and you should embrace it.</p><h4>You will be criticised (constructively, of course)</h4><p>At some point, the work you do will be under review. Maybe you made a mistake the team is trying to fix, maybe it’s a run-of-the-mill code review, or maybe you’ve just asked a colleague for help and they’ve spotted something while looking at your screen.</p><p>In one way or another, you might get told that something you’ve done is wrong, or could be done another way. A better way! That’s right, you’ve done something incorrectly, or not optimally.</p><p>You shouldn’t fret. It’s easy to get defensive when feedback is being given, but good feedback is never about you personally and is given out with good intentions. Take the information, learn from it, and try to implement the suggested change next time.</p><h4>It’s in their interest to take care of you</h4><p>Any sensible business has a system for the induction of their new employees. You wouldn’t be able to break anything crucial, even if you wanted to.</p><p>At <a href="https://www.inktrap.co.uk/">Inktrap</a>, my first day included a relaxed introduction to the team, getting set up on the computer and dealing with any paperwork.</p><p>Your induction will likely follow a similar pattern. When you move on to the development side of things, you might work on some internal projects before moving to client work. Your new employer has no interest in making this difficult for you.</p><h4>Don’t get rid of <em>all</em> the doubt</h4><p>You should acknowledge your hard work, and feel a sense of pride when you think of all you’ve taught yourself. However, we don’t want the pendulum to swing too far to the other side.</p><p>We want doubt. Doubt makes us question whether our approach is the right one. It makes us ask for help, which in turn makes us grow and adds to our understanding of how things work. It makes us better developers.</p><p>Ultimately, when walking through those doors on your first day it’s essential to have faith in yourself. It’s also important to have faith in those who hired you, and understand that they know why they offered you the position. Take pride in how much you have learnt and be confident in your ability to learn more.</p><p>In short, you’ll be fine.</p><blockquote>Got any other tips to get over those first day jitters? How have you helped your junior employees settle in? If you’ve got any advice we’d love to hear from you — please leave a comment here, or drop us a line on Twitter, we’re <a href="https://twitter.com/InktrapDesign">@InktrapDesign</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcd173e7d3c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inktrap/starting-a-new-job-as-a-self-taught-developer-dcd173e7d3c3">Starting a new job as a self-taught developer</a> was originally published in <a href="https://medium.com/inktrap">Inktrap</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>