<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Justin Conway</title>
    <link>https://conwaydev.com/writing</link>
    <description>Writing by Justin Conway</description>
    <language>en-us</language>
    <atom:link href="https://conwaydev.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Looking for a job in 2026</title>
      <link>https://conwaydev.com/writing/2026-11-22-looking-for-a-job-in-2026</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2026-11-22-looking-for-a-job-in-2026</guid>
      <pubDate>Sun, 22 Nov 2026 10:00:00 GMT</pubDate>
      <content:encoded><![CDATA[<p>This is the first time I've seriously looked for a job since 2015, and the market I walked into is a mess. Tech has been laying people off in waves for years now. Apparently more than <a href="https://layoffs.fyi">133,000 people this year alone</a>, and plenty of those folks are going after the same roles I am. If you're looking for a role right now you already know the rest. One job listing can pull a couple hundred applications in a day. Some postings closed weeks ago and nobody bothered to take them down, and some recruiters won't even say which company they're hiring for.</p>
<p>The whole situation wears on you fast. You send an application and hear nothing back, and you can't tell if a person passed on you or if there was never a person at all. After enough of that you start to wonder if it's you. Maybe your resume is off or the work you're proud of doesn't count the way you thought it did. The easy move is to apply to more, but when you're already down and demotivated the quality of what you're writing or submitting starts to deteriorate. There's a whole industry built around this now, with tools that send hundreds of applications an hour and answer the screening questions for you. When you've been at it for months, I get why people hand the whole thing to a bot and let it apply everywhere, but I think it's dangerous for you as an individual, and for hiring managers.</p>
<p>The last time I hired a senior engineer I read through hundreds of applicants, and that was before AI could write a cover letter in four seconds. Now a lot of what lands in a recruiter's inbox was written by a bot and never read by the person who sent it. The folks doing the reading can't tell who read the job and who didn't, so they get suspicious of everyone. At the same time candidates don't trust the AI screening them either. It's a dystopian nightmare, but ultimately means that your application that has always had to stand out in a pile now has to accomplish that AND get past an ATS screening of keywords without sounding like a fake resume.</p>
<p>I don't think AI is the problem here. The issues start when it does things in your name without asking you. Some of these tools will make up experiences to tailor exactly to a job posting. Some will keyword stuff every possible skill a particular post lists. I built a small Claude skill to help out with all of this. It checks that a job is actually open before it shows it to me, scores how well I fit and tells me why, and asks me when it isn't sure instead of guessing or hallucinating. Every cover letter is built from scratch, and pulls from a story I told it and memory the skill has kept over time. It keeps track of which companies have written back and what's gone quiet, either by integrating with my email or just by conversing with the agent. It never submits anything for me, and I've tested some of the alternatives on the market that do this, and it is alarming how much they can get wrong. A few folks I care about are looking right now too so I cleaned it up so anyone can set it up without touching code. If you want to poke at the code it's <a href="https://github.com/conwaydev/job-search-skill">open source on GitHub</a>. I'm also building a hosted version for people who don't want to install anything at all, more on that later!</p>
<p>None of this makes the market less crowded, but it can put you back in charge of your own search. If you're in it right now, don't let the noise talk you out of putting your name on things you actually believe in. Your experience does matter, and your skillsets you've developed in your career are valuable to any number of companies, you just need to continue to advocate for yourself and not get dissuaded by this mess. If you want a hand with the busywork, the skill is free and setup takes about 15 minutes, <a href="https://conwaydev.com/job-search">check it out here</a>. If it helps you land something, I'll be stoked.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Modern engineering leadership</title>
      <link>https://conwaydev.com/writing/2026-01-30-modern-engineering-leadership</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2026-01-30-modern-engineering-leadership</guid>
      <pubDate>Fri, 30 Jan 2026 10:00:00 GMT</pubDate>
      <content:encoded><![CDATA[<p>I’ve been thinking a lot lately about what it means to be an engineering leader right now. Some of the things we anchored our careers to are shifting under our feet, and I keep turning over what that means for the people I lead.</p>
<p>There’s a lot of noise about tools writing code for us. Copilots and agents and whatever comes out by the time this gets published. I don’t think any of it changes what teams need from engineering leaders, though it does make the gaps a lot easier to see.</p>
<p>If I’m being honest, coding was never the hardest part of software development. It was just the most visible one. The hard parts were always human. You had to decide what not to build and explain why. You had to help people grow without crushing their confidence, and ship something imperfect and stand behind it. Code was how we expressed all of that, and AI makes those parts a lot harder to ignore.</p>
<h2>When craft becomes identity</h2>
<p>One of my engineers told me recently that he was hesitant to lean too heavily on AI-assisted tooling. Not because it didn’t work, but because it worked really well. He was worried that the instincts he’d built over years of debugging and shipping would dull, and that he’d lose the thing he built his career on.</p>
<p>He’s not someone who’s afraid of learning new things, and I don’t think his fear is irrational at all.</p>
<p>For a lot of engineers, our value was tied directly to what we could produce with our own hands and brains. We learned through repetition and failure and earned fluency the hard way. When a tool shows up that can do parts of that work instantly, you start asking yourself what you’re actually good at.</p>
<p>That conversation stuck with me because it was really about trust, and whether ten years of experience still counts when a machine can make the same suggestion in a second.</p>
<h2>Coding was never the bottleneck</h2>
<p>The code was never the bottleneck. It just felt like one because it was slow and manual. What actually slowed teams down was bad decisions and unclear ownership. AI doesn’t fix any of that, and sometimes it makes it worse because bad decisions get built faster.</p>
<p>I was taught that the idea of a “10x engineer” at the leadership level was about creating an environment of mentorship and autonomy. I still believe in hiring smart people and getting out of their way.</p>
<p>What I didn’t expect is how much time I now spend setting shared approaches to tooling and workflows. Without some guardrails, reviews get harder and knowledge stops moving between people. It took me a while to accept, but my team now holds one code review bar for everything that ships, whether a person or a tool wrote it.</p>
<h2>The unglamorous part</h2>
<p>It doesn’t sound glamorous to say that part of my job is making sure we’re using tools consistently. It sounds like process. But in an AI-assisted world, alignment is where the leverage lives.</p>
<p>When everyone uses tools differently, results vary wildly and quality turns into a matter of opinion. Consistency means people can spend their energy on the actual problem.</p>
<p>Tooling decisions end up being a kind of mentorship. They tell the team what we value, and they help newer engineers learn how to think about problems. If you’re an engineering leader who feels a little lost right now, this is where I’d start.</p>
<h2>Decisions got more expensive</h2>
<p>When code is cheap, decisions are expensive. If AI can generate something that compiles in seconds, the real question is whether we should build it at all.</p>
<p>I’m spending less time nitpicking implementations and more time asking why we’re choosing one path over another. I’m teaching the team to spot the decisions that are hard to undo and to slow down when they find one.</p>
<h2>Context is part of the job</h2>
<p>AI has no memory of your organization. Your team does. It doesn’t know why a decision was made three years ago. It doesn’t understand customer pain that never made it into a ticket, or the political and operational constraints that shape real-world software.</p>
<p>So helping engineers build and share context matters more than it used to. That means writing down why we made a call and pairing engineers with product and design earlier than feels comfortable.</p>
<h2>Redefining growth</h2>
<p>There’s a lot of anxiety around career progression right now. Writing harder code used to be the obvious path to senior, and that path isn’t as clear anymore. I don’t have a perfect answer. What I’ve been telling my team is that growth now looks like better judgment and knowing when not to automate, and none of that throws away the craft people worked hard to build.</p>
<h2>What the job is now</h2>
<p>I don’t think engineering leadership has become easier. I think it’s become more exposed. Tools take a lot of the friction away, and teams still need help agreeing on what they’re actually trying to do. They still need mentorship and trust, even if the shape of that work keeps changing.</p>
<p>Lately I’ve been orienting my team less around output and more around clear goals and ownership. The better we get at those, the more the tools actually help.</p>
<p>I’m still figuring this out. Some days it feels like I’m letting go of things I used to be really good at. Other days it feels like I’m finally seeing the job for what it always was. The code changed, but the people didn’t. That’s still the job.</p>
]]></content:encoded>
    </item>
    <item>
      <title>9 years</title>
      <link>https://conwaydev.com/writing/2024-07-17-9-years-at-Sprout-Social</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2024-07-17-9-years-at-Sprout-Social</guid>
      <pubDate>Wed, 17 Jul 2024 15:59:00 GMT</pubDate>
      <content:encoded><![CDATA[<p>Y’all, I just hit nine years at Sprout Social! Can you believe it? Anytime a friend asks, "You still at Sprout?" I typically respond with, "Yeah, I’m still at Sprout." I don’t mean this in a bad way, its just that the folks I’ve interviewed and hired usually haven’t stayed even five years at an organization. Every year I go through an existential crisis of “<em>Am I providing value with what I do</em>?” I usually realize that's an annoying question, but this year is different. I’m not going to get a gold watch for my time at Sprout, but there are so many things I continue to learn in my day-to-day. I want to talk about nine lessons I’ve learned working at Sprout Social.</p>
<ol class="list-decimal pl-8 lg:pl-12">
<li class="mt-8">
<h2 class="font-sans text-2xl lg:text-3xl">Be willing to adapt</h2>
<p>Some of my biggest missteps in my career were due to my stubbornness or a “but that’s not what I’m used to” attitude. I spend a lot of time telling my team how important the ability to adapt is because things change! As an individual contributor (IC) software engineer or even a CTO, it is critical to adjust and adapt for the bottom line. A job is a job at the end of the day, but if you have resilience or grit, you’re going to be much better off than those who may be apprehensive about change.</p>
</li>
<li class="mt-8">
<h2 class="font-sans text-2xl lg:text-3xl">Be scrappy</h2>
<p>This was an “old world” Sprout value, but it is an important virtue for the team I work with. Scrappy doesn’t mean “lazy,” and it doesn’t mean “hasty.” To me, being scrappy means accomplishing something with your own sense of urgency. Decision-making becomes difficult as an organization grows, but as an individual, if you have the willingness to accomplish something and the ability to sell it, you’ll be a valuable asset to the organization. Get it done however you need to get it done.</p>
</li>
<li class="mt-8">
<h2 class="font-sans text-2xl lg:text-3xl">Be around the right people</h2>
<p>No engineering or management book covers this nearly as much as they should. I spent years talking about “the Sprout Game of Thrones,” which lent itself nicely to the fact that our executive squad used to be referred to as “The Small Council.” All of my growth within the organization is a direct result of putting myself in front of people that a marketing developer shouldn’t have been. You have to advocate for your worth, and it becomes easier once you really get to know the higher-ups. Some of my favorite moments at Sprout included playing shuffleboard or pool against my CEO. This isn’t easy to do, especially as a remote employee, but when you are trying to grow in an organization, it truly is about who you know. The Sprout alumni group is a beautiful example of this. I hate the “your net ‘worth’ is your ‘network’” sentiment, but especially at a company like Sprout, it’s really important to maintain relationships.</p>
</li>
<li class="mt-8">
<h2 class="font-sans text-2xl lg:text-3xl">Be a little lazy</h2>
Try to automate as much of your position as possible so it doesn’t require mental energy. This was easier to talk about pre-AI, but I truly think that being lazy begets being annoyed about something, which subsequently causes you to care about and finally fix it. Listen, no one loves work, but if you can be fulfilled and be a little lazy? Game over, you’ve hit the jackpot. Try to do as little as possible until you have to do as much as possible to bring you back to doing as little as possible.
</li>
<li class="mt-8">
<h2 class="font-sans text-2xl lg:text-3xl">Be wrong</h2>
<p>In every workshop about employee growth, they talk about the idea of going in with a “growth mindset,” and as much as I agree with this, they never really talk about being wrong. There have been so many circumstances in my time at Sprout where I was way wrong, and that’s how I actually grew. We talk about giving ICs the ability to “fail” but always knowing that there’s a life raft, but to have an IC feel like they were totally wrong? That, in my opinion, is how true growth happens.</p>
</li>
<li class="mt-8">
<h2 class="font-sans text-2xl lg:text-3xl">Be your own boss</h2>
<p>I have an incredible manager. So much so that I can’t imagine leaving the organization unless she did. My manager has been my boss for over five years, and every upward-feedback review cycle I shout out that my boss has never explicitly asked me to do something. This is because I have been preemptive in knowing what my boss may ask of me. By anticipating any ask, I know that I have the agency to do it my own way, but also have the room to fail or be wrong. The most successful people on the teams I’ve led have all had the same mentality that competency for your position can and should be determined by you.</p>
</li>
<li class="mt-8">
<h2 class="font-sans text-2xl lg:text-3xl">Be assertive</h2>
<p>In software development, there’s no shortage of soapboxes to stand on or arbitrary hills to die on (tabs vs. spaces, anyone?), but an important characteristic of being a team player is being assertive and knowing how to sell why you feel that way. Sometimes you’re going to be wrong, but it’s more impactful to make a decision and run with it than to have repeat conversations with the team over and over again because no one really wants to commit. We used to have the “scale of f*cks given,” which was helpful to even allow the space to be assertive. From there, leading the charge and advocating for an approach allows work to actually get done, not just talked about.</p>
</li>
<li class="mt-8">
<h2 class="font-sans text-2xl lg:text-3xl">Be open to feedback</h2>
<p>I hated constructive feedback when I started at Sprout. I had the mindset of “Who are you to be giving me feedback? I’m great at my job.” The older I get, the funnier that hubris is to me. I see it a lot with more junior or associate-level software engineers. It’s important to feel confident (read: not arrogant), but the best growth happens when you start soliciting feedback. Feedback is an important value at most tech companies, and for good reason. When we talk about self-led growth or having a growth mindset, it all depends on a person’s willingness to ask for feedback and really put it into action, even following back up. Recently, I was working with a teammate who received some corrective feedback from a peer. They took it seriously, changed their behaviors and working style with their peers, and then got heralded in a casual stand-up by the person initially giving the feedback. It’s amazing to see that work and how productive they are now collaborating, and it’s entirely because that person wasn’t just open to the feedback, they knew the impact putting it to action would have.</p>
</li>
<li class="mt-8">
<h2 class="font-sans text-2xl lg:text-3xl">Be stoked</h2>
<p>I’m a glass-half-full person almost always, which isn’t very Virgo of me. In nine years, I’ve seen many of the same types of projects, new folks bringing in older approaches, and instead of discrediting or being negative, I love to find the opportunity in trying it again. A big thing I get called out for at work is my energy and passion for what we do. If you’re not stoked on it, then why are you doing it? Again, a job is a job, but it’s almost entirely what you make of it. Why wouldn’t you want to be stoked doing it? The more fulfillment you have in your role, the better work you’re going to do. This isn’t rocket science. Get excited! When you’re frustrated by a project or workload, really take inventory of what is important to you in your career. Paycheck? Sure, but you don’t stay at a company for as long as I have without finding the joy and energy in getting to do awesome work.</p>
</li>
</ol>
<p class="mt-8">So that’s it. Nine whole years. The company I work for is an entirely different operation than when I started, and that’s a great thing. I’ve seen so many stages of the company, and I wouldn’t have had it any other way. The relationships I’ve built and the projects I’ve been fortunate to collaborate on have been an absolute joy. Here’s to nine more years! 😂</p>
]]></content:encoded>
    </item>
    <item>
      <title>Leadership lessons from 1998’s blockbuster hit “Armageddon”</title>
      <link>https://conwaydev.com/writing/2023-07-07-leadership-lessons-from-1998-s-blockbuster-hit-armageddon</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2023-07-07-leadership-lessons-from-1998-s-blockbuster-hit-armageddon</guid>
      <pubDate>Fri, 07 Jul 2023 14:00:00 GMT</pubDate>
      <content:encoded><![CDATA[<p>If you haven't watched it in a while, 1998's "Armageddon" is an incredible work of art. It's part of the Criterion collection for a reason. Michael Bay is doing full-on Michael Bay, and enough Aerosmith on the soundtrack to last a lifetime. Armageddon is the story of a rag-tag oil "roughnecks" team recruited by NASA to save the world from an impending asteroid collision. If you haven't watched it, this should be the sign to stop reading and immediately fire that bad boy up on Amazon Prime. When rewatching this movie all I could think of was how good of a boss Harry Stamper, played by Bruce Willis, is. Harry is a determined leader and exhibits many leadership lessons throughout the movie. From his unwavering commitment to his team's well-being to his ability to make tough decisions under pressure, Harry's character provides valuable insights into effective leadership.</p>
<h2 class="font-sans text-3xl">Resilience and Determination</h2>
<p>Harry is an ideal example of resilience and determination in the face of impossible odds. Despite the overwhelming magnitude of the task, Harry never succumbs to despair or doubt. Instead, he remains resolute, constantly motivating his team members and inspiring them to push beyond their limits. Harry's unwavering determination serves as a reminder that leaders must possess a steadfast resolve, even in the most challenging circumstances, to instill confidence and inspire their teams to achieve the impossible. He exhibits the very definition of "keeping his cool."</p>
<h2 class="font-sans text-3xl">Putting the Team First</h2>
<p>One of Harry's most notable leadership characteristics is his unwavering commitment to the well-being of his team. Harry consistently places his crew's safety and success above his interests throughout the movie. He ensures everyone has the necessary skills and knowledge to fulfill their roles effectively. Harry also fosters an environment of trust and camaraderie, emphasizing the importance of teamwork and collaboration. His selfless approach to leadership serves as a critical reminder that a leader's primary responsibility is to empower and support their team members.</p>
<h2 class="font-sans text-3xl">Making Tough Decisions</h2>
<p>Harry is forced to make several tough decisions with life-or-death consequences in a dire situation. These moments highlight his ability to remain calm under pressure and make swift choices for the greater good. Harry understands that effective leadership sometimes requires making unpopular decisions, but he does so with a clear focus on the mission's success. His willingness to take calculated risks and shoulder the responsibility of difficult choices demonstrates the importance of decisive leadership, even in the most challenging situations.</p>
<p>Harry's leadership in Armageddon provides valuable lessons for leaders in any industry. His resilience, determination, unwavering commitment to the team's well-being, and ability to make tough decisions under pressure set him apart as an exceptional leader. Harry's character inspires his team and the audience, reminding us of strong leadership's critical role in overcoming seemingly impossible challenges. By emulating Harry's leadership traits, individuals can aspire to become influential leaders who inspire and guide their teams to achieve extraordinary results. Software engineering leadership is by no means life-saving missions to life-threatening asteroids, but there are some tidbits I'll be putting into place for my team, and I hope you do as well.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Third Time’s a Charm (Part 1)</title>
      <link>https://conwaydev.com/writing/2021-01-10-third-times-a-charm-part-1</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2021-01-10-third-times-a-charm-part-1</guid>
      <pubDate>Sun, 10 Jan 2021 21:10:00 GMT</pubDate>
      <content:encoded><![CDATA[<p>Over the past year, I've made 2 separate attempts at creating a simple web app for my wife and me to share recipes we find online and track when we make them. It also started because I was interested in seeing if I could scrape NYT Cooking and AllRecipes to store in a centralized location, not that I would do that because that's highly against their terms of service 🤫. Application sounds simple enough, right? Sure, but for some reason, I always abandon the project while I'm building because I'll get hung up on a particular feature or just generally lose interest. Sound familiar? We've continued writing down our week's dinners on our kitchen wallboard and it <em>works</em> but...</p>
<p>New year, new me right? I had some PTO taken while we potty train our daughter, and during naps and when she goes to bed it's off to the races for me. This time I'm taking a different approach, treating it like a legitimate project and mapping requirements, wire-framing (and even designing) before touching code. We'll see if it works!</p>
<h2>The Requirements</h2>
<p>I could very well create this application in Airtable or a Notion doc, but wheres the fun in that? The application's actual responsibilities are very simple:</p>
<ul>
<li>Allow for multiple users to add and edit recipes</li>
<li>Allow for tracking when a particular recipe is made on a particular "account"</li>
</ul>
<p>As I type that out I'm already overwhelmed by the unforeseen complexity. Especially given the "Nice To Have" requirements like</p>
<ul>
<li>Ability to copy multiple recipes' ingredients lists to a "Notes" file for simplified grocery shopping</li>
<li>Ability to "schedule" dinners</li>
<li>Ability to look back in a calendar and see all dinners made</li>
</ul>
<h2>The Process</h2>
<p>On Friday evening after my daughter went to bed I dusted off Sketch and downloaded their <a href="https://www.sketch.com/elements">Elements UI Kit</a> to ease in my "designing". They sure did make it a breeze.</p>
<p><img src="https://conwaydev.com/assets/img/sketch.png" alt="screenshot of sketch"></p>
<p>I began working on the home feed and "Recipe" screen (also I've typed "recipe" so many times over the past few days it's lost all meaning). Ideally, the application when launched "recommends" a dinner recipe that you haven't made in the last week. See? There I go again just adding more complex functionality!</p>
<p>The Elements UI Kit made prototyping and enacting how I wanted to display information a breeze, and not committing to code I feel was really helpful for my process, again once I'm in my editor if I hit a block, I will likely just give it up, but this allowed me to make decisions, second guess myself and quickly create a new approach. The entire evening as I was designing in Sketch I was showing my wife who acted as a fantastic stakeholder (think "make the logo bigger" but for everything).</p>
<p>At the end of Friday evening I got the designs to a point where I felt I had enough to really start going after it, again repeating the very basic requirements:</p>
<ul>
<li>Allow for multiple users to add and edit recipes</li>
<li>Allow for tracking when a particular recipe is made</li>
</ul>
<p>With those in mind, I went to bed and thought of the myriad of ways we could accomplish this technically using any sort of tech. In the next part of this series, I'll talk through my technical decisions and how I began to scope the dev work! Stay tuned!</p>
<p>(<em>Spoiler alert</em>, it's definitely React w/ a Firebase backend because I'm basic 😏)</p>
]]></content:encoded>
    </item>
    <item>
      <title>Top 5 Favorite Album Covers</title>
      <link>https://conwaydev.com/writing/2020-01-03-top-5-favorite-album-covers</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2020-01-03-top-5-favorite-album-covers</guid>
      <pubDate>Fri, 03 Jan 2020 03:50:24 GMT</pubDate>
      <content:encoded><![CDATA[<p>I say that I hate music a <em>lot</em>. Sometimes I actually mean it, but to be totally honest the only form of entertainment I enjoy is anything and everything about rock and roll. The only movies I enjoy are concert films and documentaries about rock and roll in 1970s Los Angeles. The only books I enjoy are biographies of Twentieth century country music recording artists and books on The Beatles. I've been thinking about this a lot recently about what my favorite album covers are (not necessarily my favorite albums are, <a href="https://codepen.io/conwaydev/full/EgLRGV">I've talked about that</a>), so heres a list of some covers I think about often.</p>
<h2>1. Rolling Stones - Exile On Main Street</h2>
<img class="block border border-gray-200" loading="lazy" src="https://conwaydev.com/assets/img/albums/exile-on-main-street.jpg" alt="Exile On Main Street">
<p>This album cover is SO rad! Each image on the cover is like a miniature movie. I've spent hours just gazing at it, and I think theres so much myth and mystery to this period of the Rolling Stones career. The drugs, France, Gram Parsons, all of it. This is my favorite time of this band, and certainly one of my favorite record covers. The cover was designed by <a href="https://en.wikipedia.org/wiki/John_Van_Hamersveld">John Van Hamersveld</a> who designed so many iconic posters and records. I love this quote from <a href="https://www.loudersound.com/features/the-story-behind-the-rolling-stones-exile-on-main-street-album-artwork">Louder</a>:</p>
<blockquote class="border-l-4 pl-2 border-gray-400 text-gray-600">Although it’s widely assumed to be a collage, the main shot was actually a photo of the wall of a Route 66 tattoo parlour, taken by Frank as he passed through in 1950. To underline the key point – that the disreputable, drug-addled and tax-exiled Stones were as much outsiders as the circus freaks – the reverse of the sleeve had shots of the band members assembled in a similar collage effect. When Stones manager Marshall Chess asked Van Hamersveld to select an image from the cover of promotional purposes, there was one obvious choice. “I said: ‘Why don’t we take the guy with the balls in his mouth?’” the designer recalls. “That is the most amazing photo I’ve ever seen.”</blockquote>
<h2>2. Charles Mingus - The Black Saint and The Sinner Lady</h2>
<img class="block border border-gray-200" loading="lazy" src="https://conwaydev.com/assets/img/albums/black-sinner-saint.jpg" alt="The Black Saint and The Sinner Lady">
<p>This is actually why I wanted to write about this. I think about this album cover all the time, it may be my favorite in this list. Everything about it is awesome, but the type is <em>so perfect</em>. The poem! Him ripping that pipe! I'm not a jazz person by any means and I don't want to come off as a pretentious guy putting a Mingus record on a list, but this record cover is undeniably beautiful. The cover photograph was taken by Bob Ghiraldini who took a lot of famous jazz photographs. Most of the Impulse! Record releases have extraordinary covers, but this one is absolutely my favorite.</p>
<h2>3. Amen Dunes - Freedom</h2>
<img class="block border border-gray-200" loading="lazy" src="https://conwaydev.com/assets/img/albums/amen-dunes-freedom.jpg" alt="Freedom">
<p>This was another record that inspired me to make this list. This is a newer release on Sacred Bones Records, and I wasn't very familar with this band, but I am obsessed with this record cover. He looks so FLY and it reminds me of a movie. The album's photography and layout was done by <a href="https://www.tuomaskorpijaakko.work/">Tuomas Korpijaakko</a> who had done the previous Amen Dunes records. I was always a fan of Sacred Bones Salinger-esque consistency with their releases, but I'm all for breaking out of that when a record cover is this good.</p>
<h2>4. Big Star - Radio City</h2>
<img class="block border border-gray-200" loading="lazy" src="https://conwaydev.com/assets/img/albums/radio-city.jpg" alt="Radio City">
<p>Not only an incredible record, but such a beautiful cover. This was my introduction to the photography of William Eggleston and it was a huge realization that so many artists that I love have used his work (one of my other favorites being the cover of <a href="https://en.wikipedia.org/wiki/Tanglewood_Numbers">Tanglewood Numbers</a> by the Silver Jews). The red in the photo is so shocking and this is another one I've ZONED on for long periods of time. In an article by <a href="https://www.theguardian.com/music/2010/jan/14/william-egglestone-rock-photography">The Guardian</a> Eggleston was quoted</p>
<blockquote class="border-l-4 pl-2 border-gray-400 text-gray-600">"It's just a picture I offered out of the blue," William Eggleston says of The Red Ceiling, and its appearance on the cover of Big Star's second album. "I ­happened to run into Alex [Chilton], and he said, 'I'd love to use it.' I said, 'You're welcome to.' There's no more to that story"</blockquote>
<h2>5. Louvin Brothers - Satan Is Real</h2>
<img class="block border border-gray-200" loading="lazy" src="https://conwaydev.com/assets/img/albums/satan-is-real.jpg" alt="Satan Is Real">
<p>The Louvin Brothers are so incredible, if you don't know much about their history I highly recommend checking out the <a href="https://cocaineandrhinestones.com/louvin-brothers-running-wild">Cocaine and Rhinestones episode</a> episode on them, its fascinating. This album cover is just the best. The type is so perfect! The cover was designed by by Ira Louvin and I love the idea of them constructing the set for it. This isn't my favorite Louvin Brothers recording, but the cover is just unbelievable.</p>
]]></content:encoded>
    </item>
    <item>
      <title>On-going Portfolio Update</title>
      <link>https://conwaydev.com/writing/2019-08-28-on-going-portfolio-update</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2019-08-28-on-going-portfolio-update</guid>
      <pubDate>Wed, 28 Aug 2019 01:33:07 GMT</pubDate>
      <content:encoded><![CDATA[<p>I don’t know where it comes from, but any time I think “I should blog about that” it’s quickly followed by, “I should actually redo my entire portfolio, finally add case studies, and use a completely different technology stack”. I feel like I’m not alone in that sentiment and its SO unnecessary, but it’s there.</p>
<p>Well I’m going to do something about, and that something is blogging about me transforming the portfolio. There are so many cool and interesting technologies in the front-end space now that I think its high time I start playing around with them. Theres a ton of decisions to make along the way but I’m going to start with creating an actual CMS rather than markdown files.</p>
<h2>A CMS will make me write blog posts right?</h2>
<p>I’ve been meaning to look into <a href="https://www.netlifycms.org/">Netlify CMS</a>. In my mind, creating a space to write thats not in code will ideally inspire me to write more. Now this is super unlikely, but right now I’m feeling it. So thats what I did! I went ahead and integrated Netlify with my existing set up on GitHub pages. My next steps are definitely going to start migrating the actual “hosting” to Netlify because of how AWESOME the tooling is, but this is the first step.</p>
<h2>Do I have an “End Goal”?</h2>
<p>Not <em>really</em>, but I would like a “fancier stack”, and a place for me to just <em>write</em>, not look at the code that supports this portfolio (this immediately makes me want to redo everything or just ignore what I wanted to write about). There are some things I’d definitely like to accomplish:</p>
<ul>
<li>Use either <a href="https://www.gatsbyjs.org/">Gatsby</a> or <a href="https://www.11ty.io/">Eleventy</a> as a static site generator
<ul>
<li>This site is currently <a href="https://jekyllrb.com/">Jekyll</a> based which is great, but I want to use the cool new shiny stuff!</li>
</ul>
</li>
<li>Actual case studies
<ul>
<li>This is something I’ve said forever, but its so rewarding seeing other developers will well written problem/ solution based case studies and the actual work that went into it</li>
</ul>
</li>
</ul>
<p>Along the way updating the design and using cool new APIs like native lazy loading (are you _kidding_ me?!) and really fine tune the performance.</p>
<h2>Is this a good idea?</h2>
<p>Probably not! I think its super unhealthy behavior to think about a portfolio this much that gets zero traffic and especially when you’re not looking for a job, but I really admire when I see developers with fancy/ up to date websites. I‘ll be creating new posts as this continues and get into more technical parts as they come up. Its an opportunity to “learn out loud”!</p>
]]></content:encoded>
    </item>
    <item>
      <title>Why Greenhouse Rules</title>
      <link>https://conwaydev.com/writing/2018-07-13-greenhouse</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2018-07-13-greenhouse</guid>
      <pubDate>Fri, 13 Jul 2018 21:50:24 GMT</pubDate>
      <content:encoded><![CDATA[<img class="b-lazy" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" data-src="https://dha4w82d62smt.cloudfront.net/items/2r2D40241m1s1b3M3m3y/greenhouse.jpg" alt="Greenhouse.io" />
<blockquote>
<p>Greenhouse is an applicant tracking system and recruiting software designed to optimize your entire recruiting process. Find better candidates, conduct more focused interviews, and make data-driven hiring decisions.</p>
</blockquote>
<p>Sometimes I think that hiring software is a super saturated market. I see companies like Lever, Jazz, Yello, and hundreds of others in the space and I can’t help but think “Why would you try to start to a recruiting software company?”. Granted all of the companies mentioned do an excellent job and serve the needs of their customers, but I want to speak from a developers point of view as to why I feel like Greenhouse is the best.</p>
<h2>1. Their API docs are awesome</h2>
<p>As a developer working with any third party service you’ll know that not all services keep an up to date docs, if they even have docs at all. Greenhouse are utilizing a generator called <a href="https://github.com/lord/slate">Slate</a> that just looks fantastic and above all helps me find exactly what I’m looking for. You can find Greenhouse’s docs <a href="https://developers.greenhouse.io/job-board.html">here</a>.</p>
<img class="b-lazy" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" data-src="https://dha4w82d62smt.cloudfront.net/items/0E2w2S3q1u1x2s3M1Y3o/API.jpg" alt="Greenhouse.io API docs" />
<h2>2. You can just use their Job Board API anywhere</h2>
<p>This to me is the kicker, in that their Job Board API allows for a fully customizable experience. Before getting the chance to use Greenhouse, I had been working on customizing <a href="https://www.jazzhr.com/">JazzHR</a> career pages. Now JazzHR has a wonderful backend and a great administrative experience, but at the end of the day you’re adding CSS to their templates they’ve already made, not allowing any customization. With Greenhouse’s free-for-all Job Board API you can create a specific job board experience tailored to your company. With a company like Sprout Social who truly value the candidate experience, it was a must have to not necessary have a stock approach like companies such as JazzHR and Lever.</p>
<p>Another big side of their open-ended API is that prototyping is actually a possibility. Here’s an example of something I was able to whip up in minutes without it needing to live in our code base to show an experience where a user can filter jobs by location. This may also be a good time to mention that Sprout Social is <a href="https://sproutsocial.com/careers/open-positions/#/">hiring</a>!</p>
<p data-height="265" data-theme-id="dark" data-slug-hash="aYZvLg" data-default-tab="result" data-user="conwaydev" data-embed-version="2" data-pen-title="Sprout Social Open Positions Filter" data-preview="true" class="codepen">See the Pen <a href="https://codepen.io/conwaydev/pen/aYZvLg/">Sprout Social Open Positions Filter</a> by Justin Conway (<a href="https://codepen.io/conwaydev">@conwaydev</a>) on <a href="https://codepen.io">CodePen</a>.</p>
<script async src="https://static.codepen.io/assets/embed/ei.js"></script>
<p>The ability to simply show a list of jobs and their attributes on any web property is a super useful feature. All that said I think that Greenhouse have done a wonderful job with the ability of customization and creating solid API docs to help developers build out awesome experiences.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Performance Testing Tools</title>
      <link>https://conwaydev.com/writing/2017-04-26-performance-testing-tools</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2017-04-26-performance-testing-tools</guid>
      <pubDate>Wed, 26 Apr 2017 21:50:00 GMT</pubDate>
      <content:encoded><![CDATA[<p>Its hard to find web developers in 2017 who don't factor in performance into their day to day work. Stakeholders are realizing that web performance is essential to their business and conversions, and developers are realizing that not everyone in the world is accessing websites from a brand new MacBook Pro with blazing fast internet speeds. As a developer I may go a bit overboard, some may even call it an obsession, but web performance is something I'm incredibly passionate about. It all ties back in to the inclusion of the web, and providing the best possible experience for every person to access your site or product.</p>
<p>I'd like to take this time to showcase 3 different tools I like to use for testing out the performance of whatever I'm working on at any given time. There are tons of various tools and software applications, but I like to use a range of tools to get a common baseline. Creating real world performance metrics is difficult and often inconsistent, but by using different tools you can at least get an idea of what you're doing right, and what you may be doing wrong.</p>
<h3>WebPageTest.org</h3>
<p><a href="https://www.webpagetest.org/">WebPageTest.org</a> is easily the best (free) performance tool I've used. The testing is so thorough and the biggest thing that I appreciate is that they have an API, so you can programmatically run performance tests, allowing for awesome tooling like <a href="https://speedtracker.org/">speedtracker.org</a>. There are also forums filled with really intelligent people who know way more than me about web performance. I personally like to use the visual comparison tool when I am creating a new feature in order to test performance against the current production environment, just in case I'm introducing any new performance regressions.</p>
<h3>GTMetrix.com</h3>
<p><a href="https://gtmetrix.com/">GTMetrix</a> was actually my first introduction to web performance testing. There was a time when I worked for a small web agency and when pitching jobs to clients, things like performance or accessibility weren't part of the scope, often times it was "How can we get this in the hands to our client as fast and cheap as possible". I didn't know any better, but at that time I started getting the hunch that maybe putting 40 different JavaScript files on a page wasn't such a great idea. My coworker recommended me this tool that showed you "everything you were doing wrong with web development". It quickly becoming my bargaining chip. I was able to show stakeholders, and eventually clients an actual number indicating that performance was something we needed to consider up front, not after the fact. I still rely heavily on GTMetrix, I really appreciate their comparison report, and also their merging of both PageSpeed scores and YSlow. Its very validating when working on a larger scale application to score high on it.</p>
<h3>Google PageSpeed Insights</h3>
<p>The last tool I'd like to share is Google's own <a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed Insights</a>. The irony of using this tool is running through various Google sites and services and seeing that not even they can get a perfect 100. I believe that their goal is raise awareness and just because you're a Google product doesn't mean that you can get away with bad performance. This one will always drive me nuts, but often a great tool to share with colleagues, particularly in SEO who may not be factoring in performance as to why their search results are what they are.</p>
<p>There are plenty of options, such as <a href="https://speedcurve.com/">speedcurve.com</a> or the ones listed in the comment section of <a href="https://css-tricks.com/performance-tools/">this CSSTricks article</a>. The bottom line is that creating performant web pages and applications isn't going anywhere. Optimizing images, only loading what we need, and relying on smarter browser caching techniques is very important, and these tools are quick to call out when you're not. We as developers have a responsibility to ship users the best possible experiences in the most efficient ways, hopefully these tools can help you achieve that!</p>
<p><strong>Update (01/03/20):</strong> This is a pretty outdated post, but at Sprout Social we have been utilizing <a href="https://developers.google.com/web/tools/lighthouse">Google Lighthouse</a> for our performance monitoring. It offers fantastic metrics as well as great developer tools to integrate with our tech set up.</p>
]]></content:encoded>
    </item>
    <item>
      <title>2 Awesome Uses for Screaming Frog</title>
      <link>https://conwaydev.com/writing/2016-08-23-screamingfrog-seo-tool</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2016-08-23-screamingfrog-seo-tool</guid>
      <pubDate>Tue, 23 Aug 2016 21:50:24 GMT</pubDate>
      <content:encoded><![CDATA[<p>Recently I've had to learn a <em>lot</em> about SEO in a very short amount of time. I would say the biggest "gotcha" moment I've had is finding out about and using the <a href="https://www.screamingfrog.co.uk/seo-spider/">Screaming Frog SEO Spider</a>.</p>
<img src="https://conwaydev.com/assets/img/screamingfrog.jpg" alt="Screaming Frog SEO Spider" />
<blockquote>
<p>The Screaming Frog SEO Spider is a website crawler, that allows you to crawl websites’ URLs and fetch key onsite elements to analyse from an SEO perspective. Download for free, or purchase a licence for additional features.</p>
</blockquote>
<iframe width="917" height="516" src="https://www.youtube.com/embed/AOzOffh9HIE" frameborder="0" allowfullscreen></iframe>
<p>I have been totally blown away by how you can just scan a whole site in a matter of seconds and see immediately all your broken links and image references. I spent a great portion of my web development career believing that SEO was snake oil sales, but I'm realizing its importance now more than ever <sup>1</sup>.</p>
<p>Screaming Frog rules for performing an SEO audit on your site, but I'd like to point out 2 interesting ways to use Screaming Frog.</p>
<h3>1. Identifying Slow Loading Pages</h3>
<p>Well of course you're an incredible web developer who is the Michael Jordan of web page performance and you never have any slow loading pages ever, right? Well if for some reason you <em>might</em> have some slow pages Screaming Frog can identify those immediately.</p>
<img src="https://conwaydev.com/assets/img/response-time.jpg" alt="Screaming Frog SEO Spider Response Times" />
<p>All you need to do is filter by "Response Time" in the main crawl!</p>
<h3>2. Finding All Lazy Loaded Images</h3>
<p>By default Screaming Frog is really awesome with images. If it finds it in your markup it will automatically make a request for that image, which rules! Now how about if you're a radical web developer who lazy loads all their images so that their users don't have to unnecessarily download each one <sup>2</sup>? Well you're in luck because theres a special part of Screaming Frog called "Custom Extractions". All you need to do is add either an XPath or a regex for your images like so:</p>
<img src="https://conwaydev.com/assets/img/extraction.jpg" alt="Screaming Frog SEO Spider Custom Extraction" />
<p>Then we can see that we got all the images on the page, even though those were already lazy loaded:</p>
<img src="https://conwaydev.com/assets/img/extraction-success.jpg" alt="Screaming Frog SEO Spider Custom Extraction Success" />
<p>I didn't really understand XPath (I still don't), but I find its easiest to get the global images by simply placing <code>//img</code>. Its even easier to get the value through regex, but this will suffice for most cases.</p>
<hr>
<p>Say what you will about Screaming Frog, it's Windows 98-esque UI, or the fact that it probably should be a web app that has a SaaS model, it is an incredibly powerful application that definitely has changed the way I view SEO. There is so much more that you can do with the application, but its an essential tool in performing a real SEO audit of your webite.</p>
<p><em>Footnotes</em>:</p>
<ol>
<li>Caveat, there's still totally snake oil salesmen in that industry.</li>
<li>Lol not me on this site.</li>
<li><a href="http://www.seerinteractive.com/blog/screaming-frog-guide/">seerinteractive.com/blog/screaming-frog-guide/</a> is the best link ever and explains 53 cooler things to do with the software.</li>
<li><a href="https://www.screamingfrog.co.uk/10-features/">https://www.screamingfrog.co.uk/10-features/</a> is also a great list of ways to use the software and actually from the company that develops and maintains it.</li>
</ol>
]]></content:encoded>
    </item>
    <item>
      <title>Using Gulp in a Jekyll Project</title>
      <link>https://conwaydev.com/writing/2016-05-21-using-gulp</link>
      <guid isPermaLink="true">https://conwaydev.com/writing/2016-05-21-using-gulp</guid>
      <pubDate>Sat, 21 May 2016 03:50:24 GMT</pubDate>
      <content:encoded><![CDATA[<p>Even though I’m trying not to rely on JS build systems as much anymore and rather use plain npm scripts, I have to say I still love them. They absolutely changed my life when I started using them. Today I'm going to talk about using Gulp inside of Jekyll. Now Jekyll has a really useful server inside itself, but I prefer being able to control a little more and gulp gives me that ability.</p>
<h4>What is gulp?</h4>
<p><img src="https://conwaydev.com/assets/img/gulp.jpg" alt="gulp"></p>
<p>From https://github.com/gulpjs/gulp it is described as:</p>
<ul>
<li>Automation - gulp is a toolkit that helps you automate painful or time-consuming tasks in your development workflow.</li>
<li>Platform-agnostic - Integrations are built into all major IDEs and people are using gulp with PHP, .NET, Node.js, Java, and other platforms.</li>
<li>Strong Ecosystem - Use npm modules to do anything you want + over 2000 curated plugins for streaming file transformations</li>
<li>Simple - By providing only a minimal API surface, gulp is easy to learn and simple to use</li>
</ul>
<p>I like to use gulp to compile and concatenate my assets, but there is so much you can do with it. The first thing you’re going to want to do is create your package.json file. I find the easiest way is to <code>npm init</code>. Once you’ve generated that you can go ahead and start installing our dependencies we’re going to need.</p>
<pre><code>npm install gulp gulp-sass browser-sync gulp-autoprefixer gulp-plumber --save-dev
</code></pre>
<p>Then you're going to create a file called <code>gulpfile.js</code> and paste this code in there.</p>
<pre><code>var gulp = require('gulp');
var sass = require('gulp-sass');
var browserSync = require('browser-sync');
var prefix = require('gulp-autoprefixer');
var minify = require('gulp-clean-css');
var plumber = require('gulp-plumber');
var cp = require('child_process');

gulp.task('jekyll-build', function (done) {
    return cp.spawn('jekyll' , ['build'], {stdio: 'inherit'})
        .on('close', done);
});

gulp.task('jekyll-rebuild', ['jekyll-build'], function () {
    browserSync.reload();
});

gulp.task('browser-sync', ['sass', 'jekyll-build'], function() {
    browserSync({
        server: {
            baseDir: '_site'
        }
    });
});

gulp.task('sass', function(){
    return gulp.src('_sass/main.scss')
        .pipe(sass())
        .pipe(prefix('last 2 versions'))
        .pipe(minify())
        .pipe(gulp.dest('_site/css'))
        .pipe(browserSync.reload({stream:true}))
        .pipe(gulp.dest('css'))
        .pipe(plumber())
});

gulp.task('watch', function () {
    gulp.watch(['*.scss', 'css/*.scss', '_sass/**/*.scss'], ['sass', 'jekyll-rebuild']);
    gulp.watch(['*.html', '_layouts/*.html', '_includes/*.html', '_posts/*'], ['jekyll-rebuild']);
});

gulp.task('default', ['browser-sync', 'watch']);

</code></pre>
<p>You can see that what we’re doing is instead of letting <code>jekyll serve</code> handle the SCSS we are just compiling it ourselves then running <code>jekyll rebuild</code>. So once you have your <code>gulpfile.js</code> filled with this all you need to do is run <code>gulp</code> and it will automatically spin up a live server and minify your SCSS. Neat!</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
