<?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 Cordelia on Medium]]></title>
        <description><![CDATA[Stories by Cordelia on Medium]]></description>
        <link>https://medium.com/@cordeliadillon?source=rss-5c929a7ccb98------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MjlGZlmNOPHHPzJlblDFCA.png</url>
            <title>Stories by Cordelia on Medium</title>
            <link>https://medium.com/@cordeliadillon?source=rss-5c929a7ccb98------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:48:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cordeliadillon/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[When you find your worry twin]]></title>
            <link>https://cordeliadillon.medium.com/when-you-find-your-worry-twin-b7021ef342b8?source=rss-5c929a7ccb98------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7021ef342b8</guid>
            <category><![CDATA[mental-health-awareness]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[co-authored]]></category>
            <category><![CDATA[anxiety]]></category>
            <dc:creator><![CDATA[Cordelia]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 01:14:30 GMT</pubDate>
            <atom:updated>2021-02-03T01:14:30.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Colorful, stylized illustration of two open palm hands, one on top of the other" src="https://cdn-images-1.medium.com/max/1024/1*G_Xvy7thJoLx9wD6r0egag.jpeg" /><figcaption>Image by <a href="https://unsplash.com/@timmossholder">Tim Mossholder</a> via Unsplash</figcaption></figure><p><em>Co-written by </em><a href="http://www.emmapan.com/"><em>Emma Pan</em></a><em> and </em><a href="http://www.cordeliadillon.com/"><em>Cordelia McGee-Tubb</em></a></p><p>What’s it like to be generally anxious and second-guess yourself <em>all the time</em>? For two co-workers with high-functioning anxiety, their inner monologues are riddled with past and present self-doubt. Here is the story of how they found their worry twin in each other.</p><h3>Tuesday</h3><h4>Emma.</h4><p>I wrote an email the other day. Actually, it was a reply to someone else’s email. Upon reflection, the simple task presented a flurry of goals I suddenly felt the need to accomplish: be succinct, sound smart, be clear, include appropriate background and context, provide a summary should the recipient not have enough time to read and watch every attachment, just to name a few. The cycle of writing went, as it usually does, something like: write, re-read, delete, fret, write, delete, proofread, proofread again, fret.</p><p>As if writing the email was not a feat in itself, getting it ready and perfected for the send button was an equally daunting effort. I read, iterated, spell checked, and agonized over word choice because after the fear of inadvertently sending an email to the entire company, sending an email that doesn’t make sense or contains spelling errors would certainly be next.</p><p>When I felt ready, I held my breath, and pressed “send”. It ends there, right? Wrong. I sat hunched in my chair, my face inches from my computer screen, continuing to re-read my email. How would they perceive my email? What would they think of my words? Would they notice the care I had put into it? Was I clear enough? Wait, did the attachments go through? Let me check. Okay, good, the attachments are there. OMG what if I had accidentally left them out? The horror. Should I have written it differently? Did I leave out any critical information? Will they reply? This went on for some time, until I realized that two hours had passed.</p><h4>Cordelia.</h4><p>Yesterday, I spent what felt like my entire afternoon composing a thorough yet concise, humble yet confident email to an executive, providing him with a status update and a request. After getting it edited and reviewed by my manager and my manager’s manager, then re-reading it about 20 times myself, I was ready to send it this morning. But just to make sure, I checked the recipients list, weighed the pros and cons of ending my second sentence with an exclamation point instead of a period, decided on using a period, stepped away to make tea, flipped back to an exclamation point, and checked the recipients list again to make sure it hadn’t changed since I last touched it (it hadn’t). I don’t know how long this whole process took or why it made my hands so sweaty, but I do know that two minutes ago, I finally — finally! — sent that email.</p><p>Now, with an awkward block of meeting-free time ahead of me, I turn to my inbox to start whittling down unread emails. My heart rate has just nearly returned to normal when all of a sudden my unread count jumps up by one and my heart rate jumps exponentially with it. The executive has already replied.</p><p>I take a short breath (deep breathing is not in my wheelhouse) and open the thread. “Sounds good. Will do,” he says. Oh, to reply that effortlessly! With a sigh of relief, I return to my inbox to read the rest of my unread emails and inevitably agonize over how to respond to each one.</p><h3>Wednesday</h3><h4>Cordelia.</h4><p>I plug in my headphones, turn my microphone off, and join the video call for a design review meeting. There are quite a few people here and I double-check to make sure I’m still muted before I take a big slurp of tea. Yep, still muted.</p><p>Emma, a designer on my team, begins a polished, insightful presentation of her work. (Gosh, I wish I could make slide decks as dynamic as hers.) As she shares early research and design explorations, she answers our colleagues’ questions with ease. I kind of want to ask a follow-up question, but I’m nervous; I so rarely speak up in these meetings. Should I? I try to formulate something articulate in my head while we’re still on topic. My hand is shaking as I hover my cursor over the Unmute button. Does this question make any sense? Have I missed the moment to ask it? I finally gain the courage to unmute myself and spit out a frenzied jumble of words, right as Emma’s transitioning into a whole new section of slides.</p><p>I definitely missed the moment.</p><p>That question made no sense. And why did I start it with “Have you considered…”? I was going for engaged and inquisitive, but I think that came off as condescending, like she hadn’t thought of something super obvious! Fortunately, Emma answers just as thoughtfully as she did the previous questions, and I mute myself, type “Thanks!” meekly in the chat, and fade into the shadows for the rest of the call.</p><p>As the work day winds down, I see Emma’s festive emoji response to a colleague’s Slack message and feel a fresh pang of self-loathing about the design review earlier. I feel like I could have been less scattered, could have led with a compliment, could have framed that question any other way. I forget about it for a little bit and focus on the dinner my partner carefully crafted for us and a new (for me) episode of <em>Veep</em>. But later, as I climb into bed and toggle on seven different alarms, it comes back to me. <em>Why</em> did I say it that way? How did it come across to Emma? If another colleague had asked the same question, I wouldn’t have thought twice about it, right? So why am I worrying so much about one thing I said in one meeting? Probably because I worry about <em>every</em> thing I say in <em>every</em> meeting. I’m spiraling and I want to talk this through with my partner, but he’s fast asleep and this really isn’t worth waking him up for. Or is it? I fret about this for a while and decide what I need is a distraction.</p><p>I open the crossword app on my phone, my go-to app for when my mind is racing late at night. Instead of puzzling through my own thoughts, I focus my mental energy on puzzling through someone else’s wordplay. By the time I arrive at 53-Down, my mind is sufficiently distracted and exhausted, and I can finally get some sleep.</p><p>Five hours and 36 minutes later, I’m back where I started: wide awake, puzzling over why I had to be such a bumbling fool in that meeting yesterday.</p><h4>Emma.</h4><p>Nothing motivates and stresses me out at the same time more than presentations. Most of the time, I can’t tell if I’m driven by the fear of failing or the motivation to do well. I’m talking about the presentations where I’m the focal point, speaking about a topic I’m seen as an expert on (despite not seeing myself as an expert in anything, but that’s a blog post for another time), to other experts who, at any moment, can realize I’m a phony and not nearly as qualified as they see me to be. I have found no solution to mitigate this risk except to live life excessively prepared so that I can plan a course of action for every possible question, situation, thing tossed my way. Yes, it is as exhausting (and unrealistic) as it sounds. (Someone once complimented my ability to “see around corners”. It took me years before I realized that I know no other way.)</p><p>So, when Cordelia asked a question I did not previously anticipate during my presentation today, I was thrown off. First, mad and upset at myself for not considering the possibility of the question, then mortified by the clumsiness of my answer. It was a good question. I should have seen it coming. Why didn’t I prepare more? Why did I answer it like that? I sound like I don’t know what I’m talking about. Well, maybe I don’t. Am I even good at my job? What does Cordelia think of me now? What do the other 32 people who were dialed in think? Part of me knows that there’s a decent chance no one even noticed and if they did, they aren’t still thinking about it, hours later. But they <em>could be</em> and I can’t shake the fear of that possibility. Regardless, I am convinced that it was the moment everyone in the room realized that I’m incompetent and underqualified for my position.</p><p>This, along with ruminating on all the other better answers I <em>could have</em> said, is what consumes the rest of what was supposed to be a restful evening. I desperately turn to my usual therapies of sharing the story and accompanying feelings with my husband (who, incidentally, is the least anxious person I know), yoga in my living room, and meditation. Despite my best efforts, I only feel marginally better.</p><p>Eventually, I’m in bed, ignoring the “You’ve reached your time limit…” message on my phone, scrolling Instagram. My Explore feed has become home to puppies I want in my life, perfectly styled food photos, and funny memes I wish I thought of. Tonight, an anxiety themed comic catches my eye. It chronicles someone painfully worried about something and assuming a worst-case outcome. I mean, that’s the story of my life? In the corner I see that the comic creator’s name is Cordelia. Wait, that’s my <em>coworker</em> Cordelia. Is she anxious like me…?</p><p>I finally drift to sleep, and several hours and 6 alarm clock snoozes later, I’m up again. My mind gives me approximately 18 glorious, worry-free seconds before bringing me right back to yesterday’s dreadful design review.</p><h3>Thursday</h3><h4>Slack.</h4><p><strong>Emma:</strong> Hi! I was meaning to clarify my response to your question during the design review. I don’t know if my answer made <em>any</em> sense. Sorry if it was really confusing 😫 Let me know if you need clarification!</p><p><strong>Cordelia: </strong>🤣 OMG, I was going to message you about that moment too — I don’t think my <em>question</em> made any sense. Your answer was super clear, and I love the direction you’re going in for this project! Sorry for putting you on the spot with a jumbled question — I just got really nervous talking in front of that big group 😬</p><p><strong>Emma:</strong> Thanks for saying that but your question actually inspired a new design exploration! 🙏🏼 To be honest, I was worried about how I handled it, so it’s kind of funny that you were also worried 😂</p><p><strong>Cordelia: </strong>Worry twins! <em>👯‍♀️ </em>Glad to know I’m not the only one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7021ef342b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Projectors don’t lie.]]></title>
            <link>https://medium.com/salesforce-ux/projectors-dont-lie-b85ef628b04?source=rss-5c929a7ccb98------2</link>
            <guid isPermaLink="false">https://medium.com/p/b85ef628b04</guid>
            <dc:creator><![CDATA[Cordelia]]></dc:creator>
            <pubDate>Tue, 30 Dec 2014 19:22:33 GMT</pubDate>
            <atom:updated>2015-12-18T18:27:22.574Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IkUwlCs0UfVGP-o8vPzjHQ.png" /><figcaption>Photo by <a href="http://propergems.com/ignite">Adrian Rapp</a></figcaption></figure><p>If you’re a designer at a tech company, you’re probably equipped with state-of-the-art pixel-pushing technology. I’m typing this now on a MacBook Pro with Retina display, where I use Sketch and Adobe Creative Suite (I’m still clinging to Fireworks like a life preserver) for all my design tasks. Our team’s mockups look beautiful and crisp on my Retina screen’s vast landscape of perfect pixels. That is, of course, until we congregate in a meeting room, plug a VGA adapter into my laptop, and see these designs projected onto a fuzzy, washed-out, low-resolution screen. <strong><em>The worst!</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-db6opNphT5CZp_yx4Thrw.png" /><figcaption>My team spending the first half of a meeting adjusting the projector settings</figcaption></figure><p>How many times have you been in a meeting where a design looked strange but was waved away with “Oh, that’s just the projector”? I personally have lost count. Just yesterday, sitting eight feet away from a fairly high-quality projector screen, I felt like I was at the optometrist’s office getting my annual eye exam. Surely, it’s the projector’s fault, right? Yes and no.</p><p>In my experience, projectors don’t lie. They just exaggerate a little. Their screen resolutions, color matching, and general quality vary wildly, but so do those of the devices with which people view your website. Projectors’ tiny exaggerations can help you identify potential issues with your designs before users encounter them. When projecting a user interface onto a big screen, you probably run into the same two problems over and over again. Don’t dismiss them! For each of these problems, there’s a solution that can improve the legibility and usability of your UI.</p><h3><strong>Problem 1:</strong> All the colors are washed out and it’s difficult to see some stuff!</h3><p><strong>What you might say:</strong> Don’t worry, it’s pretty clear on my laptop.</p><p><strong>What’s actually going on:</strong> You’re right, the contrast is higher on your Mac! But if you’re having trouble differentiating elements on the projector screen, chances are many of your users with vision impairments or lower quality monitors will also struggle with this. They don’t have all the context you do, so they won’t know how to fill in the gaps when they can’t see everything on the screen.</p><p><strong>What to do next: </strong>Ask yourself, are the main calls to action still prominent on the projector screen? Can you read all the text on the page, even the text that you consider less important? If your answer is “sort of,” amp up your color contrast. Try going for extreme clarity and then slowly dialing it back to a solution that has great contrast and also meets your aesthetic goals. Run your foreground and background colors through <a href="http://webaim.org/resources/contrastchecker/">WebAIM’s Color Contrast Checker</a> and ensure that they meet <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html">WCAG 2.0 AA standards</a> (WCAG = Web Content Accessibility Guidelines). The contrast ratio between text and background should be at least 4.5:1 for normal-sized text and 3:1 for large text. If you want to be extra sure everything reads well, test your design out in grayscale and with color blindness emulators. Photoshop has color blindness filters built into its “View &gt; Proof Setup” menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*12LLbVojA9ToId_B6t52_Q.png" /><figcaption>Some examples of large text and normal-sized text at different shades of grey on a white background. Alas, depending on how you’re viewing this, the large text examples may not be large at all!</figcaption></figure><h3><strong>Problem 2:</strong> The functional prototype looks bloated! Everything is <em>enormous and smushed together!</em></h3><p><strong>What you might say:</strong> Oh, this screen resolution is really low. Let me just press Command-Minus to make this look the way it should.</p><p><strong>What’s actually going on:</strong> Your website isn’t responsive enough and you should consider a wider variety of viewport sizes. Many of your users will be looking at it with a lower screen resolution. Multi-taskers with larger monitors may have several windows open on their screen at once and will squeeze your site as small as they can in order to interact with your content while doing a bunch of other things. For example, I frequently send my laptop into fan overdrive mode by watching Hulu while editing large PNGs. It’s a minor inconvenience to have to switch to Hulu’s “pop-out” player in order to scale the video down to be 1/3rd the width of my laptop screen. I’d love to see the regular video pages scale down gracefully instead of introducing a horizontal scroll bar. But I digress!</p><p><strong>What to do next:</strong> Go on site visits, set up website analytics, and/or send out user surveys to learn more about your user bases’ most common screen resolutions. If you can’t get information about your users specifically, read more general studies like “<a href="http://www.hobo-web.co.uk/best-screen-size/">Best Screen Resolution to Design Websites</a>.” You can try these out by adjusting your computer’s display settings or using <a href="https://developer.chrome.com/devtools/docs/device-mode">Device Mode</a> in Google Chrome’s Developer Tools to emulate specific dimensions, pixel ratios, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jlRVYg4U_WpMZ8BlUtcSfQ.png" /><figcaption>In Google Chrome Developer Tools, you can easily type in pixel dimensions with which to view your website. In this example, I’m viewing our <a href="http://sfdc-styleguide.herokuapp.com/">Style Guide</a> at 800 x 600.</figcaption></figure><p>Once you have a better idea of the variety of screen sizes at play, adjust your designs accordingly. You might want to try a <a href="https://developers.google.com/web/fundamentals/layouts/rwd-fundamentals/">responsive layout</a>, which takes advantage of relative measurements as much as possible. Consider giving the user more control and allowing secondary panels to be collapsible. In a more structured layout, you can shave off pixels by adjusting padding and reevaluating the sizes you’ve chosen for fixed-width elements. For example, one of my latest projects, the <a href="https://www.youtube.com/watch?v=8WsU0_ghZ_Q">Lightning App Builder</a>, is a WYSIWYG editor with fixed left and right sidebars. Looking at it on a projector screen helped my team realize that the sidebars were a lot wider than they needed to be. We trimmed them down by 80 pixels to make more room for the canvas in the middle. We also made several color adjustments based on projector testing alone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AW9JScNbHQf5jSKXONN9gw.png" /><figcaption>We reduced the Lightning App Builder’s total sidebar width by 80 pixels after seeing how much space the sidebars took up on a smaller projector screen. Users can toggle between “100% View” and “Fit to View” to adjust how large the canvas appears in the builder’s interface.</figcaption></figure><p>The Projector Test is my favorite “gut check” manual UI test, and I encourage you to use it early, often, and especially when ironing out final visual specs. It doesn’t substitute for testing out a functional version of your site in a variety of environments — browsers, form factors, screen resolutions, operating systems, screen orientations, screen readers, etc. — but it’s a good place to start. Embrace your conference room’s projector and challenge yourself to make your designs look stellar on even the fuzziest, most washed-out of screens.</p><p><em>Follow us at </em><a href="http://twitter.com/salesforceux"><em>@SalesforceUX</em></a><em>.<br>Want to work with us? Contact </em><a href="/service/mailto:uxcareers@salesforce.com"><em>uxcareers@salesforce.com</em></a><em><br>Check out the </em><a href="http://salesforce.com/designsystem"><em>Salesforce Lightning Design System</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b85ef628b04" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-ux/projectors-dont-lie-b85ef628b04">Projectors don’t lie.</a> was originally published in <a href="https://medium.com/salesforce-ux">Salesforce Designer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alternatives to “Ninja” and “Rockstar”]]></title>
            <link>https://cordeliadillon.medium.com/alternatives-to-ninja-and-rockstar-8cc108a82c0?source=rss-5c929a7ccb98------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cc108a82c0</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Cordelia]]></dc:creator>
            <pubDate>Sun, 02 Mar 2014 00:00:00 GMT</pubDate>
            <atom:updated>2018-02-21T08:03:39.217Z</atom:updated>
            <content:encoded><![CDATA[<p>Like <a href="http://www.technologywoman.com/2011/11/18/hey-hipster-ninja-isnt-cool-what-developers-really-want-to-be-called-is/">many others in the tech industry</a>, I’m tired of companies referring to web/software developers as “ninjas” and “rockstars.” Recruiters’ job postings are littered with phrases like “rockstar developer” and “coding ninja,” which just don’t make sense. Take a look at Merriam-Webster’s <a href="http://www.merriam-webster.com/dictionary/ninja">definition</a> of ninja:</p><blockquote>A person trained in ancient Japanese martial arts and employed especially for espionage and assassinations</blockquote><p>There’s nothing in this description that is relevant to software development. Sure, you could probably make an argument about how the physical agility developed through martial arts is somehow related to the professional agility of technology teams practicing <a href="http://en.wikipedia.org/wiki/Agile_development">ADM</a>, but that’s a bit of a stretch. Ninjas are trained spies and killers. If you’re using war characters as your metaphorical ideals for software developers, wouldn’t you rather look for people skilled in defense who can fortify your city (i.e. make your product as strong as possible)?</p><p>When I see a job posting asking for a “rockstar developer,” I wonder, what qualities of a rockstar should I embody? The media’s depiction of rockstars involves excessive drug use, promiscuous behavior, lip-syncing on stage, inflated egos, and crowd-surfing, none of which seem appealing or relevant to software development. So what happens if I don’t want to be a rockstar? What if I want to be an indie-folk singer-songwriter with a comfortable coffee shop following? Is there a place on your development team for me and my banjo?</p><p>The main reason the “ninja” and “rockstar” buzzwords fall short is that they’re too vague. When recruiters use these words, they convey “we want someone who’s awesome,” but they don’t identify the characteristics and skills that make someone awesome in their eyes. If recruiters want to refer to other professions in their job descriptions, I propose they get practical and discuss roles with skill-sets that are conceptually similar to those of software developers. Ditch the ideals of <strong>ninja </strong>and <strong>rockstar </strong>and instead look for <strong>sculptors </strong>and <strong>archaeologists.</strong></p><h3>The ideal software developer is a sculptor.</h3><p>There are a remarkable amount of similarities between the <a href="http://www.getty.edu/education/teachers/classroom_resources/curricula/sculpture/background2.html">four main techniques of sculpting</a> and the activities of a successful software developer. Let’s take a look at each:</p><h4><strong>Modeling:</strong></h4><p>Modeling is the process of building up a sculpture from highly-malleable material, like clay. If you’re a technical recruiter, you want to make sure potential software developer hires have this down pat. At the bare minimum, software developers take the raw material of a programming language and use it to create something new. Expert software developers have more advanced techniques and tools — APIs, testing frameworks, architectural principles — that help them mold this raw material into something truly extraordinary.</p><h4><strong>Assembling:</strong></h4><p>Assembling is the process of combining multiple objects or materials together to make a sculpture. Think of this as 3D collage. The Master Builders in <a href="http://www.thelegomovie.com/"><em>The Lego Movie</em></a> excel at this (I just saw this movie and am obsessed!), and software developers should excel at it, too. It’s rare for a feature to use only one technology; good software developers are able to combine several external and in-house libraries, in several programming languages, into one coherent set of functionality. Additionally, when product managers ask them to combine a handful of features into one mega-awesome feature, good software developers know how to refactor and merge code to accomplish this goal.</p><h4><strong>Casting:</strong></h4><p>Casting is the process of creating a sculpture by pouring a liquid material into a mold and letting it dry. What’s brilliant about casting is that you can make multiple copies of the same sculpture. See, for example, the many bronze casts of Auguste Rodin’s <a href="http://en.wikipedia.org/wiki/List_of_Thinker_sculptures"><em>Thinker</em></a><em>. </em>Where this pertains to software development is largely in the process of creating the mold; when good developers write code, they write it in such a way that it is reusable and extensible, so that they and others can use that code to quickly build new products without duplicating effort.</p><h4><strong>Carving:</strong></h4><p>Carving is the process of creating a sculpture by chipping away parts of a hard material, such as wood or stone. Of the four sculpting techniques, this is the only one that is subtractive. There is less room for experimentation here than in other techniques (What if you accidentally chip away too much?), so it is crucial to come up with a plan in advance and work through it methodically.</p><p>In my mind, this maps most closely to the work that software developers do to maintain and improve existing features, which, let’s face it, we spend a lot more time doing than working on new features. There is always something to optimize — whether it be a site’s performance or the code’s legibility — and optimization involves taking away pieces that aren’t necessary.</p><p>Refactoring existing code is an opportunity to refine old, crusty, spread-out functionality into something that is easier to understand and maintain. But not everyone can do it. Refactoring and optimization require a strong understanding of all relevant aspects of the system; complex codebases have complex dependencies, so if you change one thing, chances are you’ll have to change several more so as not to introduce regressions or — the scariest of scary! — cause data loss. An expert software developer must be like an expert stone-carver, carefully evaluating each move for its potential ripple effects.</p><h3>The ideal software developer is an archaeologist.</h3><p>(No, I’m not suggesting that the ideal software developer should take after Indiana Jones and wear a fedora all the time.)</p><p>Unless they’re part of a startup in its earliest stage, software developers spend most, if not all, of their time working within large systems full of code they didn’t write. This can be a huge hurdle to productivity, mostly because complex codebases aren’t nearly as well-documented as they should be. There are a number of reasons why they aren’t. When people are deep within their own code, everything makes sense to them, and it’s easy to forget that outsiders have no clue what’s going on there. Some code is not meant to last long, and a codebase may contain several bandaids with code comments like this:</p><blockquote>// Hacked up temporary fix for bug #8675309<br>// TODO: Refactor this in next release</blockquote><p>Several releases later, the temporary hack is now a permanent fixture, and a new developer is staring at these comments wondering what prevented the previous team from fixing the bug the right way the first time. When adding new functionality to a feature or fixing a bug, I spend at least half my time trying to understand other people’s code, and the rest of the time actually making the change.</p><p>The best software developers know how to be code archaeologists. They are experts at excavating legacy code. Like archaeologists, they are able to analyze the results of their excavations from multiple angles and come to a reasonable understanding about what previous generations — whether a thousand years ago or a thousand days ago — were thinking. They share their findings with others. Through analysis of existing systems, developers gain the requisite knowledge to work on those systems with confidence, to begin chipping away at them like stone-carvers.</p><p>Recruiters don’t write about this stuff in job descriptions because it’s not fun to admit that a role involves digging around in a cesspool of legacy code. But the best developers will welcome the challenge, put on their waders, and stride right into the cesspool knowing that they can learn from whatever they find.</p><h3>The ideal software developer is _____________.</h3><p>The ideal software developer is probably not going to identify as a ninja or a rockstar, but as someone who enjoys the challenges of learning complex systems, thinking through tough problems, and building solutions with a variety of tools. As much as I would love to see recruiters replace “code ninja” and “rockstar developer” with “code archaeologist” and “software sculptor,” these new phrases may not mean anything without context.</p><p>My best advice for attracting talent is to be descriptive and discuss the sorts of interests and skills an ideal software developer would have. If recruiters really want to talk about ninjas and rockstars, or even sculptors and archaeologists, they should spell out the qualities that are shared between those roles and the software development roles they’re advertising. Candidates will identify more with a list of desired skills than with a list of arbitrary buzzwords.</p><p><em>Originally published at </em><a href="http://cordeliadillon.com/tech/2014/03/alternatives-to-ninja-and-rockstar/"><em>cordeliadillon.com</em></a><em> on March 2, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cc108a82c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>