Just don't forget to change it before code review.
The whateverthefuckholder : Why the Best Code I Ever Wrote Was Named Out of Spite
Programming, Philosophy, Burnout
You know the moment. You’ve tried the descriptive variable names. userProfileDataAggregator . authenticatedSessionTokenValidator . You’ve written the comments. You’ve drawn the UML diagram on a napkin that is now soaked with cold coffee.
Professionalism is solving the problem, not adhering to a dictionary. Sometimes, the most professional thing you can do is admit that the data structure you are handling is a dumpster fire, and name it accordingly.
What’s the worst variable name you’ve ever used to ship a feature? Tell me I’m not alone in the comments.
let whateverthefuckholder = []; I’m here to argue that whateverthefuckholder isn't a sign of a bad programmer. It is a sign of a sane one. We are taught that code is communication. That customerId is better than x . That specificity is kindness to your future self. And that is true—until it isn't.
There is a moment in every developer’s life—usually around 2:47 AM on a Tuesday—where the sacred texts of Clean Code go up in flames.
Just don't forget to change it before code review.
The whateverthefuckholder : Why the Best Code I Ever Wrote Was Named Out of Spite
Programming, Philosophy, Burnout
You know the moment. You’ve tried the descriptive variable names. userProfileDataAggregator . authenticatedSessionTokenValidator . You’ve written the comments. You’ve drawn the UML diagram on a napkin that is now soaked with cold coffee.
Professionalism is solving the problem, not adhering to a dictionary. Sometimes, the most professional thing you can do is admit that the data structure you are handling is a dumpster fire, and name it accordingly. whateverthefuckholder
What’s the worst variable name you’ve ever used to ship a feature? Tell me I’m not alone in the comments.
let whateverthefuckholder = []; I’m here to argue that whateverthefuckholder isn't a sign of a bad programmer. It is a sign of a sane one. We are taught that code is communication. That customerId is better than x . That specificity is kindness to your future self. And that is true—until it isn't. Just don't forget to change it before code review
There is a moment in every developer’s life—usually around 2:47 AM on a Tuesday—where the sacred texts of Clean Code go up in flames.
Funselektor news delivered to your inbox
