Coté

Coté

Resume-driven Development

Good wastebook list this episode, but first…

Even the Germans suffer from RDD

Some people actually did a study on resume-driven development. I thought it might be a joke at first, but, no: it appears to be serious. I’m working on refreshing a paper on the pitfalls of building your own application platform (“DIY platforms”),1 so the topic came up and the paper fit in nicely, see below.

Many of the pitfalls we've discussed so far touch on strategic choices and project management challenges. Resume-driven development (RDD), however, is a particularly insidious pitfall because it stems from within the organization, often a consequence of misaligned incentives.

In its innocent form, RDD occurs when your staff, fueled by genuine curiosity and a desire to stay cutting-edge, underestimate the true costs and complexities of building and maintaining a new platform using the latest technologies. They see a fascinating new tool and believe it's the perfect fit, even if it adds unnecessary burden. In its more cynical manifestation, RDD is less about genuine interest and more about self-serving ambition: builders advocating for a platform built with trendy technologies specifically to pad their resumes with highly sought-after experience.

Regardless of its flavor, RDD carries significant organizational risk. As one study on this phenomenon notes:

Extensive RDD-based technology selection may therefore lead to complex or even unmaintainable software consisting of technologies which are not suitable for the requirements, which are unfamiliar to current or future employees, or which did not deliver on their promise and were discontinued.

Part of the blame for this incentives problem can be found in the hiring process itself. Knowing that technical talent is often drawn to novel challenges, those crafting job descriptions might, perhaps unknowingly, make roles sound more cutting-edge and trendy than they truly are. This inadvertently fuels a vicious cycle: prospective employees expect to use new technologies, they actively seek roles that promise this exposure, and once hired, they then push to build with these new technologies.

It's a natural inclination, of course. When you hire people to build systems, it should come as no surprise that they will, indeed, build systems. This tendency becomes especially salient when it comes to platforms. As new building blocks and architectural patterns emerge, these talented builders will be eager to learn their intricacies and integrate them into new platforms.

However, while there are perfectly valid reasons to adopt and even build with new technologies, the danger with RDD is that fundamental architectural and strategic decisions get made based on the individual career development of your staff, not on the long-term, strategic benefit to the organization. This inherent conflict of interest can be a costly blind spot.

When contemplating building your own platform, resume-driven development is a common pitfall that demands careful scrutiny. Be sure to look beyond the allure of the new and evaluate the true benefits of each option against the comprehensive costs and risks, many of which are outlined in the preceding sections.

Here’s a related piece I wrote in August 2024 on the topic.

WhitneyGPT

On this week’s Software Defined Interviews, I interview Whitney about her new infatuation with generative AI. She’s mostly been using it for coding, but also goes over some CFP abstract uses. Listen to it! Subscribe! Enjoy!

Wastebook

  • “Did I ever tell you the time I actually slipped on a banana peel? That was the moment I realized my life is a comedy, not a tragedy.” Guest DJ, The Lounge Show, May 31st, 2025.

  • “Loudcasting.” Hate them so much.

  • “I’m not the Russell Davies anyone wants.” The other Russell.

  • “I’d be a lot more into this stuff if it wasn’t being steamrolled by a handful of tech companies, off the back of exploitation and theft.” Worth pondering for AI marketers.

  • “a sudden explosion of storefronts selling every imaginable commodity, bottling water and branding bread.” Reviewing Gianny Rodari.

  • ”went to columbia university film school but I only stayed there a single semester. I had some wonderful professors but I learned that I don’t like having a lot of conversations in order to work on a story.” Eric Chase Anderson.

  • And: “I put a map at the start of every single chapter instead of just at the start of the book. I assumed this would blow the collective minds of the world’s eleven year olds. however, in a frustrating turn of fate the book was never marketed to the eleven year olds I’d made it for.”

  • “Even Gwyneth Paltrow eats bread now.” Warren Ellis.

  • “If there’s one thing people with depression are used to hearing – it’s that other people have it worse.” Internet Commentary.

  • Competitive outlier.

  • “Executize this” -> “write this for someone who doesn’t care about the topic but needs to deal with it for their job.”

  • “The Robot Chicken sphere.” Blank Check.

  • The AI Fig Leaf - If you consider great literature and art - and entertainment - AI could have created none of it, because it’s so censored and “mid.” There are no boobs and dicks, shits or fucks. Perhaps a place for humans to establish competitive advantage.

  • The purpose of a to do list is what gets done. Wink, wink.

  • “I don’t need this. But I’ll never throw it away. It’ll be someone else’s problem one day.” Noah.

  • Theoretic parking spot in Brussels hotel garage.

  • “a neurasthenic who, in the last three years of his life, locked himself up in a cork-lined apartment, ate an unbalanced diet of coffee and 1 - 2 croissants a day, and became largely nocturnal.” Proust.

  • And: “One easy way to distinguish true art from mere entertainment: How many years did the creator spend languishing in bed to produce it?”

  • “‘I’m not capable of the work I want to do. How can I make better work?’ 'Take something you like,” she said, ‘and try to copy it exactly. Copying teaches you a lot about technique.’" Ibid.

  • “Not my fondest memory.”

  • ”on Twitter or Bluesky, there are five major varieties of short-form social-media post: Here is some information; Look at how funny I am; Look at how stupid my enemies are; Look at how smart my allies are for pointing out how stupid my enemies are; Hello total stranger! You’re an idiot.” PSA from Waco.

  • Related: “It means nothing to me. I have no opinion about it, and I don’t care.” Picasso on the moon landing.

  • “…probably more seduced by the ambrosia-like scent of maple syrup lingering in the room, but yeah.”

WFH with Coraline’s dad.

Relative to your interests

ChatGPT creating an image based on a blurry phone from my RAZR in the 2000s. The original was not this, but this is pretty nice.

Logoff

I forgot I’d dumped the above as an episode draft. This was just going to be links and wastebook, but here we are!

1

We’ve taken the last two versions of the paper down until we refresh it, but you can find the original February 2017 (which means it was probably written ~November, 2016) one here. I wrote a blog article about the 2021 version. As ever, I am biased, but when I read the 2017 one I think: “man, things haven’t really gotten any better, but we sure did a lot of yaml’ing.” I did a survey of 5 don’t build your own platforms studies (all, you know, not academic and driven by vendors). The numbers come out to about the same as that 2017 paper. I’ll have to post some commentary on that soon.

@cote@hachyderm.io, @cote@cote.io, @cote, https://proven.lol/a60da7, @cote@social.lol