Resume-Driven Development

Noun · Hacker Culture

Definitions

  1. Choosing technologies or architectures based on what looks good on a resume rather than what's appropriate for the problem. Results in unnecessarily complex stacks — Kubernetes for a static site, GraphQL for a simple REST API, or microservices for a team of two.

    In plain English: Picking fancy technologies because they'll look good on your resume, not because the project needs them.

    Example: "We don't need Kubernetes, a service mesh, and event sourcing for a todo app — this is resume-driven development."

Related Terms