• 1 Post
  • 20 Comments
Joined 4 months ago
cake
Cake day: March 8th, 2024

help-circle










  • I can’t count the number of times I start talking about executive dysfunction and someone immediately chirps in with “make a list, chunk it down, say you’re going to do this for 20 minutes and then take a break.” I eventually started asking in response, “Do you suggest to your depression patients simply not being sad? Do you tell your anxiety patients not to worry about stuff? Because that’s what I’m hearing, and it tells me you don’t understand the situation.”









  • I’ve been pondering this one myself for awhile. I knew a decade ago that, barring massive financial change, I would never be able to afford to retire. So these are the options:

    • Work until I die
    • Work until I can’t (or nobody will hire me/pay a living wage), live off of savings until I can’t, then die
    • Stop working, live off of savings until I can’t, then die

    The first two are the default and just kind of accepted by society as fair and just. The last one, strangely, gets all sorts of pushback, even though the only material difference is 20-30 years of mundane toil to make line go up.


  • Is this like the millennial bug?

    Certainly sounds like it. The whole issue was that if year was a two-digit value, it was always interpreted as 19xx. Some systems were updated to require 4-digit years, but many (especially older, niche systems, which plenty of airlines still operate on) just kicked the can down the road. Some made a new static cutoff date for determining 19/20 that someone will have to fix in X years, or a range based on the current date, which sounds like what happened here. Birthdate stored as 25? That means 1925. Birthdate stored as 23? That means 2023.

    Any coders out there want to deal with decades-old tech debt for the remainder of your career? Pick up COBOL and live the dream.