<?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 Neil O&#39;Connor on Medium]]></title>
        <description><![CDATA[Stories by Neil O&#39;Connor on Medium]]></description>
        <link>https://medium.com/@neil.oconnor?source=rss-c0d78c579e9f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*xsfoCrDeBNYowCTe0k-gsA.jpeg</url>
            <title>Stories by Neil O&amp;#39;Connor on Medium</title>
            <link>https://medium.com/@neil.oconnor?source=rss-c0d78c579e9f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:49:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@neil.oconnor/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[TLA+ for startups (part 2)]]></title>
            <link>https://medium.com/koodoo/tla-for-startups-part-2-1ef288adab39?source=rss-c0d78c579e9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ef288adab39</guid>
            <category><![CDATA[specifications]]></category>
            <category><![CDATA[tla-plus]]></category>
            <category><![CDATA[formal-methods]]></category>
            <category><![CDATA[software-design]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Neil O'Connor]]></dc:creator>
            <pubDate>Thu, 05 Dec 2019 16:58:31 GMT</pubDate>
            <atom:updated>2019-12-12T15:18:47.001Z</atom:updated>
            <content:encoded><![CDATA[<h4>The elevator pitch</h4><p><em>This is the second in a series of articles on why the use of formal specification languages — and specifically the language TLA+ — isn’t a completely mad idea for startups. In fact, </em><a href="https://medium.com/koodoo/tla-for-startups-part-1-8b162863824b"><em>I made the case in the first article</em></a><em> that they could actually prove to be a match made in heaven.</em></p><p><em>You may agree or disagree with my claim at your own discretion. But I will plough on and start working through a problem using TLA+, and we’ll see if it helps or hinders.</em></p><h3>Caveat emptor</h3><p>Let’s clear one thing up from the start: <strong>I’m not going to attempt to teach you about the theory of TLA+ or how to use it</strong>. I’m also not going to make any further attempts to sell its merits to you, beyond what I wrote in the first article.</p><p>At the time of writing, I have learned what I consider to be the minimum amount necessary to roll my sleeves up and make a start. I have read Hillel Wayne’s book, <a href="https://www.amazon.co.uk/Practical-TLA-Planning-Driven-Development/dp/1484238281/ref=sr_1_1">Practical TLA+</a>, I have worked through <a href="http://lamport.azurewebsites.net/video/videos.html">Leslie Lamport’s Video Tutorials</a>, I have installed the <a href="https://lamport.azurewebsites.net/tla/toolbox.html">relevant tools</a>, and I have watched and read a few interesting blog posts and conference talks.</p><p>I have a background in Computer Science and a reasonable head for mathematics, but I think any logically-minded person could get to the same stage as I am currently at, with a little application.</p><p>From this point on, I’ll dive straight into describing the problem domain and attempting to model it in TLA+. I’ll talk you through my thought processes as I go along, and will add the occasional explainer for certain important constructs, but otherwise will assume you know what they mean.</p><h3>The Elevator Pitch</h3><p>Our problem domain will be <strong>elevator control software</strong>. Over on this side of the pond we call them lifts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*44o14m7kvJAvIKkhpTtOtQ.jpeg" /><figcaption>A typical British lift</figcaption></figure><p>Why do I think this is an interesting problem to model?</p><ol><li>Everyone reading this, with the possible exception of claustrophobes, will have used an elevator. Even the claustrophobes will understand the basics of how an elevator operates.</li><li>At its simplest, the control software for elevators should be pretty straightforward to model, so we can start with some easy but valid examples (e.g. 1 car, 2 storeys).</li><li>However, the problem gets exponentially more complex as you add more cars, more storeys and more safety features. This should allow us to validate that TLA+ is indeed capable of modelling these more complex scenarios without brain-melting amounts of extra effort.</li><li>They are a nice example of a finite state machine, which TLA+ is ostensibly good at modelling.</li><li>We can make suitable abstractions without compromising the usefulness of the solution. For example, we can model the logic about how calls to the elevator are received and serviced, without having to worry about the mechanics of how the elevator actually moves — gears, pulleys, power, door mechanisms, etc. We can reasonably assume that someone else has got all that covered.</li></ol><p>Agreed? OK, let’s get stuck in.</p><h3>The entry-level elevator</h3><p>Leaving aside the simplest possible elevators, such as manually operated ones or stairlifts, the entry-level elevator that would benefit from control software would be one that:</p><ul><li>Has a single car</li><li>Travels between just two floors/storeys (I’ll use the words interchangeably, sorry!)</li><li>You can press a button from either floor to call the car (and even if it’s in use, it remembers your call request)</li><li>Once inside the car, you just press a ‘go’ button and don’t have to select the destination floor</li><li>Doesn’t have any pauses built into its behaviours (allowing passengers time to enter and exit)</li></ul><p>We might visually represent it like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*l8_RAk4OlgtPXR5afRd1QA.png" /></figure><p><em>(American readers will be happy with the numbering above, but may not realise we Europeans call the storey at ground level the “ground floor” or simply “0”. I prefer the European convention, but we’ll go with the American convention for one simple reason: TLA+ sequences are 1-based!).</em></p><p>You might at this point wish to politely point out that elevators without doors are a little dangerous. But they wouldn’t be the first — I spent many a happy afternoon hopping on and off the <a href="https://www.bbc.co.uk/news/av/uk-england-south-yorkshire-42997131/sheffield-university-s-paternoster-lift-in-motion">paternoster elevator</a> during my university years in Sheffield. For now, let’s accept it as a valid simplification.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FdvvcYruZSxAfm%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FdvvcYruZSxAfm%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FdvvcYruZSxAfm%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/1f149cfcbadddf02b54d07524aeb7d96/href">https://medium.com/media/1f149cfcbadddf02b54d07524aeb7d96/href</a></iframe><h4>Let’s make a start</h4><p>Let’s start writing our TLA+ spec. We’ll start by trying to define our constants, variables and initial state. Let’s say the set of known Storeys is a subset of the set of Integers, with the car’s initial location being at an arbitrary storey.</p><p>We’ll prefix our state formulas and actions with EC for “Elevator Controller”.</p><pre><strong>CONSTANTS</strong> Storeys</pre><pre><strong>VARIABLES</strong> carLocation</pre><pre><strong>ASSUME</strong> Storeys \subseteq Int</pre><pre>ECInit == carLocation = <strong>CHOOSE</strong> s \in Storeys : TRUE</pre><p><em>Remember that the CHOOSE operator indicates that an arbitrary value could be selected for carLocation from the set of available storeys. This is not the same thing as saying it WILL select one of those values or telling it HOW to select one— we are building a specification to check, not code to execute.</em></p><p><strong><em>UPDATE: </em></strong><em>Following helpful feedback from the TLA+ community, it was pointed out that the use of the CHOOSE operator here could mask an error, as it may leave some states unexplored (it will fix the carLocation to an arbitrarily chosen value). Instead, we can simply use carLocation \in Storeys to explore all possible starting states.</em></p><p>Are we happy with that? Well, for one thing, it assumes the system is starting up with the car positioned at a storey and not between two storeys. Probably a reasonable assumption for the time being. Perhaps we should’ve called the <em>carLocation</em> variable <em>carLastHaltedLocation</em>, but let’s keep it simple for now!</p><p>What else can we assume about our starting state? We can assume something about the car’s movement. For now we will define the car’s potential movement states as “idle”, “going up” or “going down”, which we will represent numerically as 0 for idle, 1 for going up and -1 for going down.</p><p>The changed bits of the spec now look like this:</p><pre><strong>VARIABLES</strong> carLocation, carTravelStatus</pre><pre>ECInit ==<br>    /\ carLocation \in Storeys<br>    /\ carTravelStatus = 0</pre><p>We can also assume something about the status of the two ‘call’ buttons on the walls and the ‘go’ button inside the car, namely that they are all in a ‘clear’ state.</p><pre><strong>VARIABLES</strong> carLocation, carTravelStatus, callRequest, goRequest</pre><pre>ECInit ==<br>    /\ carLocation \in Storeys<br>    /\ carTravelStatus = 0<br>    /\ callRequest = [s \in Storeys |-&gt; 0]<br>    /\ goRequest = 0</pre><p><em>I’m not going to explain every concept or construct as we go along, but this one, or a variant of it, is something you will see a lot of in TLA+ specs:</em></p><pre>callRequest = [s \in Storeys |-&gt; 0]</pre><p><em>callRequest is here defined as a function where each value of set Storeys maps to the value of 0. As the set Storeys currently only contains the values 1 and 2 for our simple elevator, this might be written as follows: callRequest[1] = 0 and callRequest[2] = 0.</em></p><p><em>This is an example of a very elegant operator in TLA+, which enables you to describe something fairly complex about the properties of the system you are modelling without having to worry about how you might implement it in code.</em></p><h4>What’s next?</h4><p>We’ve defined a fairly rudimentary starting state. Now we will go about identifying some potential next states (known as “actions” in TLA+).</p><p><strong><em>Car is called</em></strong></p><p>The first ‘next state’ action we will describe is that the elevator is called from the other floor. Visually we could represent this as follows (a button is lit up after being pressed):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*OQxHCuodPonEm6k-O0GfhA.png" /></figure><p>Here’s how we’ll write this in TLA+:</p><pre>ECNextCall(s) ==<br>    /\ callRequest[s] = 0<br>    /\ callRequest&#39; = [callRequest <strong>EXCEPT</strong> ![s] = 1]<br>    /\ <strong>UNCHANGED</strong> &lt;&lt; carLocation, carTravelStatus, goRequest &gt;&gt;</pre><p><em>Let’s break this down into plain English as best we can.</em></p><p><em>callRequests[s] = 0 means that, for the storey our elevator is being called from, the callRequest record has a ‘before’ value of 0 (i.e. it wasn’t already called).</em></p><p><em>callRequest’ = [callRequest EXCEPT ![s] = 1] means that the elevator hasn’t been called from any other storey, only s, so the value of the callRequest[s] will be 1.</em></p><p><em>The UNCHANGED line means that none of our other variables are modified.</em></p><p>So essentially what we have described here is that one possible next state is that a call request is made, turning the 0 to 1 in the relevant <em>callRequest</em> record, and nothing else changes in the process.</p><p><strong><em>Service a call</em></strong></p><p>Another ‘next state’ action we will describe is that the elevator proceeds to the storey from which it has been called:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*VE_zsN5NB5xoQ6zppU1qVg.png" /></figure><p>In our specification, we now need to reflect the fact that the car is moving in this state:</p><pre>ECNextServiceCall(s) ==<br>    /\ carLocation # s<br>    /\ carTravelStatus = 0 <br>    /\ carTravelStatus&#39; = <strong>IF</strong> s &gt; carLocation <strong>THEN</strong> 1 <strong>ELSE</strong> -1<br>    /\ <strong>UNCHANGED</strong> &lt;&lt; callRequest, goRequest, carLocation &gt;&gt;</pre><p><em>What does this mean?</em></p><p><em>carLocation # s means that the car’s current location is not the same as the storey it was called from.</em></p><p><em>The two conditions for carTravelStatus mean that the car was not already moving, and that it either goes up or down depending on whether the call came from the upper floor or the lower floor.</em></p><p><em>The UNCHANGED bit means that the callRequest remains in place, and carLocation remains unchanged, until the elevator gets there (and goRequest is also unaffected).</em></p><p><strong><em>Car arrives after call</em></strong></p><p>Our next potential action will describe the car arriving at the requested floor, as shown by:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*nQUn5OJ85dGHjGeWXRMeCw.png" /></figure><p>We will specify this in TLA+ as:</p><pre>ECNextArriveCall(s) =<br>    /\ carLocation # s<br>    /\ carTravelStatus # 0<br>    /\ callRequest[s] = 1<br>    /\ carLocation&#39; = s<br>    /\ carTravelStatus&#39; = 0<br>    /\ callRequest&#39; = [callRequest <strong>EXCEPT</strong> ![s] = 0]<br>    /\ <strong>UNCHANGED</strong> &lt;&lt; goRequest &gt;&gt;</pre><p><em>Breaking this down:</em></p><p><em>carLocation before entering this state was NOT the storey being arrived at (s), but after entering this state it is.</em></p><p><em>carTravelStatus # 0 describes that the car was in motion, but upon arriving carTravelStatus’ = 0 means it then stops moving.</em></p><p><em>callRequest was 1 for the target storey before the car arrives, but becomes 0 after the car arrives; all other callRequest records remain unchanged.</em></p><p><strong><em>Go request</em></strong></p><p>So people can request the car from another storey, but passengers can’t yet tell it to go once they get in! So let’s visualise that:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*xtK9mrkk5h2B6w0OrkJvow.png" /></figure><p>We will specify this as follows:</p><pre>ECNextGoRequest ==<br>    /\ goRequest = 0<br>    /\ carTravelStatus = 0<br>    /\ goRequest&#39; = 1<br>    /\ carTravelStatus&#39; = <strong>IF</strong> carLocation = 1 <strong>THEN</strong> 1 <strong>ELSE</strong> -1<br>    /\ <strong>UNCHANGED</strong> &lt;&lt; carLocation, callRequest &gt;&gt;</pre><p>So when the passenger hits the Go button, if it wasn’t pressed already, the car starts moving towards its destination.</p><p>Oh wait. There might be a flaw in this. Just by starting to write out the action formula, and identifying the preconditions (unprimed variables) and postconditions (primed variables) of the action, it made me realise something: what if I got in the car, and before I could hit the Go button, someone else on the other floor hit the Call button? Should I then be able to hit Go anyway and see it light up? I think I should.</p><p>The point here is not that we need to find the perfect solution right away, but the act of attempting to write the specification has forced me to think about edge cases or “non happy path” behaviours. It’s a perfectly valid behaviour for an elevator — and one that is no doubt happening all over the world right now as we speak — for the car to start moving towards another storey before the passenger has managed to select their preferred destination. TLA+ helps us to reason about these behaviours in a formal way.</p><p>For now, let’s split out the Go request from the servicing of the request:</p><pre>ECNextGoRequest ==<br>    /\ goRequest = 0<br>    /\ goRequest&#39; = 1<br>    /\ <strong>UNCHANGED</strong> &lt;&lt; carTravelStatus, carLocation, callRequest &gt;&gt;</pre><p><em>Translated, this now means the goRequest moves from a 0 to 1 when entering this state, and that’s it. We’re assuming nothing else about the location or travel status of the car, or any call requests made from the storeys.</em></p><p><strong><em>Service the Go request</em></strong></p><p>So now we can have an unfulfilled Go request, we need an action where that request is serviced — i.e. the elevator heads to its requested destination.</p><pre>ECNextServiceGoRequest ==<br>    /\ goRequest = 1<br>    /\ carTravelStatus = 0<br>    /\ carTravelStatus&#39; = <strong>IF</strong> carLocation = 1 <strong>THEN</strong> 1 <strong>ELSE</strong> -1<br>    /\ <strong>UNCHANGED</strong> &lt;&lt; goRequest, carLocation, callRequest &gt;&gt;</pre><p><em>That is: given a go request and a non-moving car, in this state the elevator will start moving up or down, depending on the current location.</em></p><p><strong><em>Car arrives after Go request</em></strong></p><p>Similar to the call request, we will specify the action where the car arrives after fulfilling its go request. Note that in this action and the previously described action, we did not specify (s) behind the action name. This is because it does not need to be parameterised for the storey — there’s only one go button, whereas there are <em>n</em> call buttons (where <em>n</em>=2<em> </em>in our simple elevator system).</p><pre>ECNextArriveGoRequest ==<br>    /\ carTravelStatus # 0<br>    /\ goRequest = 1<br>    /\ carLocation&#39; = <strong>IF</strong> carLocation = 1 <strong>THEN</strong> 2 <strong>ELSE</strong> 1<br>    /\ carTravelStatus&#39; = 0<br>    /\ goRequest&#39; = 0<br>    /\ <strong>UNCHANGED</strong> &lt;&lt; callRequest &gt;&gt;</pre><p><em>As the elevator arrives from servicing a go request, the carLocation will flip from either storey 1 to storey 2, or vice versa.</em></p><p><em>The carTravelStatus will change from moving (not 0) to not moving (0).</em></p><p><em>The goRequest will be cancelled once the car arrives; callRequests remain unchanged.</em></p><h4>Putting it all together</h4><p>We’ve so far specified an elevator system that has one car, travelling between two storeys, which can be called by waiting passengers, will move to service such a call, and will cancel the call request once it has arrived.</p><p>If a passenger enters the elevator car and hits the Go button, the car will move to the other storey, and when it arrives, the ‘go’ request will be cancelled.</p><p><strong><em>The full next-state formula</em></strong></p><p>Given all the individual actions described above, our full next-state formula can be defined as follows:</p><pre>ECNext ==<br>    \/ \E s \in Storeys :<br>        \/ ECNextCall(s)<br>        \/ ECNextServiceCall(s)<br>        \/ ECNextArriveCall(s)<br>    \/ ECNextGoRequest<br>    \/ ECNextServiceGoRequest<br>    \/ ECNextArriveGoRequest</pre><pre>vars == &lt;&lt; carLocation, carTravelStatus, callRequest, goRequest &gt;&gt;<br>Spec == ECInit /\ [][ECNext]_vars</pre><p><em>In case you weren’t already aware, the indentation in TLA+ is significant. The above means that our universal next state (ECNext) is a logical disjunction between the three possible actions parameterised by a storey identifier (elevator is called) and three possible actions without a storey identifier (elevator is asked to go by a passenger inside it).</em></p><p><em>The construct \E s \in Storeys : can be read as “there exists a value s in the set of all Storeys where…”. The TLC model checker will interpret this construct by attempting to fulfil the next state using any valid value from the set Storeys.</em></p><p><strong><em>Invariants</em></strong></p><p>We also want to describe in a formula all of the things that should remain true in all states of our system. We’ll start simple, as follows:</p><pre>ECTypeOK ==<br>    /\ carLocation \in Storeys<br>    /\ carTravelStatus \in {-1, 0, 1}<br>    /\ callRequest \in [Storeys -&gt; {0, 1}]<br>    /\ goRequest \in {0, 1}</pre><p><em>The above is pretty uncontroversial. We’re checking that the car is always at a valid floor, that it’s always either stationary, going up or going down, that the callRequests are from the valid combination of call requests for our known floors, and that the Go request is either on or off.</em></p><p><em>These aren’t particularly taxing — we’ll have a go at making those a bit more meaningful later.</em></p><h4>Does it work?</h4><p>We’re ready to give our specification a spin. I won’t share the complete source code, as I think there’s more value in you putting it together yourself and understanding each bit at a time :)</p><p>Here’s how your model might look:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I4ydmOSUfvhEE2eAZ9S1zw.png" /></figure><p>When we run this through the model checker, it works! We get 90 states and 32 distinct states. We have a working elevator!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F101FTJFnTnNi5W%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F101FTJFnTnNi5W%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F101FTJFnTnNi5W%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/f718c082f562273ec566163a65ed8b96/href">https://medium.com/media/f718c082f562273ec566163a65ed8b96/href</a></iframe><h3>What have we learned?</h3><p>This was a pretty simple elevator, and only our first iteration.</p><p>But despite this, I think that just going through the process of identifying the different significant components of our system, and considering how that translates to variables and state changes (actions), helped me to conceptualise my system better.</p><p>We’ve made several important simplifications, such as not modelling doors, and keeping to one car and two storeys. By identifying those simplifications and attempting to codify them in a TLA+ specification, I feel I have a better understanding of the dimensions along which my system is going to get more complex.</p><p>Although I didn’t talk you through every step of my thought process, I found the construction of the next-state formulas (“actions”) to be particularly useful. In my first attempt, I started writing the <em>ECNextGoRequest</em> state formula with a behaviour in mind that as soon as the elevator passenger hit the Go button, it would set off for its destination. However, just by starting to write down the conditions of this action formula, I realised that there was a perfectly valid edge case behaviour I’d missed, and this led to the addition of the <em>ECNextServiceGoRequest</em> action.</p><blockquote>The very act of trying to describe your system in unambiguous terms is itself a very thought-clarifying process. This is why many advocates of TLA+ consider the journey of formal system specification to be just as important as the destination.</blockquote><p>There were other micro-decisions like this that I’ve not documented in this article which helped me conceptualise my system.</p><p>There were also decisions I’m not happy with yet: for example, the formulas for servicing/arriving for calls are very similar in nature to those for Go requests, and I wonder if I should refactor them... but then I am also aware that I’m not trying to write clean code here, I’m trying to model a system’s intended behaviours with as much clarity as possible. So the jury’s out on that one! I’m sure the dilemma will evolve as we add complexity to the system.</p><h3>A couple of gotchas</h3><p>There were a couple of things I noticed were wrong as I was writing my specification. Did you notice them too?</p><p>I’ll let you try to find them. If you spotted them straight away, then well done, you are clearly able to reason about multivariate state machines better than most! But even if you are feeling smug about that, I hope you can also see that spotting anomalous behaviours in a system will only get exponentially harder as we increase the complexity. After all, this is a really, <em>really</em> simple elevator!</p><p>If you didn’t spot them, sorry but I’m not going to reveal them yet. I want to see if the next iteration of our specification helps us to tease out these anomalies.</p><p>The model checker didn’t spot these gotchas because our model is currently very naive. Our invariant check formula only checks for things that really ought to be true unless something went badly wrong (e.g. we somehow managed to send our elevator to floor 3 even though we don’t have one).</p><p>It doesn’t check for more subtle behaviours that might result in our elevator behaving erratically or counterintuitively for the passengers. For these we need more sophisticated checks — and this is where the T in TLA+ comes in. We need temporal checks (i.e. things that we want to be true across an end-to-end behaviour, rather than true simply for all reachable states).</p><p>This will be the subject of the next blog post in this series.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ef288adab39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/koodoo/tla-for-startups-part-2-1ef288adab39">TLA+ for startups (part 2)</a> was originally published in <a href="https://medium.com/koodoo">Koodoo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TLA+ for startups (part 1)]]></title>
            <link>https://medium.com/koodoo/tla-for-startups-part-1-8b162863824b?source=rss-c0d78c579e9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b162863824b</guid>
            <category><![CDATA[specifications]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tla-plus]]></category>
            <dc:creator><![CDATA[Neil O'Connor]]></dc:creator>
            <pubDate>Mon, 25 Nov 2019 16:36:18 GMT</pubDate>
            <atom:updated>2019-12-12T15:02:00.218Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why formal specifications are not a completely insane idea for startups and small teams</h4><p><em>This is the start of my personal and professional journey into the formal specification language TLA+. Before we dive into the details, I should probably begin by explaining my motivation for creating this series of articles.</em></p><h4><strong>Startup life: right thing, right time, done right</strong></h4><p>In my professional life, I build and run software development teams that create business systems using some of the latest technologies and methodologies. The systems we build are complex, but not Apollo programme or nuclear power plant complex. Thousands of lives may not depend on us writing robust, reliable and correct code; but if we write brittle, unreliable and faulty code, the company’s reputation will suffer, our clients’ reputation will suffer, and we will lose money.</p><p>The quality of the systems we build could make the difference between us winning in our chosen business domain and failing, badly. As I work in startups, marginal losses from poorly thought-out business strategies, poor tactical choices, or badly written code can take you very quickly indeed to the end of the road.</p><p>So there is a very real incentive in my world to create software systems that are <strong><em>right</em></strong>. Now there’s a funny word. That could mean a lot of different things to a lot of people. At one end of the spectrum, I could spend millions (somebody else’s millions, that is) creating a software solution that fully solves every significant problem in my company’s chosen business domain… only to find that there is no market appetite for 90% of what we’ve built, and as a result we will never come close to recovering the cost of the build.</p><p>Or I could create a super-lean, MVP solution to a very specific problem, promote it aggressively to gain traction in the market quickly… only to find that the shortcuts we made in getting there quickly come home to roost, while I watch a competitor coolly and calmly launch their product three months later that fixes all the shortcomings in our solution.</p><p>In short, the reason why startup life is a lot harder than it looks is that you generally have one shot at getting it right. And that means you have to <strong>build the right thing</strong>, and you have to <strong>build that thing right</strong>. Oh, and you have to do all that <strong>at exactly the right time</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*f77fO4kegpIMMNwXg9q5dg.png" /></figure><h4><strong>Pragmatism is King</strong></h4><p>Common sense would have it that, to hit the sweetspot in the middle of the Venn diagram above, the startup tech lead has to be supremely pragmatic. If you think you can succeed in the startup world by overburdening your team with detailed processes, design frameworks and formal practices, you will have a very rude awakening. You have to be lean and mean; fast and furious. You have to be the gazelle to the corporate dinosaur; the speedboat to the corporate oil tanker.</p><blockquote>Conventional wisdom would tell you that formal specification languages are wholly unsuited to startup life</blockquote><p>If common sense tells you that you have to be fast, lean and supremely pragmatic, then conventional wisdom would also tell you that formal specification languages are wholly unsuited to startup life. It would probably be safe to assume that, on a continuum of the amount of effort invested in the design stage of software, most people would place formal specification languages way over on the right. Startups should be picking from somewhere near the left, and ought to be leaving formal specification languages to the superbrains designing missile targeting systems for fighter jets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*r-9XtO85rsozhW6jaLhGHw.png" /><figcaption>How we typically think of the amount of design effort, and who it is suited to</figcaption></figure><p>But is that true?</p><h4><strong>Luck be a lady tonight</strong></h4><p>Thinking about the Venn diagram and the continuum diagram together, we have a contradiction. On the one hand, we’ve identified that startups typically have one shot at getting it right (right thing, right time, done right). But on the other hand, conventional wisdom tells us that we need to do it with almost the lowest possible amount of investment in the design stage (also known as the thinking stage).</p><p>In other words, if we are to succeed, we’re going to need to get very, very lucky.</p><p>So what are you, our long-suffering startup tech lead, to do? Should you gradually and gently be moving rightwards on the continuum of pain? Maybe at first asking your team to sketch out their designs on a whiteboard before writing code? Then when that no longer feels fit for purpose, employ a BA to start writing something that at least <em>looks</em> a bit more thought-out? And then maybe 12 months later give one of your best developers an “architect” title and ask them to start drawing proper diagrams? You vaguely remember that formal specification module you did for a semester on your CS degree all those years ago, and you tell yourself that maybe you’ll find a use for it one day… but of course you’re not building software for controlling the coolers in nuclear reactors so… y’know.</p><p>While you are pondering your journey along the continuum of formal design, there’s a pretty decent chance that you have been distracted by some pretty major firefights in v1 of your solution; the lead developer you would’ve given the architect title didn’t turn up to work three weeks ago last Monday and you haven’t seen her since; the client you were counting on winning won’t sign the contract because they kept getting timeouts on your demo environment.</p><p>Perhaps all this could have been avoided if you had done a bit more design upfront, but hindsight is a wonderful thing, and frankly you didn’t have the time.</p><p>Before you know it, your startup dream is lying in tatters.</p><p>As I say, you’re going to need a lot of luck.</p><h4><strong>Thinking is underrated</strong></h4><p>That was a lot of preamble to bring me to the real point of this first article in the series ‘<em>TLA+ for startups’</em>.</p><p>I guess the title gives it away. I would like you to throw out your preconceptions about formal specification languages. Despite what you might think, they’re not just reserved for arcane computer science problems or hyper-critical systems.</p><blockquote>Most importantly of all, TLA+ <strong>helps you THINK</strong> about the problem you are trying to solve</blockquote><p>Although it builds on a rich history of formal specification theory and practice, TLA+ has been designed for solving real-world computing problems. But most importantly of all, TLA+ helps you THINK about the problem you are trying to solve.</p><p>It can be applied to a wide range of computing problems from simple algorithms through to large scale distributed architecture designs. It does not require years of training or a PhD to get started, just a grounding in some relatively straightforward mathematical concepts.</p><p>I believe that TLA+ enables software engineers and systems analysts, for the first time, to <em>practically</em> and <em>formally </em>reason about the code they are going to write before they write it.</p><p>The <em>formally </em>part I will leave to a later article, or indeed point you to some of the links sprinkled throughout this or later articles. Other people far smarter than me can explain why <em>formal</em> reasoning about systems using the universal language of mathematics is an incredibly powerful and useful thing to do.</p><blockquote>The very act of attempting to describe the properties of some code you are planning to write is often enough to spark a new way of thinking about it</blockquote><p>But <em>practically</em>, because despite what you might assume, it is definitely possible to get started with TLA+ quickly and start leveraging value from it right away. The very act of attempting to describe the properties of some code you are planning to write is often enough to spark a new way of thinking about it; to reveal a nuanced insight into the problem that you are trying to address; to tease out a logical flaw in your assumptions.</p><p>I often advise engineers on my teams to either sketch a design or write down in plain English the main tasks that they will need to complete before writing any code. The reason I suggest this is that doing so forces your brain to conceptualise the problem in a subtly different way, and the result will often be quite enlightening.</p><p><em>***In these two similar lectures (</em><a href="https://channel9.msdn.com/Events/Build/2014/3-642"><em>here</em></a><em> and </em><a href="https://www.youtube.com/watch?v=-4Yp3j_jk8Q"><em>here</em></a><em>), Leslie Lamport, inventor of TLA+, explains the importance of thinking above the code, and how TLA+ helps you to do that.***</em></p><h4><strong>Eating the elephant</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/771/1*WFTvyTduroh8RMpVjM3-aw.png" /><figcaption>There’s no need to eat the whole elephant</figcaption></figure><p>You can start by using TLA+ or its alter-ego PlusCal to describe a small part of your system. Perhaps there is a short but non-trivial algorithm or logical flow in your system that you are pretty sure you can just go ahead and code, but you want to just validate your thinking on it before you do. Once you’ve got your head around the basic structures and semantics of TLA+, this would be a perfect candidate to get started on.</p><p>Importantly, you do not need to eat the whole elephant in one go. If your first use case for employing TLA+ in your design process is describing a high throughput, highly parallelised, distributed software architecture, you’re going to get your fingers burned. Or should I say you’re going to choke on a tusk.</p><h4><strong>Recalibrate your thinking</strong></h4><p>I would urge you to recalibrate your thinking about the role that formal specification languages can play in your design process. I would argue that TLA+ makes it possible for you to introduce some formality into your design process much, much earlier than before, and indeed I would recommend introducing it BEFORE considering other structured design practices such as UML.</p><p>I’m not arguing against using these practices — they can be extremely useful. I’m arguing for easing into the habit of formally describing the intended behaviours of your system so early on that it becomes second nature. It is something that you and your engineers and analysts <em>can practically do </em>before you need to consider more heavyweight, structured processes that will inevitably come as your company grows.</p><blockquote>This series of articles attempts to make the case that TLA+ and startups are actually very happy bedfellows</blockquote><p>In short, this series of articles attempts to make the case that TLA+ and startups are actually very happy bedfellows. It gives you a toolset by which you can improve your thinking and reduce your chances of making those critical design mistakes early on, with surprisingly low upfront investment. For the specific challenges that startups face, as discussed at the top of this article, that little bit of extra <em>thinking</em>, done in the right way, could be the difference between glory and ignominy.</p><p><em>*** In </em><a href="https://www.youtube.com/watch?v=_9B__0S21y8"><em>this video</em></a><em>, Hillel Wayne (author of </em><a href="https://www.amazon.co.uk/Practical-TLA-Planning-Driven-Development/dp/1484238281/ref=sr_1_1"><em>Practical TLA+</em></a><em> and the </em><a href="https://learntla.com/"><em>LearnTLA+ website</em></a><em>), does a very good job of demystifying the core concepts of TLA+ and demonstrating how it can be used practically for smaller problem domains.***</em></p><h4><strong>What to expect</strong></h4><p>Now I’ve made the case for tech startups considering adding TLA+ into their armoury, in subsequent articles I will get practical. I’m going to build up an example of a real-world system that everyone can relate to, one that is simple to understand but a little more difficult to reason about. I’ll use TLA+ to help me do so.</p><p>I am definitely not an expert on TLA+, and might never be. Rather than just talking the talk, I am going to attempt to walk the walk of proving that TLA+ can be usefully employed at an early stage of system design thinking, with an <em>appropriate</em> amount of time investment for a small business, and can grow with you as your system matures.</p><p>I may fail in my quest. But hey, I work in startups, so I’m not scared of that as long as I’ve given it my best shot!</p><h4><strong>A few important links</strong></h4><p><a href="http://lamport.azurewebsites.net/video/videos.html">Leslie Lamport’s official video course</a></p><p><a href="https://lamport.azurewebsites.net/tla/hyperbook.html">Leslie Lamport’s TLA+ Hyperbook</a></p><p><a href="https://learntla.com/introduction/">Hillel Wayne’s Learn TLA+ website</a></p><p><a href="https://groups.google.com/forum/?fromgroups#!forum/tlaplus">The TLA+ Google Groups community</a></p><p><a href="https://www.amazon.co.uk/Specifying-Systems-Language-Hardware-Engineers/dp/032114306X/ref=sr_1_2">Leslie Lamport’s seminal work, Specifying Systems</a>, also available in <a href="https://lamport.azurewebsites.net/tla/book-02-08-08.pdf">PDF format here</a></p><p>I’ll introduce more links as we go along, but these are, in my opinion, the building blocks upon which you should begin your TLA+ journey. Also buy Hillel Wayne’s <a href="https://www.amazon.co.uk/Practical-TLA-Planning-Driven-Development/dp/1484238281/ref=sr_1_1">excellent book</a>.</p><p><a href="https://medium.com/koodoo/tla-for-startups-part-2-1ef288adab39"><strong><em>Go to Part 2 &gt;&gt;</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b162863824b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/koodoo/tla-for-startups-part-1-8b162863824b">TLA+ for startups (part 1)</a> was originally published in <a href="https://medium.com/koodoo">Koodoo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CTO Secrets: How to get the best companies fighting to hire you (part 3 of 3)]]></title>
            <link>https://medium.com/koodoo/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-3-of-3-29ed4a464115?source=rss-c0d78c579e9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/29ed4a464115</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[tech-test]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <category><![CDATA[tech-career]]></category>
            <category><![CDATA[dddem]]></category>
            <dc:creator><![CDATA[Neil O'Connor]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 16:10:47 GMT</pubDate>
            <atom:updated>2019-11-25T11:40:12.772Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I recently gave a talk at the inaugural </em><a href="http://dddeastmidlands.com/"><em>DDD East Midlands</em></a><em> conference in Nottingham, UK. Here is a transcript of that talk, in three parts. </em><strong><em>UPDATE: the video of the original talk is now available </em></strong><a href="https://www.youtube.com/watch?v=FHhgTXiv-Rw"><strong><em>here</em></strong></a><strong><em>.</em></strong></p><p><a href="https://medium.com/@neil.oconnor/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-1-of-3-808819940f6e"><strong>&lt;&lt; Back to part 1</strong></a></p><p><a href="https://medium.com/@neil.oconnor/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-2-of-3-424965f4ed86"><strong>&lt;&lt; Back to part 2</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U4A2uOr9LY8tMyTRh7HXbw.png" /></figure><h3>PART 3: Getting the job</h3><h4>Before the interview</h4><p>So you’ve started hitting some of those sweet career goals, you’re making a name for yourself in the tech community as a bit of a badass, you’ve crafted a killer CV, and you’ve got yourself that plum interview. Now what?</p><p>OK, so first of all <strong>do a bit of research about the interview</strong>. Find out what the interview structure is and in particular whether there will be a technical assessment and what sort of assessment. More on that shortly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p8K46X_ILrfyX8DV12pVAA.png" /></figure><p>Do at least some basic research on the company. You don’t need to be able to reel off facts about profits and what their first office dog was called. But at least be able to describe in a sentence or two what they do and why you find that super interesting.</p><p>Find out who is interviewing you. Look them up and try to assess how technical they are from their online presence or previous jobs. <strong>Do not attempt to connect with them on </strong><a href="http://linkedin.com/"><strong>LinkedIn</strong></a><strong>.</strong></p><p>Have a look at <a href="http://glassdoor.com/">Glassdoor</a>. It might give you some clues about the culture, but also there are sometimes reports about what the interview experience was like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZajDADvwMS7fWFngb3530w.png" /></figure><p><strong>Prepare some answers to behavioural questions</strong>. These are the sorts of things where you are asked how you have handled yourself in certain situations. They’re straight out of the corporate interview playbook, and you can train yourself to answer them better. Find a list online somewhere, write down bullet points against each, and just memorise as many of the bullet points as you can. Get a friend to randomly ask you similar questions until you’re confident you’re remembering enough of the bullet points.</p><p>But the main thing to remember about these behavioural questions is not that there is a right and wrong answer. Instead, view them as an opportunity to sell some of your achievements or knowledge. If you’re asked some random question like “how do you deal with conflict”, don’t answer that in the abstract, “err I try not to raise my voice” or “I’m a black belt in krav maga”.</p><p>Instead, use it as an opportunity to say something like, “I was working in a team where we had a disagreement about using SQL Server or Mongo. I could see the pros and cons of each, but one guy was arguing loudly for Mongo, so I spent half an hour writing the pitch for SQL, and we presented our boss with both options”…. or something along those lines.</p><p>And here’s the thing: it doesn’t even matter if you’ve used a bit of poetic licence. <strong>That exact scenario may never have happened in the way you describe it</strong>. As an interviewer, I don’t care. I’ve asked a question, you’ve engaged with it, you’ve managed to bring a technical angle into it, we may get to talk about that technical subject later, and I’ve learned that you understand the importance of not bringing a knife to a fist fight. Everyone is happy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CqwHFuZYP4wLkecuu-bHag.png" /></figure><p>Some other prep you should do. Read your own CV carefully before you go in. Partly to remind yourself how awesome you are, and partly to remind yourself what you’ve said. I’ve lost count of the times I’ve asked someone in an interview about something they’ve claimed to be an expert in on their CV, only for them to tell me that they’ve not really used it. Those interviews didn’t last very long.</p><p>OK, listen carefully to the next three pieces of advice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*miTKZ_OAcNCsivmmwV-BZA.png" /></figure><p>In preparation for the interview, <strong>write down the key projects</strong> that you have worked on in the last couple of years. Then write down what your contribution was that made it a success, and write down what you learned from that project.</p><p>You may think it’s pointless writing this down because it’s all in your head and you won’t forget. Well in fact, the act of writing something down accesses a different part of your brain and forces you to structure your thoughts. You are then more likely to remember it when asked about it — rather than looking like a fool, you’ll be able to crisply and eloquently describe these previous projects and what you gave to them and took from them.</p><p>Which leads me to the next thing: <strong>can you draw the architecture of the last project you worked on in 60 seconds?</strong> You would not believe the number of times I have asked someone to draw a simple visualisation — ANYTHING — of a system they were supposedly a key contributor to, and they can’t do it. With a whiteboard marker in their hand and an empty whiteboard in front of them, no matter how comfortable I try to make them feel, they turn into a blithering idiot. It might be stage fright, but what comes across is that they have never attempted to explain their work to another human being.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0oWydZrle_IWT_ZaWHCMCA.png" /></figure><p>You might think you know in your head how your system is put together, but you will be proved wrong the first time you attempt to actually draw it in boxes and arrowed lines. So think about which project you are going to talk about the most in your interview, and practice drawing a diagram that represents it the best. And practice it again.</p><p>It might be a physical architecture diagram, or a logical system diagram, or a data flow diagram, or a sequence diagram, or a use case diagram. That’ll depend on your job and what points you want to get across. But it needs to be obvious to the interviewer that it comes very naturally to you to be able to visualise and explain a system you have worked on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6zVzVtLkM7YZ-ayywfl2Fw.png" /></figure><p>The third thing: you will often be asked <strong>what you would do differently if you had the chance for a do-over</strong> on a particular project. Think about this one in advance. Knowing what you know now, would you choose different tech or make different architectural choices? Would you put a greater emphasis on some non-functional aspect such as monitoring or performance testing? Why didn’t that happen first time around? Was it an oversight or were someone’s arguments to management not sharp enough?</p><p>I’m telling you to think about this not just so you can prepare a well-rehearsed answer. After all, you may not even get asked the question. But even just by asking yourself this question, you are training yourself to think about how you can learn from your mistakes or experiences. It may trigger a thought process about best practices and how to win the argument for adopting them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6i19aYD2X86iKjFl-BDhWQ.png" /></figure><p>So those last few things I mentioned are about demonstrating that you can see the bigger picture. You can move comfortably between the concrete and abstract details, and you can demonstrate ownership and personal accountability through being able to describe, visualise and reflect upon the projects you have contributed to. These all help me as an interviewer to feel confident in your ability to be net positive contributor if you join the team.</p><h4>During the interview</h4><p>OK, those were my tips for interview prep. Now a few words about the interview itself. I won’t dwell on this because there’s reams of stuff written on this topic, but here are a few quick pointers on what I value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tULj9MVBT9fXRduEey-opQ.png" /></figure><p><strong>Turn up on time. </strong>I had an interviewee arrive 10 minutes late and offer no apology or explanation. I asked him, “did you have trouble finding us?”, “oh no, it was easy”. “OK, did you have a long way to come?, “no, I just live round the corner!”. Bad impression from the off.</p><p><strong>Be polite and professional. </strong>Even if you know they have a very casual dress code, that’s not a reason to turn up in your favourite 20 year-old Napalm Death t-shirt. Little things like this matter. I once interviewed a guy who had a bag with him, and he left it open on the floor between us. I could see one condom sitting proudly at the top of his bag. Just one. Ribbed. I still wonder exactly how he thought that interview was going to pan out.</p><p><strong>Ask about the tech culture.</strong> They should be selling this to you, but if not you should ask. Ask what they do to encourage and support the team keeping on top of the latest practices and technologies, and what they do to share knowledge in the team.</p><p><strong>Don’t ask questions that sound like you’re a jobsworth.</strong> If you’re asking in the interview whether you can finish at 4pm every day, you may already be talking yourself out of it. If you have a specific requirement such as childcare commitments, it’s much better to bring this up once you have an offer but before you start, because they’ll be more psychologically committed to you as a candidate by then.</p><p><strong>Remember that they want you to succeed. </strong>In most cases, they will be willing you to do well and hoping you are the right person for the job. They’ve already taken time out of their day to speak to you and have already rejected a bunch of other CVs. They’ve seen something in you they like. Take a positive mindset into the interview.</p><p><strong>Unfortunately, there are bad interviewers. </strong>I said at the top of this talk that we all make snap judgments, and sadly that can work against you or for you. Some other bad types of interviewers are:</p><ul><li>The one that’s trying to catch you out or make you feel small. Usually this is because they have are having marital problems</li><li>The one that persists with a specific question because there’s a particular thing they seem to want to hear</li><li>The one who talks about themselves the whole time</li><li>The one who is super friendly but doesn’t ask you any probing questions you can use to bring out your best</li></ul><p>The best you can do in these cases is be polite and patient, but look for opportunities, little openings, to turn the conversation in a direction you want to take it. Have those bullet points about yourself and your projects that I talked about at the ready. It may or may not work, but this is where the prep pays off in an unexpected way.</p><p><strong>Speaking of bad interviewers, </strong>you do unfortunately still get otherwise sane people asking you in interviews what your spirit animal is, or what kitchen utensil you’d like to be reincarnated as, or asking you to estimate how many grains of sand there are in the Sahara. One guy on my team had to talk for 5 minutes about a rock that was placed on the desk in front of him.</p><p>I have to admit to having tried all these things in the past. They might tell me something about your reasoning skills or your sense of humour, but I’ve concluded they are usually pretty pointless. But play them with a straight bat and answer them as best you can, because if you laugh in their face you will probably insult them, because they obviously think it’s a really clever question.</p><h4>Ace the interview</h4><p>Right, so I’ll repeat a few points here, but for me these things are key to delivering a great interview, rather than a decidedly OK interview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3bisZWBSdMlbpqbDMaSIPw.png" /></figure><p><strong>I keep talking about having a point of view. </strong>Don’t be afraid to let that come out. Take the initiative in the interview and set out a narrative, a theme or common thread around which you can build your answers. You might want to make the case, for example, for automating as much as you can in the development pipeline. Lay that out as something you are passionate about early on, and keep referring back to that in your answers to subsequent questions.<strong> </strong>It is great to hear when someone has an opinion on the state of tech or the industry, and can speak passionately and informatively about it.</p><p><strong>Listen to and answer the questions put to you. </strong>In doing so, try to work out why they were asking that. What were they really trying to get out of you by asking that question?</p><p>But then <strong>use their questions as springboards </strong>to get across the points you want to make that help you sell your skills and experience. Think of it like the tennis player who uses the power of the opponent’s serve to generate a cracking return, and then adds a bit of spin on top as well.</p><p><strong>Expect the unexpected. </strong>That’s an awful cliché, but here’s what I mean. Let’s say they ask you about something on your CV that you weren’t expecting to be asked about, whether it’s a particular framework you’d forgotten about or something more leftfield. The natural response is to go on the defensive.</p><p>But again, think of these as an opportunity. Even if you give a mediocre answer, you’ve still got a free hit for you to bring up some of the attributes or skills that YOU want to talk about.</p><p>This is where it really helps if you have practised those bullet points about what you’re good at and what you’ve achieved. Because you’ll often find opportunities suddenly arising at the most unexpected time to get across some point you wanted to make, and you’ll have those little phrases and examples at the tip of your tongue just when you need them.</p><p><strong>Try to balance confidence with humility.</strong> It’s a very British thing. We like people who are capable and intelligent, but we don’t like them to show off about it. A bit of self-deprecating humour can go a long way, used judiciously. You want to get across the message that “I’ve got this. But I don’t take myself too seriously, so other people will go along with me”.</p><p>If you’re going for a <strong>senior role</strong>, I read a <a href="https://medium.com/swlh/you-need-better-senior-software-developers-4c762950fe1">great article</a> about what companies are looking for, whether they realise it or not, when they say they want a senior.</p><p><strong>Firstly</strong>, they want someone who is a skilled mentor. It’s not just about bringing mad skills; you need to be excited about and able to transfer those skills to more junior team members.</p><p><strong>Secondly,</strong> they want someone who is an accelerator. Are you someone who makes things go faster, because you’re always looking at ways to optimise and improve? Or are you going to keep things as they are, or worse slow things down? Every manager in the world thinks the dev team aren’t delivering fast enough. So they want an accelerator.</p><p><strong>Thirdly</strong>, they want someone with perspective. This often means experience, but you can gain perspective with every new thing you learn. There are always at least two sides to every story, and being able to balance off competing priorities using experience and insight is a valued skill.</p><p><strong>Be comfortable visualising technical concepts you are talking about.</strong> Don’t be afraid to ask if you can jump up and draw it on a whiteboard. If you ask them, rather than wait to be asked, if you can draw it, you will give them a warm fuzzy feeling that you have a good handle on the big picture and are a natural explainer.</p><p>Interviewers for dev positions will listen carefully to your answers about<strong> technical debt and non-functional requirements. </strong>It’s a sore subject in most teams, and usually a source of tension between product and tech. The trick is not to come down hard on one side of the argument or guess what side you think they are likely to be on, but to demonstrate (ideally with examples) that you realise it’s a balancing act. It shows maturity and good judgment.</p><h4>Nail the tech test</h4><p>The tech test is where the chickens on your CV can come home to roost.</p><p>There are various flavours of technical test, and I’ve tried them all at various stages. Right now, I do a combination of a simple whiteboard test in the first interview stage to check you have got the rudimentary thinking skills, and a more in-depth coding exercise with the team if you get through to the second stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iu_v6AGx9_0RFg63MaSY7A.png" /></figure><p>I’ll go through the main types of tech test you might encounter:</p><p><strong>Standard screening</strong> test before you get an interview. I think these are generally a bad idea — it’s like they’re <em>trying</em> to put you off the company. I can’t give you any specific advice on how to approach these ones, other than that you can get better at them with practice.</p><p><strong>At-home tests</strong> after you’ve already had a positive first interview. I’ve used these before, and they can be pretty useful. What I’m generally looking for here is that you a) understood the thing I’m asking you to do, and that means it’s OK for you to come back and ask questions about the challenge; b) can write solid and elegant code; and c) understand the importance of good housekeeping.</p><p>So take a bit of care with your solution, don’t rush through it. And for that last point, be sure to comment your code appropriately, even if you aren’t a big believer in doing that; write unit tests that pass; and commit to whatever repo you are using as though you were working on a team project. Clear some time in your weekend to work on it, because if you tell me you were busy and did a quick hack, I’ll assume you’re not that bothered about the job.</p><p><strong>Locked away like a hostage in a meeting room </strong>for an hour with a challenge and a laptop. For these, before you start, ask the interviewer what success looks like; what are they are most interested in seeing from you? Are they more interested in having something working, something complete, or something well-written?</p><ul><li>Realistically, they might tell you to use your own judgment, but even asking them sends a good signal. If they do say that, tell them you’ll focus initially on having something working.</li><li>In which case, you need to be disciplined about continuously compiling and running, so spend a few minutes at the beginning making sure you are set up for that.</li><li>If they want something complete, it’s pretty much a test of your ability to hit a deadline. In this case, take a few minutes at the start to plan out your hour, and give yourself milestones to hit.</li><li>If they want something well-written, take a few moments to consider what you want to showcase. Look for clues that suggest what they want to see — maybe it’s a particular code structure or implementation pattern. If you just dive in without considering what an elegant solution might look like, you will probably just write bad code.</li></ul><p>Whatever your approach, explain at the end what approach you took and any assumptions or shortcuts you made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QaQxY7o_JLyxcfrvFYprYA.png" /></figure><p><strong>Coding in front of a technical interviewer</strong>. For this one, you want to appeal to their instincts as a peer. They will, or at least should, appreciate you doing things like writing unit tests, perhaps even following a TDD style, observing concepts such as single responsibility principle and patterns such as dependency inversion.</p><p>They will probably also admire your pragmatism if you say, “Oooh I bet there’s an NPM package for this, can I have a look?”. In any case, the most important thing is to talk them through what you are thinking. Explain your reasoning, and if they guide you down a different path, be sure to listen.</p><p><strong>Whiteboard coding</strong>. Don’t be deceived into thinking that you’ve dodged a bullet by not having to write working code. A good interviewer in a software company will actually ask you to solve a particularly thorny question in this format because it means you can focus on logic and reason and fundamental computer science concepts, without getting bogged down in the syntax of a particular language.</p><ul><li>Remember that — don’t get bogged down into writing working code. It’s a whiteboard, not an IDE. Write it in pseudo-code, or if you are more comfortable, write it in your favourite language but tell them you aren’t going to get hung up on semicolons</li><li>If they ask, “are you happy with your solution?”, that’s often code for them saying they think there is a mistake. If you can’t see it, I’d be impressed if you started writing some pseudo tests for your pseudo code. Because this simultaneously shows you understand the importance of validating your code AND it may actually help you tease out the logical flaw if there is one.</li><li>Also, don’t be afraid of just scrubbing it and starting again — it’s a whiteboard, that’s what they’re designed for. If you are really stuck in a rut, think about it as a TDD problem. Tell them you’re going to break it down into the smallest unit of a problem, write the simplest case that will pass, and then build on it. If you are still stuck, ask them for a clue.</li></ul><p>As you go through your tech test, remember we’re looking for people who, in the words of <a href="https://www.joelonsoftware.com/">Joel Spolsky</a>, are <strong>smart and get things done</strong>. Focus on what the problem is they are asking you to solve, listen to what they are trying to guide you towards, explain your thinking, and prioritise getting to a working solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0a0Lvz5KgW3MwvBbipXLIQ.png" /></figure><p>Thanks for listening, and I hope you found some of that useful. And of course I would be stupid not to use this opportunity to tell you: <strong>I’m hiring</strong>!</p><p><em>(Opinions are those of the author, not the company. All images used are copyright of the original publishers, who are too numerous to track down given the sheer volume of memes in this talk!)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29ed4a464115" width="1" height="1" alt=""><hr><p><a href="https://medium.com/koodoo/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-3-of-3-29ed4a464115">CTO Secrets: How to get the best companies fighting to hire you (part 3 of 3)</a> was originally published in <a href="https://medium.com/koodoo">Koodoo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CTO Secrets: How to get the best companies fighting to hire you (part 2 of 3)]]></title>
            <link>https://medium.com/koodoo/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-2-of-3-424965f4ed86?source=rss-c0d78c579e9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/424965f4ed86</guid>
            <category><![CDATA[tech-career]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <category><![CDATA[dddem]]></category>
            <category><![CDATA[resume]]></category>
            <category><![CDATA[cv]]></category>
            <dc:creator><![CDATA[Neil O'Connor]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 16:10:22 GMT</pubDate>
            <atom:updated>2019-11-25T11:39:47.602Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I recently gave a talk at the inaugural </em><a href="http://dddeastmidlands.com/"><em>DDD East Midlands</em></a><em> conference in Nottingham, UK. Here is a transcript of that talk, in three parts. </em><strong><em>UPDATE: the video of the original talk is now available </em></strong><a href="https://www.youtube.com/watch?v=FHhgTXiv-Rw"><strong><em>here</em></strong></a><strong><em>.</em></strong></p><p><a href="https://medium.com/@neil.oconnor/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-1-of-3-808819940f6e"><strong>&lt;&lt; Back to part 1</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C_GsT1AwOD7FsRYUwOccIA.png" /></figure><h3>PART 2: Getting the interview</h3><p>OK, so I just gave you some of my opinions on what you should be prioritising as career goals as a professional software engineer. Why did I spend 15 minutes talking about that? Because these are the sorts of things that I really value as a hiring manager. I want to see that you take your craft seriously. That you <strong>care</strong> about your own professional development and you care about giving something back to your colleagues and the industry. That you <strong>care</strong> about creating the best solution you can.</p><p>But that all doesn’t count for much if you don’t get invited to interviews. So I’ll now talk about securing that interview you really want to get.</p><p>It’s an uncomfortable truth that people reading CVs will make snap judgments. If I’ve got 5 CVs on my desk, my eye will be drawn to the one that’s got something a bit different about it. So we’ll talk about CVs shortly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v6uGQZ2r9TVvscEmu9NKIQ.png" /></figure><p>So you know how the most attractive and well-heeled people are rarely single, and if they are, they don’t tend to spend their time on Tinder? This same rule sort of applies to hiring. Surprise surprise, the best people tend to always be in a job — they get snapped up by their placement company straight from uni, then they get poached by a client company, then they go and found a startup with their mates, and so on.</p><p>And guess what, <strong>the best companies know this</strong>, and hire with this in mind. They don’t need the hassle of advertising jobs and sifting through thousands of CVs, not least because they know that the best people are already in jobs. So they use agencies to headhunt; they rely on staff referrals; they hang out at hackathons and conferences like this; they go to university fairs and snag the brightest sparks before the undergrads properly realise there’s such a thing as a job market.</p><p>So firstly, you need to know that <strong>recruitment agencies are not your mortal enemy.</strong> I’ve heard some pretty stupid opinions in the past from people refusing to talk to agencies, and convinced they are all charlatans and money-grabbing scoundrels. Some are, most are not, they are just people like you and me who are trying to earn a living. But even if they are rotten scoundrels who only see you as a pound sign, then that’s even more of a reason to work with them, not against them.</p><p>So play nice with agencies. They sometimes have exclusive hiring arrangements with companies you want to work for, and if one of the agencies I work with sends me a CV, I will always look at it because I know they’ve screened the candidate and their reputation with me depends on them sending me relevant and quality people. Often their clients will be anonymous in the advert, because they don’t want floods of direct applicants, and these companies are often the good ones.</p><p>And don’t sneer when recruitment agencies sponsor or turn up to events like this. If anything, make a note of who they are, and maybe go and have a pint with them later, because they’re the ones who are smart enough to realise that the savvier techies will be at events like this. They are like the smart lion who hunts at the antelope watering hole. As a hiring manager, seeing that a recruitment agency has sponsored an event like this makes it <strong>more likely</strong> that I will want to work with them instead of another agency, because they are being proactive and are immersing themselves in the local community.</p><p>Be polite and friendly with agencies. Don’t mess them about and don’t mess about their clients. If you aren’t interested in the current job they are calling you about, don’t tell them to eff off, because next month they might have a job that you really do want.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2KOx2iFF_lHYfp1QpB_pQ.png" /></figure><p>When you speak to an agency on a screening phone call, treat it like a first interview stage. You want to get the best version of yourself across, because they will then call <strong>me</strong> and say, “Neil, I’ve got an awesome candidate for you!”. I’ll sit up and take notice when I get that call.</p><p>Remember what I was saying about developing a point of view. Talk to the recruitment agent about it. Talk to them about your side hustles and your community involvement. These are things that will make you memorable to them when they talk to me.</p><p>Also, I mentioned that the smartest tech companies recognise the power of a) staff referrals, and b) hiring from the tech scene. So think about what that means from the perspective of getting hired by one of these cool companies. It means that if you hang out on the tech scene and get involved, they’ll notice you. It means you’ll start to get to know other people on the tech scene, and it’ll turn out that some of them work for the cool companies, and eventually they might recommend you to their boss once they’re confident you’re not going to make them look stupid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sd5oOb_jKse4ruj_KoYaog.png" /></figure><p>So, your CV. <strong>What makes an attractive CV? </strong>Often, less is more. If you’ve been in the industry for 2 years and you’ve got a 3 page CV, I promise you it’s too big. It’s a bit of a cliche now, but have you seen the sample Marissa Meyer CV that went round a couple of years ago? It was actually being used to promote a CV writing service, but it captured people’s imagination. This is one of the most experienced and successful people in our industry, and they’ve captured everything you need to know about her on one page, with plenty of white space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mLva20D_9klLPooYTjFSMg.png" /></figure><p>If you think that’s nonsense, let me tell you I’ve helped a lot of people with their CVs, and every one where I’ve cut it down with them to 1 page, they’ve had amazing feedback on their CV.</p><p>Also, here is one of those nonsense rules that you’ll hear: “don’t put your photo on your CV”. I cannot think of any good reason why you shouldn’t — humans like to put a face to a name, and as long as it’s not a picture of you throwing up in a bar in Magaluf or something, it will only enhance your ability to connect with the hiring manager on a personal level before you get there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fmKjxpaTv9MDAx5w_3McSA.png" /></figure><p><strong>Here’s something important to remember.</strong> You will not get hired on the strength of your CV. But you could get eliminated at the first hurdle because of a weak CV. A hiring manager uses CVs as a screening mechanism to whittle down the candidates to a manageable shortlist of people to interview. A great CV will simply go to the top of the pile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*622TuVhjv5pS4RCunyR_4Q.png" /></figure><p><strong>Don’t just list out the languages and tools you’ve used.</strong> It’s meaningless — it’s become a standard joke that candidates pretty much list everything they’ve heard of. I want to know what you used them for and your skill level with each — maybe give yourself a rating on each.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jaq2bEVrLugUX_Qi9UZvfw.png" /></figure><p>In your job history, I want to know what your contribution was. Even if you were the most junior person in the organisation, I want to know what you did that helped make it a better place, or how what you did there made you a better engineer or a better person.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6VyBpPZ6UNegg1vVegCDuA.png" /></figure><p>Consider making a portfolio CV that showcases your skills. This is common for artists and so on, but it’s not just creative types that can benefit from a portfolio CV. I’ll tell you about a couple of the best CVs I’ve seen.</p><p>Firstly, one of my current senior developers, Zac, who you may have heard speak brilliantly earlier today. Really obvious thing for anyone in our industry to do: he made a CV website, and his is a really nice example. You can see it at <a href="http://zackerthehacker.com/">ZackerTheHacker.com</a>. But here’s the thing: I know he’s got mad React skills, but he made it clear to me that he used a template and didn’t build it from ground up in React. But that’s fine: he’s shown that he can channel his developer instincts into something that he recognises is important, namely creating a really nice “shop window” that shows me why I should hire him.</p><p>Secondly, a guy I employed as a BI engineer sent me a CV that used various data visualisation techniques, such as those radar charts, to highlight which skills he had employed in each of his previous roles. It was a really smart way of showing me something that was both very relevant to my reading of his CV while showcasing that he could use a skill very relevant to the job, namely data viz.</p><p>There’s nothing stopping you doing the same. Let’s say you are pretty pleased with your API writing skills. OK, so why don’t you make a HATEOAS compliant RESTful API that I can interrogate to explore your CV? It would only take a few hours to write, and I’ve <strong>literally</strong> never seen anyone do that; but if a potential candidate gave me that as an alternative way (not the only way, please!) of exploring their CV, I’d be impressed.</p><p>Remember that your CV is your shop window. Spend some time on it, and use it to showcase your skills. Be imaginative. Bring out your personality. I saw a CV of someone applying to a junior social media marketing role, so they laid their CV out like a twitter conversation. Simple but effective.</p><p>Too many people think of CV writing as a template-driven exercise, where they have to list out certain pieces of information and not do anything too funky. Firstly, to go back to my dating analogy, does that work when you are trying to hook up with someone? Do you make yourself attractive to someone by listing out your attributes?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQhAAj4IkLRsFy0otm8hqQ.png" /></figure><p>Secondly, a killer career move could literally be worth thousands of pounds in your pocket. You would be stupid not to spend a good amount of time getting it right. Maybe even pay for a CV writing or reviewing service if you aren’t confident in your own judgment. It might cost you 50 or 100 quid — the price of a good night out — but if it is the difference between getting your dream job and not, it’s a small price to pay.</p><p>I mentioned Zac’s CV earlier. The opening sentence of that said he was “super jazzed by front end frameworks”. When I saw that it made me laugh out loud and I was telling people about it for days. He is an Aussie so he can get away with such ridiculous phrasing, but I didn’t know that when I read his CV. He also said in his CV that he is a mutant code monkey sent from the future, and I still employed him. It was memorable, and I got his personality from it. Turns out he is indeed a mutant code monkey.</p><p>Once you’ve started following through on some of the career goals I talked about earlier, make sure that all comes across on your CV. Include a link to your github and tell me what your stackoverflow reputation score is. Tell me about what talks you’ve given, even if they’re just to your team. Definitely tell me about your side hustles and any open source projects you’ve contributed to. Even if you’ve only had one PR merged on an open source project, it’s one more than most people.</p><h3>How I read a CV</h3><p>OK, so just to reiterate some of that, but from my side of the desk. <strong>How do I read a CV?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tq-jXCQ27JOhBWpqni5eEg.png" /></figure><p><strong>Firstly, what is the overriding impression </strong>that the CV as a whole conveys? Is it succinct and waffle free? If it’s 2 pages or less I’m likely to read it all; more than that I’m going to start skimming for keywords.</p><p>Is it well laid out, with at least some white space and maybe a splash of colour and the occasional use of bold to draw my eye to something important?</p><p>Are there any <strong>spelling mistakes</strong> in there? Spelling mistakes are bad in general, but if you misspell a framework that you’re supposedly an expert in, I promise you I am going to make assumptions about your true expertise in that. If you are rubbish at spelling, get someone who isn’t to check it for you.</p><p>Also make sure it’s a <strong>neat and clean layout</strong>, because subconsciously someone reading a messy CV with spelling mistakes in it will assume that you are lacking in self-discipline and basic organisation skills.</p><p><strong>For your education</strong>, I’m interested in what university you went to and what degree you did. If you graduated recently, I’d be interested in a short statement about what you enjoyed the most about your course.</p><p>If you didn’t do a degree, or you did a degree in a non-computing subject, I’m going to look for what you have done instead that has helped to get some of the formal skills that come with a computing degree. Not everyone asks for a computing degree or equivalent, but I do, because of the professionalisation stuff I talked about earlier, but I do make exceptions if someone has really gone out of their way to develop those skills in a less formal learning environment.</p><p><strong>For your job history</strong>, I’m most interested in your current or last job. How long have you been there, what is your personal contribution. If you’ve been there for less than 3 months and are already looking for a new job, explain why on your CV and make it convincing, otherwise I’m going to assume that you’re about to fail probation.</p><p>I’m interested to know how you have <em>improved</em> things in your team. What are the achievements that you are most proud of. I’d rather read one line saying “As a junior developer, I ran a POC of a new CI tool and the whole team loved it” rather than three paragraphs of filler.</p><p>I’ll attach progressively less importance to your <strong>previous jobs</strong>, but I’m interested in how long you stayed in each one and whether they show you’ve got a bit of staying power and have learned something from each and left for the right reasons.</p><p>I don’t really care either way if you’ve demonstrated leadership skills in a summer job flipping burgers. However, if you tell me you were coding before you could talk, or that you’ve automated your toaster using a Raspberry Pi, I’d like to hear it.</p><p>Basically I will look for signs from your CV that you are <strong>motivated by the right things and care about doing things right</strong>, care about your craft, rather than just chasing the dollar or a senior title.</p><p>I also love a good <strong>personal statement</strong>. Tell me your interests and hobbies, tell me what gets you excited about tech or the projects you’ve worked on. Remember I said you should develop a point of view? Tell me what it is. I want to get a sense of your personality. I want to see PASSION for computers and coding.</p><p>I am also definitely going to look for your <strong>side projects</strong>. If there’s not a link to a personal website or github or blog on there, I’m going to be disappointed. If there is one of those and there’s been a couple of posts or commits in 2017 and nothing since, I’m also going to be disappointed. I’ve had CVs from people who claim to be web developers, and their websites look like the sort of thing that the guy who runs our village hall website would be ashamed of.</p><p>Finally, should you write a <strong>cover letter</strong>? Yes, when not. Especially if it shows you have taken the time to research my company and you explain why you think you’d be a good fit. It shows you believe in your skills enough to be selective about who you are applying to. If you’re applying through an agency, you can still write a cover letter, as they’ll include it on the cover sheet they send through with each CV.</p><p><a href="https://medium.com/@neil.oconnor/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-3-of-3-29ed4a464115"><strong>Continue to part 3 &gt;&gt;</strong></a></p><p><em>(Opinions are those of the author, not the company. All images used are copyright of the original publishers, who are too numerous to track down given the sheer volume of memes in this talk!)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=424965f4ed86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/koodoo/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-2-of-3-424965f4ed86">CTO Secrets: How to get the best companies fighting to hire you (part 2 of 3)</a> was originally published in <a href="https://medium.com/koodoo">Koodoo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CTO Secrets: How to get the best companies fighting to hire you (part 1 of 3)]]></title>
            <link>https://medium.com/koodoo/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-1-of-3-808819940f6e?source=rss-c0d78c579e9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/808819940f6e</guid>
            <category><![CDATA[tech-career]]></category>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[dddem]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <dc:creator><![CDATA[Neil O'Connor]]></dc:creator>
            <pubDate>Mon, 04 Nov 2019 16:10:07 GMT</pubDate>
            <atom:updated>2019-11-25T11:39:19.102Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I recently gave a talk at the inaugural </em><a href="http://dddeastmidlands.com/"><em>DDD East Midlands</em></a><em> conference in Nottingham, UK. Here is a transcript of that talk, in three parts. </em><strong><em>UPDATE: the video of the original talk is now available </em></strong><a href="https://www.youtube.com/watch?v=FHhgTXiv-Rw"><strong><em>here</em></strong></a><strong><em>.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UinIlSW435MlOiWft8B73A.png" /></figure><h3>What’s this talk about?</h3><p>Thanks for coming. I did consider going with a full-on clickbait title for this talk and calling it something like “28 incredible career hacks for geeks (and you won’t believe number 7!)”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lKdP62f0-965HdLkPOkTJQ.png" /></figure><p>But basically I am going to give you my advice, for what it’s worth, on how to make yourself as attractive as possible to hiring managers in the sorts of companies you really want to work for.</p><p>Sadly, I’m not a magician. I’m not here to help you get a job that you’re not qualified for. There are, of course, other ways of achieving that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q0eHgMtWxAgk24DVLmjvoA.png" /></figure><p>I WILL talk about plenty of quick fixes you can make to improve your CV or your interview style, or those little hacks to help you get noticed, but other things I’m going to talk about might require you to think differently about what you prioritise in your career and to adopt a different mindset.</p><p>So what qualifies me to talk to you about this? Well, because I’m one of those hiring managers. I’m CTO of a fast-growing fintech startup called <a href="http://koodoo.io/">Koodoo</a>, which is one of the <a href="http://blenheimchalcot.com/">Blenheim Chalcot</a> ventures. I was CTO of <a href="http://oakbrookfinance.com/">Oakbrook Finance</a> for 5 years, who have been hiring a lot of tech talent locally over the last few years, and I’ve had previous hiring roles in large respected software teams.</p><p>I insist on interviewing everyone myself for the first interview, and as a result I have interviewed hundreds of software professionals in the last 10 years, and seen 1000s of CVs, and I like to think I’ve got a pretty good track record in the ones I’ve hired. I’m sure a few people in this room have had the pleasure or displeasure of being locked in a room with me for an hour.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iSlkaIOIo9kHfZgCbrzI_g.png" /></figure><p>My talk title mentions making yourself attractive to the “best companies”. What do I mean by best? I don’t necessarily mean the ones that pay the most or have the most recognisable name. Those guys can be soulless or cutthroat places where they talk a good game about their tech investment, but in reality you are little more than a cog in a corporate machine.</p><p>I’m talking about the gems — the places that value what you do as a software professional, give you the opportunity to learn and grow, and have happy, engaged teams making great software. Believe me when I tell you that these places are where you want to be building your career.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IYwT7F2orUNBOmlhyYnDyw.png" /></figure><p>The first clue is that the best places will often call themselves software companies. They are the places that value great software and great software engineers. I’m not saying there’s anything wrong with writing software for a global manufacturing company or a bank or a funeral director or… whatever… I’m sure many of them are pleasant places to work. But if you are hungry to create awesome code in an environment where your colleagues and your boss and your boss’s boss TRULY understand what it means to build awesome software… then you should probably be aspiring to work for an innovative software or tech company.</p><p>The other part of my talk title is about getting those awesome companies fighting to hire you. Industry legend Joel Spolsky says that really he is looking for people with just two qualities: <strong>Smart &amp; Gets Things Done</strong>. This talk is about how to become that perfect candidate who hits those two sweet spots.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cmS_pal9MpV13s3WXKGQ8g.png" /></figure><p>I’m going to talk to you about career goals, getting an interview, and nailing an interview and tech test.</p><h3>PART 1: Career Goals</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*talxPm3gsU_kA7KfRPHKEw.png" /></figure><p>So bear with me here. Some of these things might seem a bit abstract at first, but hopefully you’ll start to see the relevance as we go through.</p><p>I’m going to ask you to take pride in <strong>being a professional</strong>. What does this mean? We are a very young industry, but in a ridiculously short timescale, the entire modern world has come to rely on software and the people writing it. 20 or 30 years ago, the idea that badly written software could cause the world’s economies to go into meltdown, or cause nationwide electricity blackouts, or cause cars to crash into trees, was fanciful. Now, the truth is, every aspect of life as we know it depends on someone *exactly like you* not screwing up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g9XgSrquXggLquVbrmHIGA.png" /></figure><p>But our industry hasn’t kept pace in terms of professionalisation. Think about this: anyone can work in software development if they can talk their way into a job. There are no minimum qualifications, no universally enforced professional certifications.</p><p>You can’t become a brain surgeon or an airline pilot or a nurse or a lawyer or a vet without having the right professional qualifications. In fact, you’d probably be a little concerned about ever going to the dentist if anyone could become a dentist just because they nailed the interview on the day. But literally anyone can apply for a job in software development.</p><p>(As an aside, apparently when they launched the first fully fly-by-wire aeroplane, the Boeing 777, they made the software engineering managers sit on the test flights. I imagine that helped focus their minds during the QA phase!)</p><p>Don’t get me wrong, it is great that our industry is finally seen as sexy. God knows I’ve been waiting long enough. It’s great that people are retraining and coming into the industry and helping with the skills shortage. And the flipside of that is that having a Computer Science degree is also definitely not the same thing as being a competent developer.</p><p>And of course not all software jobs are equally critical. If you are writing colourful apps for toddlers, the bar is not as high as if you are writing control software for nuclear power plants.</p><p>But what I am urging you to do is to aim to be amongst the minority of true professionals. By which I don’t mean “don’t turn up to work drunk”. I mean professional in the sense of treating your job as having serious, formal accountabilities that go with it. Take your craft seriously. Take the time to learn about the practices that some of the leading lights in our industry write about, such as formal software design patterns.</p><p>You may have heard the term ‘boy or girl scouting’ in the context of code — leaving it better than how you found it. Well take that up a notch: a professional software engineer, should aim to leave the *industry* in a better state than how they found it. So how do you do that?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FqC89Lo7OnrGsDjdRaB1hw.png" /></figure><p><strong>Have a side hustle or two. </strong>There is no better way to keep your skills sharp and stay in the habit of solving problems than doing it for something that you are personally invested in. Build an app, run a community website, become a key contributor to an open source framework. Find something you are passionate about and spend time working on it — it may even one day make you lots of money. Or it may not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5r8yqsu5II9jj1mDrUhwQ.png" /></figure><p><strong>Be part of your local tech community</strong>. You’re already here, so that’s a great start, but if you don’t already, go to some meetups, apply to take part in Hack24. As you sit there in your second or third meetup listening to someone else talk, you should feel a burning obligation to be standing up there at a future one doing the talking yourself. If the idea fills you with horror, then use that feeling as a way of personally challenging yourself to a) become an expert in something others want to hear, and b) defeat your introverted self and learn to stand in front of a room and talk. It’s an important skill that will help you throughout your career.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6SOJn8SVr5J6njgDN_0CoQ.png" /></figure><p>And still on community, <strong>being an active part of the online tech community</strong> should be top of your list. Don’t be a passive consumer of other people’s knowledge from StackOverflow. It’s not their job to solve your problems, so pay it forward. Every time you find an answer to a problem on StackOverflow, contribute something back.</p><p>Start by thanking them for their answer and explaining how it helped your case. Then maybe find someone else trying to solve a similar problem and answer their question. Then as you gradually acquire expertise in various things, start actively seeking out problems people are having that you may know the answer to. Think of it as equivalent to voluntary work. It will make you feel good as a human being, give it a try.</p><p><strong>Contribute to open source projects.</strong> Have you found an NPM package that was particularly useful? Noticed any bugs in it or thought of a way it could be improved? Could the readme have been a bit clearer? Then put in a PR, no matter how small. Someone just like you has made that package out of a labour of love because they wanted to do something nice for you. Give back.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yf1NvNcsXEi9kCrz21rJDQ.png" /></figure><p><strong>Practice your core skills. </strong>If you were a professional tennis player you’d be practicing your backhand 1000 times a day, or if you were a professional musician you’d be practicing your scales and arpeggios. As a professional software engineer, you can practice your core skills too. Online coding katas are the obvious way to do that. Try <a href="http://codewars.com/">codewars</a> if you like your practice gamified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M1kpmyNIF3wajagilvL1NA.png" /></figure><p><strong>Keep learning. </strong>Make reading tech material a regular habit. Honestly, have you read a techie textbook in the last 6 months? If you haven’t picked up a textbook since uni, force yourself to get back in the habit.</p><p>If dead trees aren’t your preferred reading style, your options have never been greater for keeping on top of a range of material. I use an app called <a href="http://feedly.com/">Feedly</a>, and whenever I’ve got 15 minutes to spare, I’ll open it and flick through a few dozen articles in my feed and maybe read one or two that sound interesting. And of course there are loads of MOOCs — free or bargain online courses on every subject imaginable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZDcKYa6pTXMq3A9VC1zaw.png" /></figure><p><strong>Adjacent skills and practices. </strong>I love meeting a naturally talented coder. What a love even more is meeting a natural coder who has reached the point in their career when they’ve started to understand about the adjacent skills and practices that make for well-rounded, well-engineered solutions. A good driver doesn’t just understand how the car’s pedals and steering wheel work — they know about traffic systems and traffic laws and road signs, they know how to cope with different weather conditions, they know how to read the road, they know a bit about the psychology of other drivers, they know when to give way and when to accelerate out of danger.</p><p>So if you’re a developer, I want you to know at least SOMETHING about test practices and frameworks. About continuous integration and delivery. About performance and scalability. About security. About writing clean code. About debugging. About cloud architectures. About different types of databases. About monitoring. About version control workflows. About agile methodologies. About Domain Driven Design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c893G4n1ouG7mdKQJjjKZQ.png" /></figure><p><strong>Work on your soft skills. </strong>Obvious stuff like presenting, writing clear email. — there’s plenty of online resources about this stuff. But also, if you’ve never done one, take a Myers Briggs or similar personality classification test online, and find out what your strengths and weaknesses are. I don’t normally buy into this stuff, but it was a revelation to me that people don’t necessarily conceptualise information in the way I do, so I made a conscious effort to address that, and suddenly I was getting through to people I hadn’t previously managed to get through to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ngxXfDiv3Q_cAp0klUwZWA.png" /></figure><p><strong>Seek help from others. </strong>Do you think Roger Federer doesn’t still get tennis lessons from a coach? Find someone who you respect and ask them to mentor you or just ask them if they don’t mind spending a few minutes of their day explaining why they did something a certain way. Or even ask your colleagues to sit with you and critique your thinking. Don’t be so arrogant to think that you know it all already or think it’ll look weak if you ask someone for their advice.</p><p><strong>Give your help to others. </strong>Everyone has something to offer. Everyone. If you don’t feel comfortable just going to other people and imparting your wisdom, there are other ways of doing it. Offer your wisdom to the huddled anonymous masses by blogging about something you care about, or as suggested a minute ago, seek out <a href="http://stackoverflow.com/">StackOverflow</a> questions you can answer. Stream yourself coding on <a href="http://twitch.tv/">Twitch</a>. Yes, that’s a thing.</p><p><strong>Teach to learn. </strong>Teaching is also a great way of learning something yourself, and it also helps you to develop your empathy muscles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u5ooPlB6DDO_yykMb70Mfg.png" /></figure><p>Final one for now: <strong>develop a point of view</strong>. By this I mean, as part of a global community of software developers, you should have opinions about things. Is this latest silver bullet javascript framework really better than the last one? What’s with everyone using MongoDb these days? Should developers operate in an ethical framework? Is blockchain the future of cat memes?</p><p>Take time to connect the dots between your individual opinions and talk about them with your colleagues. Anyone who uses Twitter knows that individual rants are boring. Having a point of view, based on trends that you have observed over time, and a central theme or narrative, is interesting. Develop a point of view and it will not only help you in your job, it will give you something to blog about, and guess what, it’ll give you something to talk about in interviews.</p><p><a href="https://medium.com/@neil.oconnor/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-2-of-3-424965f4ed86"><strong>Continue to part 2 &gt;&gt;</strong></a></p><p><em>(Opinions are those of the author, not the company. All images used are copyright of the original publishers, who are too numerous to track down given the sheer volume of memes in this talk!)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=808819940f6e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/koodoo/cto-secrets-get-the-best-companies-fighting-to-hire-you-part-1-of-3-808819940f6e">CTO Secrets: How to get the best companies fighting to hire you (part 1 of 3)</a> was originally published in <a href="https://medium.com/koodoo">Koodoo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>