<?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 Craig Sullivan on Medium]]></title>
        <description><![CDATA[Stories by Craig Sullivan on Medium]]></description>
        <link>https://medium.com/@craigs-io?source=rss-da3d3b5b1a98------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OLsYuDcZ1yX4szzCsTf0qA.png</url>
            <title>Stories by Craig Sullivan on Medium</title>
            <link>https://medium.com/@craigs-io?source=rss-da3d3b5b1a98------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:41:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@craigs-io/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[The joy of end to end type safety]]></title>
            <link>https://medium.com/digit-co/the-joy-of-end-to-end-type-safety-d47d9fd4161f?source=rss-da3d3b5b1a98------2</link>
            <guid isPermaLink="false">https://medium.com/p/d47d9fd4161f</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[engineering-at-digit]]></category>
            <dc:creator><![CDATA[Craig Sullivan]]></dc:creator>
            <pubDate>Wed, 09 Jun 2021 06:52:39 GMT</pubDate>
            <atom:updated>2021-06-09T11:10:47.200Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="The joys of end to end type safety with TypeScript and GraphQL" src="https://cdn-images-1.medium.com/max/1024/1*00ShabrVzSGbK6GBnCOapA.jpeg" /></figure><p>A common pattern for apps is to split our architectural concerns in half. Our back end services contain all the logic for our application while front end systems are devoid of any business logic.</p><p>The two halves communicate via an API layer.</p><p>In building large scale TypeScript applications, we have seen the benefits of types. They elevate our quality, eliminating whole categories of bugs. They enrich the development experience.</p><p>I want to show you an approach in which you can unlock the joys of end to end type safety with TypeScript and GraphQL.</p><h3>Sample application</h3><p>To demonstrate end to end type safety, I have developed sample api and web applications in NextJS. The <a href="https://github.com/craigs/e2e-type-safety/tree/main/api">API</a> is a simple GraphQL endpoint that retrieves users from GitHub’s API.</p><p>The <a href="https://github.com/craigs/e2e-type-safety/tree/main/web">web application</a> uses Apollo client to call our API and render the list of users on a page.</p><p>The repository is available at <a href="https://github.com/craigs/e2e-type-safety">https://github.com/craigs/e2e-type-safety</a></p><h3>The GraphQL API</h3><p>The GraphQL schema language is a typed language. As a front end developer, we really don’t care that it can be implemented in any programming language. What we really care about is that the API is our source of truth for our data and consequently, our types.</p><p>As data changes in the API, we want to know about the changes. We want to be able to inspect the hierarchy and we want to be able to easily understand what it all means.</p><p>Let’s start our <a href="https://github.com/craigs/e2e-type-safety/tree/main/api#readme">sample API server</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aHCz96TXH58kzo8tX6BrWw.gif" /><figcaption>Start the demo GraphQL API server</figcaption></figure><p>Once you have followed the instructions and have your API server started, you will be able to access the API playground on http://localhost:4000/api</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uR9OnS-4093FS13IrLua6g.png" /><figcaption>GraphQL Playground, with Schema and Documentation</figcaption></figure><p>Being able to test your queries with access to the schema definitions and documentation as defined by the back end team is pure joy.</p><p>In this instance, I have my query and can use that in my front end application.</p><h3>Web application</h3><p>Our web application uses Apollo Client to talk to our GraphQL and is written in TypeScript. The back end development teams have crafted a beautiful API for us with all the types that we need. What we do not want, is to write or maintain our own copies. The API is our source of truth.</p><p>We want to just maintain our queries and mutations and automatically generate our TypeScript types and React hooks for Apollo Client.</p><p>First of all, let’s take a look at the web application and see what it does.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_JXRexNqUNlGKy1FJjpCw.gif" /><figcaption>Start the NextJS web application</figcaption></figure><p>With both the API and Web running, you will be able to see your application on <a href="http://localhost:3000/">http://localhost:3000/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FMPxkAlgoMd0sDFRYUe2aQ.png" /></figure><p>If you take a look at <a href="https://github.com/craigs/e2e-type-safety/blob/main/web/src/pages/index.tsx#L10">src/pages/index.tsx</a> you will see that it uses the useUsersQuery() custom hook. These are imported from <a href="https://github.com/craigs/e2e-type-safety/blob/main/web/src/pages/index.tsx#L5">~graphql</a> located in <a href="https://github.com/craigs/e2e-type-safety/blob/main/web/src/generated/graphql.ts#L69-L87">src/generated/graphql.ts</a>. Just to be clear, we wrote the <a href="https://github.com/craigs/e2e-type-safety/blob/main/web/src/graphql/Users.query.graphql">Users.query.graphql</a> file and then used a completely generated custom hook that used a generated User[] type all validated against our API. That is joyous!</p><h3>Code generation</h3><p>So how were the types and custom React hooks generated?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AV5ffzO2A0a-QNQCtvkdLw.gif" /><figcaption>npm run codegen</figcaption></figure><p>The <a href="https://github.com/dotansimha/graphql-code-generator">graphql-codegen</a> library validates our *.graphql queries and mutations using the endpoint in <a href="https://github.com/craigs/e2e-type-safety/blob/main/web/codegen.yml#L2">codegen.yml</a>. It then generates all the required TypeScript types and creates React hooks for us. Just lovely.</p><p>Run <a href="https://github.com/craigs/e2e-type-safety/blob/main/web/package.json#L9">npm run codegen</a> to see it in action.</p><h3>Linting is your friend</h3><p>We want to be hyper aware of is when the API changes. Codegen ensures that we are perfectly in sync with changes to the API. Our types will change and TypeScript will do what it does best and ensure that our front end application adheres to the new shape of data.</p><p>But we can do better than be notified at compile time. Linting can really bring a level of happiness to developers by informing you of the changes at design time.</p><p>In the sample app, I have a field called <em>name</em>, which I have deprecated in the API. The deprecation notice includes instructions to the developer. If you open Users.query.graphql, you will see that the name field is underlined with our nice helpful message displayed.</p><p>Likewise, if I try to add a field that does not exist, my linter will helpfully remind me to not be crazy. If you miss the message in your IDE, eslint will let you know about it in CI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g1gxyIe7hRm01m0wO8ZsTA.gif" /><figcaption>Linters in action. They really are here to help.</figcaption></figure><h3>A more refined developer experience</h3><p>With end to end type safety in operation, TypeScript features like autocomplete start to play a role in the development experience. Autocomplete will bring the shape of our data to our finger tips, it will let us know what is available and what you shouldn’t use any more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J1tZA2rfc94bjSMgIBETug.gif" /><figcaption>Autocomplete shows you what is available, and what to avoid.</figcaption></figure><p>We can go a step further to look after developers by recommending plugins to their IDE that will help them develop in this environment. The key point here is to help bring the easiest, most helpful development ecosystem to your team’s finger tips.</p><h3>What can we do if we cannot use GraphQL?</h3><p>It is not uncommon for GraphQL to be difficult for established organisations to adopt. If you are using normal REST style endpoints, you cannot generate your types dynamically.</p><p>What is possible is importing your back end shared types library. You will have to be aware that this library is consumed by two parts of your ecosystem and that you may not want to leak internal back end types with front end applications.</p><p>There is nothing preventing the existence of multiple type libraries to overcome your specific design issues.</p><p>I do have a preference for regenerating types from my GraphQL, but if GraphQL is not an option, I’ll take a shared type library any day.</p><h3>So what’s the take away?</h3><p>The benefits of types are well understood. As teams and codebases evolve and grow, the arguments for TypeScript adoption begin to intensify. What is important is to consider the experience we deliver to our developers. Clean architectures with low cognitive friction pay handsome dividends. We want one source of truth for our types. We do not want to write code that we do not have to. We want feedback as we type, not after a long time in CI.</p><p>The goal of end to end type safety is to eliminate whole classes of bugs, embracing change and enhancing communication through teams. It’s about bringing little moments of joy in the development experience so that our developers can focus on obsessing over bringing the best experience to our customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d47d9fd4161f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digit-co/the-joy-of-end-to-end-type-safety-d47d9fd4161f">The joy of end to end type safety</a> was originally published in <a href="https://medium.com/digit-co">EPD at Digit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Ace Developer Technical Interviews]]></title>
            <link>https://medium.com/swlh/how-to-ace-developer-technical-interviews-725248637fc?source=rss-da3d3b5b1a98------2</link>
            <guid isPermaLink="false">https://medium.com/p/725248637fc</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Craig Sullivan]]></dc:creator>
            <pubDate>Tue, 11 Aug 2020 02:08:52 GMT</pubDate>
            <atom:updated>2020-08-12T15:14:24.715Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9xyebyMLkE38J5cA3uVY4w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@richtervet?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Rich Tervet</a> on <a href="https://unsplash.com/s/photos/code?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Technical interviews for developer jobs can be difficult. You are sure to fail a few until you grasp what people are looking for.</p><p>I conduct many interviews so here are my tips on getting through to an offer.</p><h3>The take home challenge</h3><p>Many companies have a take home coding challenge. It normally consists of a written problem and a description of what the reviewers of your submission are looking to see. Some will let you choose what language to tackle the problem in, some may specify what you have to use.</p><p>Please, read the instructions. Let it soak in for a period of time and read it again before you start. I have reviewed many submissions where people have only read the first part of what’s required and then dived in to writing the solution. I would re-read the requirements info before you submit your solution to ensure you have ticked all the boxes. Failing to meet the requirements will get you cut early.</p><p>With submissions I review, here is what I am looking for.</p><p><strong>Have you added a well written README?<br></strong>I will start here and follow your instructions to the letter. You probably should do the same.</p><p><strong>Does it work?</strong><br>Nah seriously, does it actually run and produce correct results? I will run it and verify the results.</p><p><strong>Does it have tests and do they pass?<br></strong>I am going to run the tests. I am looking for green here. I’ll probably also notice if there is only 1 test or 300. I’m looking for a good amount of testing to ensure that the program produces the correct results, but not overkill. It goes without saying, you should add some tests!</p><p><strong>Have you got a git history?</strong><br>I’ll check that a git history exists. I’ll load it up in my favourite GUI tool and scroll through the commits. I wont be looking for what order you work in. Some people go strict “tests first”, others do a little coding and then do a little testing. What I am looking for is that you have some method to the way in which you work.</p><p>If you tick off these, you will probably pass the first round of screening to see if you can actually code.</p><p>As the roles get more senior, I’ll pay more attention to the commit messages, the sorts of payloads that are in the commits and try to work out ways of working.</p><p>If you want to really make certain you progress, then here are a few tips.</p><p><strong>Take it seriously</strong><br>Treat the exercise like this is your profession. You’re coding to land the job. Add linters and code quality to make sure you code looks wonderful. I often open up submissions and it’s all over the place. My IDE is set up to highlight trailing whitespace in red, draw lines between the brackets. When you’ve got your indentation and formatting all wrong, I do see it. It’s not a hanging offence, but it can affect what pay scale level is recommended if you receive an offer.</p><p><strong>Cheat and prototype your solution<br></strong>If you can’t immediately see how you want to tackle the solution, do a prototype first. Forget testing, just work through the problem, get your head straight. When you’ve got a prototype solution, start a new project, the one you are going to submit. This way, you can show a clean pattern to match the expectations of the reviewer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G1Y71S6H20wCW7WbgrQXew.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@headwayio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Headway</a> on <a href="https://unsplash.com/s/photos/interview?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>The pairing interview</h3><p>The take home challenge was to see if you can code or not. The pairing interview is different.</p><p>What I am primarily looking for is what it is like to work with you. Everyone knows that I am looking to see if you wrote that submission and can code like we saw in the take home challenge. I am also looking to see how you approach a problem. I am looking to see what it’s like to work by your side. Are you a decent human? Are you a control freak? Are you doing OK with the pressure of the pairing session? Is the problem too hard to work through?</p><p>Here’s a few secrets from some of my pairing interviews.</p><p>Yes, the problem can be difficult. There is only a limited amount of time to work on the problem. No one has got to a working solution within that time window. Just keep calm.</p><p>I have been in pairing interviews where we didn’t even get started in the problem because the candidate just got overwhelmed. I will try to make you feel comfortable. I do understand that it’s stressful. I will try to help.</p><p>In my company, we provide a skeleton application that takes care of the boilerplate work. This is because we don’t want to waste your time showing us how to set up a project. We are looking to get in to the problem space and see how you work towards a solution.</p><p>Want a successful pairing session? Here are some top tips.</p><p><strong>Treat it like your day job<br></strong>Acknowledge the time constraints and talk to your interviewer like it was your first day on the project. Chat about the ways you want to work on the problem. For my part, I’ll make sure that you are aware that I am not looking for all the answers and that it’s OK to ask me, Google or Stack Overflow for the answer. Heck, without Google, I’m not much of a coder at all.</p><p><strong>Do code</strong><br>We want to see you code, so don’t spend all your time designing the solution or talking about the problem. Remember that I have to check off that you were the person who added the great work in the code submission. So write some tests, write some functions or classes. This really should be your priority.</p><p><strong>Chat!<br></strong>Talk about what you are doing and your ideas as you work through the problem. It helps me understand the way you are working. It’s also a great way to pair. I can ask questions and we can discuss ways to solve things. I may not have all the right answers. Sometimes I have the wrong answers and you might even see me Googling the syntax. If things are just rolling along smoothly, feel free to chat to me as a person.</p><p><strong>Want to impress? Use git</strong><br>Not many people demonstrate using git. Nearly no one. So when someone does, it just feels so good.</p><p><strong>Get a rhythm going<br></strong>Whatever your normal workflow is, use it. For me, I look at a small chunk of the problem and I write some code. Then I write some tests. Then I fix my code and write a few more tests. I then check in my little feature and move on. Work to a drumbeat that shows how you work, I will notice it.</p><p><strong>Be friendly</strong><br>I’ll always ask some question about you as a person while we’re coding. Small talk like how far away you live or if you are a dog or cat person. It’s a way I can start to see if you would be great on my team. That’s my big goal — would I want you on my team? If you can code, problem solve, handle diversity of opinions, ask for help and above all, are friendly, the answer will be yes and you will most likely pass this round.</p><p>We’re not looking for robots. We like working with nice people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kAJWgaK0u-Ws-pvq5PP1VQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@heftiba?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Toa Heftiba</a> on <a href="https://unsplash.com/s/photos/coffee-meeting?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>The values or culture interview</h3><p>I always tell everyone that you can’t fail a values or culture interview. You might not fail, but you definitely might not be selected.</p><p>To be successful in a values interview, I am looking for a few things.</p><p><strong>Openness<br></strong>I have interviewed people who are determined to give me the right answer. But this is a chat about your values and the questions are designed to tell honest stories. We’re looking for open minded people. Feel free to tell your story. If someone doesn’t want to hire you because you were honest and open, you shouldn’t want to work for them either.</p><p><strong>Empathy<br></strong>I always look for empathy for others. Questions like “Have you ever had a disagreement with others?” has only one possible answer. We all know the answer is yes. Tell a story, be open and honest about how it made you feel. What I am really looking for is if you can see the disagreement from the other side. Are you someone who shows empathy.</p><p><strong>Honesty and blame</strong><br>I’ll always be looking that you are honest in your stories and that you are not quick to blame someone. I really enjoy working in a zero blame environment where people feel safe to be honest. This is the purpose of the values interview to me.</p><p>I want to work in a place where people are supportive. Where people try the hard things and fail sometimes. I want to work where people are honest and non-judgemental.</p><p>I work at <a href="https://cogent.co/careers/">a place like this</a> now and I trust that the core culture is protected by the people conducting the interview process.</p><p>Be yourself, it is really hard to be anyone else. Good luck in your journey.</p><p><em>*This article was originally published on </em><a href="https://craigs.io/articles/how-to-ace-developer-technical-interviews"><em>craigs.io</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=725248637fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/how-to-ace-developer-technical-interviews-725248637fc">How to Ace Developer Technical Interviews</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upping my Zoom (video conferencing) game]]></title>
            <link>https://craigs-io.medium.com/upping-my-zoom-video-conferencing-game-eb7ee60dfd4d?source=rss-da3d3b5b1a98------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb7ee60dfd4d</guid>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[video-conferencing]]></category>
            <dc:creator><![CDATA[Craig Sullivan]]></dc:creator>
            <pubDate>Thu, 06 Aug 2020 02:45:36 GMT</pubDate>
            <atom:updated>2020-08-12T08:52:17.157Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VN3TpI-ORWACGaZDVPWjNQ.jpeg" /></figure><p>It was Friday company drinks. We were all in awe by our colleague <a href="https://www.linkedin.com/in/brett-wilkins/">Brett Wilkins’</a> brilliant camera and lighting setup. He looked awesome!</p><p>Brett did a great job of writing about his setup on our slack channel. Excellent mirrorless DSLR, <a href="https://www.elgato.com/en/gaming/cam-link-4k">Elgato camlink</a> to connect the HDMI from the camera to the computer, mounts and <a href="https://www.elgato.com/en/gaming/key-light">great lighting</a>.</p><p>Inspired, I looked around to see what I could do with a limited budget. Getting a great external camera is a bit pricey. The Elgato camlink is pricey. Lighting kits are expensive. Mounts are expensive.</p><p>Then I noticed that I have an excellent camera — my iPhone! It is so much better than the MacBook Pro internal camera. I decided to connect my iPhone to my MacBook and use it as my webcam.</p><h3>The setup</h3><p>My setup is familiar to many developers …</p><ul><li>MacBook Pro</li><li>iPhone 7 plus</li><li><a href="https://www.apple.com/au/shop/product/MKQ42AM/A/usb-c-to-lightning-cable-2m">Lightning to USB/C charge cable</a></li><li><a href="https://telecast.camera/">Telecast.camera app</a></li><li>I also found that I had a <a href="https://blackeyelens.com/product/filming-handle-tripod/">mini tripod</a> lying around!</li></ul><p>My trusty old iPhone 7 plus is connected to my laptop via a lightning to USB/C cable that I use to charge the phone.</p><p>The iPhone is mounted on the tripod with the rear camera facing me.</p><p>I purchased <a href="https://telecast.camera/">Telecast.camera</a>. This app lets you use your phone as a webcam and you can select what camera on the phone is used in what mode, resolution and frame rate. Total cost $26.99AUD</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u3cNJ-yQ_116XJfgFIFVEg.jpeg" /><figcaption>Telecast.camera allows you to use your iPhone as a camera in your Video Conferencing app</figcaption></figure><p>Open the app on the phone and start the desktop app. You will see your camera feed in to your Mac. You can now select that as a webcam in Zoom or Google Meet. In face, just about any app can let you set the camera used for video.</p><h3>Do not disturb</h3><p>If you are using your iPhone in an online meeting, turn on <a href="https://support.apple.com/en-au/HT204321">Do Not Disturb</a>. It will stop pesky calls and notifications interrupting your camera feed.</p><ul><li><a href="https://support.apple.com/en-au/HT204321](https://support.apple.com/en-au/HT204321)">https://support.apple.com/en-au/HT204321</a></li></ul><h3>Conclusion</h3><p>This is a great improvement over the standard webcam. It is not in the league of Brett’s setup, but better than what I had. I really need to get some lights to improve the scene further. Small talk on calls has increased! People can see the wonderful things in my office and that is what I was trying to achieve.</p><p>For me, face to face communication is really important. If I can make that experience a little more human and feel closer to the people I am talking to, then that is a win.</p><p>I am also happy that it is cheap enough for most people to implement with the tools they have at hand. For less than $27, it’s worth trying. In fact, Telecast has a free tier to get you started. Give it a try. I hope it works for you.</p><p><em>*This article was originally published on </em><a href="https://craigs.io/articles/trauma-never-sleeps"><em>craigs.io</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb7ee60dfd4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer branding toolkit]]></title>
            <link>https://craigs-io.medium.com/developer-branding-toolkit-6e7c532c655a?source=rss-da3d3b5b1a98------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e7c532c655a</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[personal-branding]]></category>
            <dc:creator><![CDATA[Craig Sullivan]]></dc:creator>
            <pubDate>Tue, 07 Jul 2020 03:32:47 GMT</pubDate>
            <atom:updated>2020-08-12T08:49:50.831Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Developer branding toolkit" src="https://cdn-images-1.medium.com/max/1024/1*rKd9c9Nu0NoBHohxO34Jyw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@flysi3000?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Simon Abrams</a> on <a href="https://unsplash.com/s/photos/developer?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Everyone loves being recognised for the effort that is needed to being the best that they can be. Being a developer is hard, requiring focussed effort to keep expanding our abilities.</p><p>Being good at our job is the first step. At some point in time, you will discover that the best superpower you can acquire is being a good communicator.</p><p>So let me help with some great tools to help you communicate with the world outside your team. Let’s start building your brand and tell your story.</p><h3>Acquire naming rights</h3><p>I use a number of services. Most have the ability to set usernames or handles. You will find most common user names are taken.</p><p>I was happy with my handle at GitHub, <a href="https://github.com/craigs">@craigs</a>. I then looked for a personal domain name and then tried to match that to available names at twitter.</p><p><strong>GitHub</strong>: <a href="https://github.com/craigs">craigs</a><br><strong>Domain name:</strong> <a href="https://craigs.io/">craigs.io</a><br><strong>Twitter</strong>: <a href="https://twitter.com/craigs_io">craigs_io</a><br><strong>LinkedIn</strong>: <a href="https://www.linkedin.com/in/craigs0/">craigs0</a></p><p>All starting to be a little consistent.</p><h3>GitHub</h3><p>GitHub is where I spend my days and it is also the easiest to update in order to provide some context about who you are and what you work on. People will definitely click on your profile and look to see if there is anything they can learn about you from there. So let’s give them something.</p><p><strong>Edit profile</strong><br>Update your profile first and add links to everything you can. My description was super simple: “Developer”</p><p><strong>Personal README.md</strong><br>A personal README will allow you to create a markdown file for your GitHub account.</p><figure><img alt="GitHub’s Personal README" src="https://cdn-images-1.medium.com/max/1024/1*RR057WX2OOWKMo_8aE-gxg.png" /><figcaption>Adopt GitHub’s Personal README repository</figcaption></figure><p>Just create a repo with your username and initialise it with a README.md. This file will be presented in the overview section of your profile on GitHub.</p><p>Remember to link relevant words back to your personal site, social accounts and company.</p><h3>twitter</h3><p>Although twitter has a bad reputation for being full of the worst parts of society, it is also home to the brightest and kindest parts of society. The developer community is strong on twitter and it’s a great way to stay up to date.</p><p>Get on board and update your profile. Link to your personal site and be sure to update the description. You will want to keep the same tone of voice as in the GitHub description. It’s about you, make it reflect who you are.</p><p>Sure I just used the word “Developer” for me, but that is reflective of who I am. I am brief and self deprecating.</p><p>Right here, I would recommend starting by following all your team mates.</p><h3>LinkedIn</h3><p>You already probably know about LinkedIn. Take the time to update your bio and skills. If you’re like me and hit the limit of skills on LinkedIn, tailor the skills you choose to list to match the projects that you enjoy working on. LinkedIn is a complete standalone subject, but when you start communicating, do not forget to post an update to LinkedIn.</p><p>Make a habit to connect with who work with, both at your organisation and those you come in to contact with. If you’re up to it and need it, encourage people to write feedback for you. You have the opportunity to request edits and not display it if it’s not what you expected.</p><h3>Personal site</h3><p>Setting up your own personal site will take longer to get configured. I open sourced my site for two reasons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MnD_69lBxCekSk8QSdOL8g.png" /><figcaption>Craig Sullivan’s personal branding site — craigs.io</figcaption></figure><p>Firstly, it was great to allow others to take the source code and adapt it for their needs. It allowed me to teach Next.js, TypeScript and GraphQL. You will be able to run this site for $0. To me, it was important to achieve $0 as this prevented many junior developers from getting their own site up and running.</p><p>Secondly, by open sourcing your site, people who wish to work with you can examine the craftsmanship and decide if that is the sort of person that they would like to work with. Your dedication to improving your craft is the essential part of your personal brand. Do not be ashamed to show off the effort you put in to your work, we’re all on a journey.</p><h3>Start your story</h3><p>With these elements of your toolkit in place, you will be accessible with a consistent message about who you are and what you do.</p><p>The hard part? Start writing. Start tweeting. Start sharing.</p><p>I’m not talking about essays, although you can certainly do that. It is as simple as re-tweeting others, posting about new features in your project on LinkedIn or even logging a book you have read. This is your story and your story is your personal brand.</p><p>People will read over this and get a feeling for the great human that you are and will be happy to reach out to you.</p><p>I too am starting the public branding exercise and publishing ideas. I’ll be open and publish things I learn, both good and bad.</p><p><em>*This article was originally published on </em><a href="https://craigs.io/articles/developer-branding-toolkit"><em>craigs.io</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e7c532c655a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>