'e' is always "error", I don't have to comment to make that clear! It's also always 'event', obviously. Unless it's a constant, then it's 2.71828.
Replies
The parameter is a string storing a date, what's there that needs documenting? Oh sweet summer child, oh the falsehoods programmers believe about time. This both during code-reviews and during "user story refinement s".
aug 29, 2025, 11:49 pm • 7 0 • view
Time is NOT a flat circle, it's just one very long number.
aug 29, 2025, 11:52 pm • 6 0 • view
But what time zone is that long number in?
aug 29, 2025, 11:55 pm • 3 0 • view
IT DOESN'T MATTER DK, THE LONG NUMBER IS ALWAYS THE SAME, YOU ARE THE ONE WHO IS WRONG FOR TRYING TO MAKE IT BEND TO YOUR LOCATION
aug 29, 2025, 11:57 pm • 4 0 • view
If that means you have to go to a meeting at 2:00 in the morning, well, I guess you should've lived somewhere else, shouldn't you?
aug 29, 2025, 11:57 pm • 3 0 • view
Nooo....you sound like the people that drove me to quit because 'ohhh we can just meet at 5pm after all the other stuff yeah?' while refusing to acknowledge I lived on the East Coast while they were in Cali (I finally had to block 5pm to 8:30am every day in Outlook along with a 30min fooding)
aug 30, 2025, 12:03 am • 3 0 • view
I'm really beating up on myself here. I am the only UTC-8 person on my team. Everyone else is UTC-5, UTC+8, or UTC+10. I genuinely do have 7:00 AM meetings 3 days a week.
aug 30, 2025, 12:12 am • 4 0 • view
Ahh yeah, because we were a federal gov contractor we were only -5 thru -8 for the work that paid the bills, there was also a team I volunteered to help that was -8 and -10.
aug 30, 2025, 12:16 am • 2 0 • view
Omg...last project before I quit last job I wrote in huge letters on onedrive and confluence & all Jira tickets that time was in ISO-8601 format, always in UTC and we were always using Earth Centered Inertial J2000 coordinates unless the UI team specifically queried my microservices for lat/lon/alt
aug 29, 2025, 11:55 pm • 4 0 • view
My backend team was like… "we never specify UTC offset part. And different endpoints the timezone is different. In this one it's 0, in this other one is in the timezone where the business is located." How do we find out the timezone of a business? That's the neat part, you can't! (Invincible gif)
aug 29, 2025, 11:59 pm • 4 0 • view
Try running a spacecraft with 3 different clocks on it!
aug 30, 2025, 1:22 am • 4 0 • view
Oh yeah, I wrote some ETL pipeline software for my last employer project and....I didn't really feel like explaining to baby fresh grads abt 'this thing reports time in Modified Julian Date' oh and this other thing uses Heliocentric Julian Date. Have fun my little never took physics b/c CS grads.
aug 30, 2025, 1:27 am • 3 0 • view
I'm not even writing the software and the amount of time I've spent discussing what is and is not TAI time...
aug 30, 2025, 1:29 am • 3 0 • view
Um. Yeah. I was _the_ developer writing algorithms for space traffic management and conjunction analysis services in house because _reasons_ . You can imagine the level of frazzled and months of not wearing hard pants as I sat in awkward ways in a chair coding.
aug 30, 2025, 1:37 am • 3 0 • view
Ugggggh. There's a reason my poor student at one point laughed at me when he got some code that was _clean.py. he thought clean meant I removed all the cursing...in comments about bad documentation and variables. It just meant I removed all the debugging print statements. 😬
aug 29, 2025, 11:42 pm • 7 0 • view
This is real SQL that I really wrote with the intention of putting it in a production environment, and I genuinely did not realize what I had done until I went back and read over it
aug 29, 2025, 11:51 pm • 3 0 • view
I once encountered an error message of "BAD ERROR FIX ME" in released commercial software, so until we top that we're doing ok
aug 30, 2025, 1:21 am • 8 2 • view
I accidently left an error code in a website that said "ERROR: pants!"
aug 30, 2025, 6:45 am • 0 0 • view