Sign Up
Subscribe today to get The Marjorie’s in-depth environmental journalism and storytelling delivered directly to your inbox.
Subscribe today to get The Marjorie’s in-depth environmental journalism and storytelling delivered directly to your inbox.
Thank you for registering!
An account was already registered with this email.
Please check your inbox for an authentication link.
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.
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.
What’s the worst variable name you’ve ever used to ship a feature? Tell me I’m not alone in the comments.
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.
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.
What’s the worst variable name you’ve ever used to ship a feature? Tell me I’m not alone in the comments.