A Developer's Honest Definition of a 'Hard Worker'
Description
A screenshot of a tweet from user Nathan Usher (@thenatewolf). The tweet, dated 23/10/2016, displays a humorous, self-deprecating exchange. It reads: 'Interviewer: would you call yourself a hard worker? Me: absolutely. I make almost everything harder than it has to be.' The humor lies in the literal and unexpected interpretation of the common interview question. For senior developers, this is deeply relatable, touching upon the tendencies toward over-engineering, premature optimization, or simply getting bogged down by self-imposed complexity. It's a witty commentary on the fine line between diligence and creating unnecessary work, a hallmark of the developer experience where solving a problem can often feel like a Rube Goldberg machine of one's own making
Comments
8Comment deleted
A junior says this and gets rejected. A senior says this and gets an offer to lead the architecture committee
Proof I’m a hard worker? I turned a one-line awk script into a fault-tolerant, multi-AZ event-driven pipeline - complete with Terraform modules and a post-mortem nobody asked for
The candidate just described every senior engineer's approach to implementing a simple CRUD API: 'Let's add a message queue, event sourcing, CQRS, and maybe a few microservices... oh, and we'll need Kubernetes for our three users.'
Hardest worker on the team: turned a config change into a Kubernetes migration, a feature flag framework, and three ADRs nobody read
This perfectly captures the senior engineer's curse: given a simple CRUD endpoint, we'll inevitably architect a distributed event-sourcing system with CQRS, implement custom serialization protocols, add a message queue 'for future scalability,' and spend three days debating whether to use Protocol Buffers or Avro - all before realizing the original requirement was just to return a user's email address
I told the interviewer I’m a hard worker - I turned a simple if-statement into an event-sourced, eventually consistent microservice so it could horizontally scale our complexity budget
Hard worker? I once Saga-orchestrated a hello world app because 'future scalability'
Interviewer: “Would you call yourself a hard worker?” Me: I once turned a 20-line cron job into an event-sourced CQRS microservice with Kafka and a platform team - so, regrettably, yes