<?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 David Johnston on Medium]]></title>
        <description><![CDATA[Stories by David Johnston on Medium]]></description>
        <link>https://medium.com/@david_63019?source=rss-2ae7cb60197b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*CuHmwVA5amJgLZ1Y</url>
            <title>Stories by David Johnston on Medium</title>
            <link>https://medium.com/@david_63019?source=rss-2ae7cb60197b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:00:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@david_63019/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[Tech Job Interviews: Intellectual humility vs Selling yourself?]]></title>
            <link>https://medium.com/@david_63019/tech-job-interviews-intellectual-humility-vs-selling-yourself-dbb563c92a64?source=rss-2ae7cb60197b------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbb563c92a64</guid>
            <category><![CDATA[intellectual-honesty]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[tech-interview]]></category>
            <dc:creator><![CDATA[David Johnston]]></dc:creator>
            <pubDate>Wed, 06 Mar 2019 23:07:49 GMT</pubDate>
            <atom:updated>2019-03-06T23:26:51.001Z</atom:updated>
            <content:encoded><![CDATA[<p>Something I grapple with in attending IT job interviews is how much to express intellectual humility, and to admit where I have less experience in a thing, vs how much to ‘fake it till you make it’, or to tell the interviewer what they want to hear, such that they’re going to comfortable hiring you.</p><p>I think I’m a pretty decent programmer.</p><p>For what it’s worth, I thought I was a pretty decent programmer a year ago too, and I think I’m a much better programmer now, than I was then. (To give a couple of examples, a year ago I didn’t know about async/await, and I was by default, doing object oriented programming, not being aware of the usefulness of the functional paradigm in general application development).</p><p>I think a big problem in IT as a culture, is a lack of intellectual humility, where individuals will favour using bluster and egotistical chest-beating over admitting that they don’t fully understand a thing.</p><p>This kind of culture can become a feedback loop, if other programmers see that admitting they don’t know a thing just leads to them being sidelined, and bluster ends up being persuasive, then the incentive is there for them to adopt the same strategy.</p><p>Favouring bluster over humility can prevent a developer from improving too — in order to understand the thing, you first need to admit that you don’t know it. Generally — a company with a strong culture of intellectual humility, I think, is going to attract and develop people with better skills — as it fosters their intellectual curiosity.</p><p>It’s understandable how bluster can be persuasive — if either a non-technical manager, or a stakeholder who doesn’t have expertise in that particular domain, is required to make a decision about who to listen to, or who should lead the project — they don’t have the technical expertise to evaluate the arguments — and so have to make a decision based on just who sounds the most persuasive (or who has the better past track record, I guess).</p><p>But myself personally, I’m aware that the Dunning-Kruger effect is a thing — that is — that people who have more experience in a thing are more likely to express doubts or concerns about it, while people who have less experience are more likely to overestimate their abilities — they don’t know enough to know what they don’t know.</p><p>This brings us around to job interviews.</p><p>A job interview is typically, in part, evaluating one’s technical capability to do the job.</p><p>Well-crafted technical challenges and questions are in my opinion a good way to way to establish a good baseline on certain narrow metrics. An interview process that doesn’t include good technical challenges should be considered a red flag.</p><p>However, technical questions can’t really cover the broad scope of building an entire solution, they’re really more there to <em>disqualify </em>people for not knowing some fundamentals, rather than qualify them.</p><p>I think to get a proper understanding of someone’s technical capability you need to have a general conversation — or it involves a more long-winded, multi-session interview process.</p><p>If I were interviewing someone, and I ask them to talk about their comfort with XYZ technology — and they told me they were an expert at it, knew it inside and out, unless they had twenty years experience with it, this kind of response would more likely be a red flag to me than be persuasive. At least the person who says ‘Well I’m good at these things, but don’t have much experience with these things’ knows what they don’t know.</p><p>That’s the way I might run things if I were conducting the interview — but what about when I am being interviewed?</p><p>To give a real example — my core experience is frontend development, but I have some experience with Kubernetes, I’ve set up my own Kubernetes clusters, added TLS certificates and mapped domain names to one, and set up a basic automatic ‘build and deploy on commit’ CI triggers for it.</p><p>I’d hazard to say that of all the people who know what Kubernetes is — I’m above the 50% percentile in terms of technical ability.</p><p>However, I am certainly not an expert on Kubernetes. If you made me responsible for doing all of that stuff for a production Kubernetes cluster, you could expect mistakes to be made.</p><p>So in an interview — and someone asks me about my experience with Kubernetes — do I confidently say that I can do the things? Or do I talk about the things that I have done, while highlighting the my experience is somewhat limited?</p><p>I think ultimately — it’s a matter of gauging who the interviewer is.</p><p>If they’re a technically savvy, intellectually humble person, then highlighting both your areas of strength, as well as the areas that you know you are weaker in, is going to be impressive.</p><p>However, if they’re a non-technical manager, who just needs to be feel confident that project will go smoothly, and you’re confident that you can deliver that — then sure, be aware that what you’re convincing them is not a technical capability, but that you’re reliable and that project will go smoothly. It’s an emotional decision you’re dealing with — and in that scenario — more of a sales pitch than a technical assessment.</p><p>This comes around to some final advice — if you are a non-expert hiring manager, and you’re wanting to develop a culture of intellectual humility and curiosity — then my advice is to have a technically savvy person on the interview panel — and don’t let someone admitting they don’t know a thing be a disqualifier; focus on the things that they do know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbb563c92a64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple advice for recent IT graduates to upskill your career quickly.]]></title>
            <link>https://medium.com/@david_63019/simple-advice-for-recent-it-graduates-to-upskill-your-career-quickly-db86133b32ac?source=rss-2ae7cb60197b------2</link>
            <guid isPermaLink="false">https://medium.com/p/db86133b32ac</guid>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[David Johnston]]></dc:creator>
            <pubDate>Tue, 11 Sep 2018 13:44:25 GMT</pubDate>
            <atom:updated>2018-09-14T04:09:38.593Z</atom:updated>
            <content:encoded><![CDATA[<ol><li>Listen to tech podcasts. <a href="https://syntax.fm/">Syntax.fm</a> is what I’d recommend for web developers. <a href="https://medium.com/@david_63019/my-favourite-tech-podcasts-c20edf92e41f">See my other podcast recommendations here.</a></li><li>The best way to learn is to be surrounded by programmers who are better than you, (and who are not assholes), so that’s what you should be looking for in a job — are these guys good programmers?</li><li>There might be downtime at your work, in which case, find a project to fill the time, and <em>don’t feel guilty about it. </em>This is something I’ve retrospectively realised — having gone out on my own because I resented having to be a bum on a seat for 40 hours a week, when I could be working on my own projects; I’m realising now that I could have been spending that time far more effectively doing the learning that I’m doing now, <em>and being paid for it.<br></em>The trick is, in terms of both professionalism and alleviating any guilt you might feel — is to find a project that<em> is work related, </em>it’s probably not going to fly to create that MMORPG on work time. <br>You could just play with framework that might be helpful, create a hello world application in it — but personally I’ve found that just playing with the framework for the sake of learning it isn’t a particularly motivating way to learn — what’s better is to have an end goal in mind, and you’re using that framework to achieve it. That lets you see the value in what the framework is giving you. <a href="https://medium.com/@david_63019/how-a-side-project-can-make-you-a-better-programmer-and-how-to-choose-the-right-side-project-56dfcdaf3c71">See my post here about choosing a side project.</a></li><li>Do the #100daysofcode challenge. It keeps you on your toes and really gets you doing that incremental learning a fast pace.</li><li>Attend (good) meetups. This one may depend on the city you are in. When I started my career — I attended a few meetups was quickly discouraged, as these were just meeting at a bar or cafe and shooting the shit. I’m not saying don’t do that — but they’re not the meetups I have in mind. I mean attend meetups where people give presentations — these ones will let you keep a finger on the pulse of where IT is at.</li><li>If you’re a web developer — then build your own website — there’s a lot to learn, that your workplace is probably taking care of for you.</li><li>Stay curious. Programming is fun and always evolving. You’re riding a wave and it’s good to stay where it’s good and fun.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db86133b32ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My favourite tech podcasts]]></title>
            <link>https://medium.com/@david_63019/my-favourite-tech-podcasts-c20edf92e41f?source=rss-2ae7cb60197b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c20edf92e41f</guid>
            <category><![CDATA[podcast]]></category>
            <dc:creator><![CDATA[David Johnston]]></dc:creator>
            <pubDate>Thu, 06 Sep 2018 01:14:17 GMT</pubDate>
            <atom:updated>2018-09-06T01:14:17.942Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Syntax</strong></p><p><a href="https://syntax.fm/">https://syntax.fm</a></p><p>I discovered this podcast recently, and I’m been bingeing it hard.</p><p>The format is a conversation between the two presenters, Wes Bos and Scott Tolinski — where they mostly talk about Javascript related web development.</p><p>As far as tech podcasts go — I’ve found this one the most practical in terms of learning web development concepts.</p><p><strong>Software Engineering Daily</strong></p><p><a href="https://softwareengineeringdaily.com/">https://softwareengineeringdaily.com/</a></p><p>This is the first explicitly technical podcast I got into.</p><p>The format is the host Jeff Meyerson interviewing various industries leaders and about their field, and getting quite technical on it.</p><p>I’m always impressed by the range of knowledge Jeff has — whatever the concept is, Jeff always seems to be able to introduce it and ask good questions about it.</p><p>This podcast can be a bit drier than some of the others — and I don’t listen to all the episodes if they’re something I’m not especially interested in.</p><p>I have found it good for introducing concepts that I’ve heard of, but didn’t really know anything about (eg. Flutter, Web Assembly). This is a good podcast for keeping a finger on the pulse of where tech is at.</p><p><strong>Recode Decode</strong></p><p><a href="https://www.recode.net/recode-decode-podcast-kara-swisher">https://www.recode.net/recode-decode-podcast-kara-swisher</a></p><p>The the format is an interview between the host Kara Swisher and often VIP guests (eg. Mark Zuckerberg) where they talk about the direction of tech, usually with more of a political of sociological lens.</p><p>Kara is quite a refreshing host to listen to — she facilitates the interview well, in a way that allows the guest talk about their worldview — but is not afraid to hammer home her opinion.</p><p><strong>Decrypted</strong></p><p><a href="https://www.bloomberg.com/podcasts/decrypted">https://www.bloomberg.com/podcasts/decrypted</a></p><p>Infotainment podcast by Bloomberg, this podcast presents the more interesting issues in tech in an entertaining and enlightening and accessible way.</p><p><strong>Bonus Podcast: Planet Money</strong></p><p><a href="https://www.npr.org/sections/money/">https://www.npr.org/sections/money/</a></p><p>This isn’t a tech podcast, but an economics one.</p><p>Short form podcast — each episode is only about twenty minutes long — it presents interesting little anecdotes from the world of economics.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c20edf92e41f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My #100DaysOfCode commitment.]]></title>
            <link>https://medium.com/@david_63019/my-100daysofcode-commitment-1890692cf9af?source=rss-2ae7cb60197b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1890692cf9af</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[100daysofcode]]></category>
            <dc:creator><![CDATA[David Johnston]]></dc:creator>
            <pubDate>Mon, 03 Sep 2018 02:55:48 GMT</pubDate>
            <atom:updated>2018-09-03T02:55:48.245Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m doing the<a href="https://www.100daysofcode.com/"> #100daysofcode</a> challenge.</p><p>I’m not strictly following the ‘official’ rules though, here’s the challenge I’m setting for myself:</p><p>Each day, I’m going to either learn something, or clarify something technical, or otherwise make some kind of progress on some kind of project.</p><p>Some ideas I have to cover are:</p><ul><li>Discovering or learning more about VSCode extensions or features.</li><li>Understanding some grittier details about Javascript (eg. prototypal inheritance).</li><li>I think my new side project is to start building a website with CI/CD running on a kubernetes cluster.</li></ul><p>If the thing I’ve learned can be summarised in a tweet, then I’ll just tweet about it, and likely point to the tutorial I’ve read. If it’s something more in depth, I’ll write a post about it.</p><p><a href="https://twitter.com/search?f=tweets&amp;q=from%3Ablacksheepcode%20%23100daysofcode&amp;src=typd">See my twitter feed here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1890692cf9af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a side project can make you a better programmer — and how to choose the right side project.]]></title>
            <link>https://medium.com/@david_63019/how-a-side-project-can-make-you-a-better-programmer-and-how-to-choose-the-right-side-project-56dfcdaf3c71?source=rss-2ae7cb60197b------2</link>
            <guid isPermaLink="false">https://medium.com/p/56dfcdaf3c71</guid>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[David Johnston]]></dc:creator>
            <pubDate>Sun, 02 Sep 2018 10:38:32 GMT</pubDate>
            <atom:updated>2018-09-02T10:41:14.444Z</atom:updated>
            <content:encoded><![CDATA[<p>Early in my career, I found the common career advice for developers — to contribute to open source, have a side project, maintain a blog, etc — <a href="https://medium.com/@david_63019/alpha-geek-syndrome-in-it-culture-b28a1231de13">a little frustrating.</a> I was of the opinion that forty hours a week in a paid job should be enough development, and that it’s better to maintain a healthy well rounded lifestyle than be an uber geek who lives and breathes code.</p><p>I still stand by this — I think that if a firm is looking to hire developers who contribute to opensource — they should be willing to have those developers contribute to opensource on work time, and it’s important to have a good work life balance.</p><p>However — the reality with commercial programming work, especially for a junior developer, is that typically you’ll end up slotting into a project with a fairly limited scope of responsibilities. The technical architecture and design patterns will have already been chosen, the deployment process will already be established. You’ll likely be continuing following the established ways of doing things, which is fine — you’ll still be learning, but perhaps in a limited way that isn’t as transferable if you leave the company.</p><p>After having made a few attempts at starting a side project (I had some quickly aborted attempts at making a bitcoin trading bot, playing with public transport type algorithms, and making a Panama Papers explorer. I also for a while hosted an online portfolio, but I found it so boring and unfun to work on.), — and finding it hard to maintain the motivation to work on it, when I could be playing board games with friends instead I eventually did stumble on a side project that stuck with me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*colvyFXLpYbFmaUko5qXNw.jpeg" /></figure><p><a href="https://geoplanets.io/">geoplanets.io </a>is an interactive geometric art generator. It started with me seeing a gif on Facebook that purported to highlight the the beauty of the relationship between Earth and Venus:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*u2XEQKpsGf3F8mnKDod0IQ.gif" /></figure><p>I thought — ‘Yeah, that’s cool, but firstly, the orbits of Earth and Venus aren’t perfectly circular, and secondly, if you draw links and regular intervals between any two points orbiting a center, you’re going to get something neat looking’.</p><p>To demonstrate, I quickly built a demo using HTML5 canvas and JQuery, and allowed the user to modify the speed and the distance of the two orbits.</p><p>And then I thought ‘Hey, that’s kinda neat, what if I added a third orbit? What if they orbited each other? What if instead of a circular orbit, it was triangular?’. And the idea stuck, so I got onto fleshing out the idea as a fully fledged webapp.</p><p>At this point — while I was comfortable writing HTML and JavaScript, and deploying applications within the development environments at my work — I didn’t know how to deploy my own application from scratch, for the public to see.</p><p>In order to build the app — I needed to learn:</p><ul><li>A frontend framework (I chose React).</li><li>Various hosting solutions — I looked at Heroku, AWS and GCP.</li><li>I wanted to allow people to share their creations to their own Facebook feeds, so I learned about social sharing meta tags.</li><li>I also started getting familiar with the Twitter API, (and working with public APIs in general), so I could automatically post images to <a href="https://twitter.com/geoplanetsio">my Twitter feed.</a></li><li>I learned how to set up DNS configuration to point my own domain name to my hosted website.</li><li>I learned how to publish NPM modules.</li></ul><p>The point here I want to highlight — is that I didn’t set out thinking ‘I need to learn these things — what’s a side project that would suit?’ — the side project necessitated learning these things.</p><p>And that’s I think the most important thing for a side project — a side project has to be enjoyable and has to make you want to work on it.</p><p>To this end — I think what makes a good side project is something a little silly, and a bit simple. If you’re interested in being a web developer — then hosting your own website is a good idea — there’s a lot to learn. What’s on the website? I recommend against going for a conventional portfolio — though, that’s me — instead maybe make a small game, or a chatbot, something that <em>you </em>are going to find fun to work on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56dfcdaf3c71" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alpha geek syndrome in IT culture.]]></title>
            <link>https://medium.com/@david_63019/alpha-geek-syndrome-in-it-culture-b28a1231de13?source=rss-2ae7cb60197b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b28a1231de13</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <dc:creator><![CDATA[David Johnston]]></dc:creator>
            <pubDate>Sun, 02 Sep 2018 09:38:41 GMT</pubDate>
            <atom:updated>2018-09-02T09:38:41.118Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>nb. I wrote this post a couple of years ago. Some aspects of my life have since changed, and in these days I’m more likely to spend time on my weekend writing code. I have also discovered listening to IT podcasts while I go for a walk or whatever.</strong></p><p>I think IT culture can suffer from an ‘alpha geek’ syndrome — where total commitment to code and technology is valued above all else.</p><p><a href="http://www.supercoders.com.au/blog/evidenceofpassion.shtml">This post at Super Coders IT</a> (an IT recruitment firm, which I have to be fair, I think they have a great website and blog posts) expresses this, in the form of a list activities that demonstrate a developer has passion:</p><ul><li>Spends lots of personal time at home reading software development related books, blogs and websites</li><li>Spends lots of personal time at home writing code and developing personal software projects</li><li>Has made substantial contributions to open source projects</li><li>Has created their own software product which is available for download on the web</li><li>Has written articles for online publications/magazines</li><li>Coding since childhood/high school</li><li>Participates in programming competitions</li><li>Writes a blog</li><li>Has an account on Stack Overflow which shows a history of participation</li></ul><p>It’s not uncommon for employers to ask if a candidate works on projects outside of work — seeing this as a sign of being a good programmer.</p><p>The problem with this is it ignores the other human elements of the programmer. It assumes that good programmers are another species, closer to a computer than a human, who derive pleasure from all things technology related. <a href="http://antjanus.com/blog/thoughts-and-opinions/im-a-developer-but-its-not-my-passion/">This blog post here articulates well a similar opinion that I’m expressing here.</a></p><p>I’m a single, thirty year old. I have a plenty of free time.</p><p>I could dedicate my weekends to contributing to an open source project, or answering questions on Stack Overflow — but do you know what I prefer doing?</p><ul><li>Writing this blog.</li><li>Running and exercise.</li><li>Learning ceroc.</li><li>Playing board games.</li><li>Socialising</li><li>Taking photos for my <a href="https://www.facebook.com/humansofnewtownwgtn">Humans of Newtown</a> Facebook page.</li></ul><p>If I were a married man with children, I’d have even less free time — I would certainly be prioritising spending time with my children over writing/reading code.</p><p>Some people do live and breathe code, I appreciate that. These coders probably are likely to better coders, having more familiarity with the framework or library.</p><p>At the same time — the human aspects of being a coder shouldn’t be understated. When you first walk in to the office on a Monday morning, and you ask your colleague what they got up to on the weekend, what do you want to hear? ‘I learned a new web framework, and fixed some bugs for this open source project I’m contributing to’ or ‘I went surfing and then played board games some friends.’ Which contributes to a more congenial work atmosphere?</p><p>My intention here isn’t to disparage either person. IT attracts a quite a wide range of people, and there are plenty of people who would prefer talking about something technical, than about social interactions. At the same time, others would much rather talk about the movie you saw on the weekend, than more code. The point of workplace socialising is primarily for relaxation and to build relationships after all, rather than spreading technical knowledge.</p><p>It would however, be a mistake to think that super-nerds are the only people that an IT firm should value, for two reasons.</p><p>Firstly — the firm risks missing out on perfectly capable developers, simply because they value spending their spare time on other things, rather than code.</p><p>Secondly — the firm’s culture becomes ‘alpha nerd’ focused, and this could lead a hyper-competitive and workaholic type atmosphere.</p><p>This might be beneficial for the company in the short term, or perhaps even necessary for a bleeding edge technology company or start up, but I would be very cautious taking a company’s culture that way. In the long run it could lead to interpersonal conflicts and uncooperative behaviour.</p><p>At the end of the day, I guess company cultures vary from firm to firm, and people who live and breathe code might feel more comfortable at firms who have a culture that values that. But I would suggest that it would be a mistake to think that all good developers don’t have interests outside of code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b28a1231de13" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>