Look at the last table in my original post. It contains 26 columns (A–Z), some of which are not shown, and 27 rows (blank–Z). There are 27 rows and 26 columns, regardless of the contents of the table. If the top-left cell (A, blank) were a 1 and (B, blank) were a 2, then (Z, blank) would contain a 26, and ZZ would contain a 702. Nothing about the layout of that table changes.
To summarize: The table will always be lopsided, if you start counting at 0 or at 1.
Like every name in IT in the last 10 years.
“Windows App”
“Rust”
<every goddamn hot beverage>
The argument stays the same. Only every index gets incremented.
And don’t forget that 1900 still is a leap year in Excel.
Thank you! Saying this finally made me realize why I always need to add/subtract one day when I’m trying to convert dates to and from the Excel representation. 🤦
I have been able to outsource low level parsing to third party libraries
Today I watched a Java server crash because a library decided it needed more than 3GB of heap space to read a 10MB file. That was after manually removed background colors from around 100,000 cells, which apparently caused the parser to create even more objects in its internal representation of the sheet.
I thought about that, but decided to leave it as an exercise for the reader.
Don’t forget that Integer8 (the middle dragon) counts increments of 100 nanoseconds, because… reasons.
And don’t forget that 1900 still is a leap year in Excel.
But does it really make less sense to say “a string slice”?
That’s an interesting point. You say “a pizza slice” or “a slice of pizza”, but you only say “a slice of bread”, not “a bread slice” (right? I’m not a native speaker).
Program sucks at something it was not designed to do.
surprisedpikachu.gif
The requirements have always been the same. Only now they’re reflected more accurately in your docs.
That sounds like something that would be apparent from the get-go, no?
The key is to not reassign function names to local variables.
const print = obj.toString
print() // gives you a bad time
These indicators help in troubleshooting. If the indicator says the device should be swiveling, but doesn’t swivel, you know it’s broken. If there’s no indicator, you might think you’re just too stupid to put it in swiveling mode.
Old-fashioned switches, of course, solved this problem without LEDs.
Someone on the design team heard that squircles are the latest shit and put zero thought into implementing them.
Doesn’t matter if the mechanism that checks the repo and sends the trigger message to the runner is down.
The fewer magic blackboxes are around, the
I marvel at the proficiency with which Microsoft tears down every piece of software it touches nowadays.
Sending “temporary” changes into your CI pipeline isn’t even stupid, it’s borderline malicious.
No? “Hey customer, I’ve deployed the changes you requested to the staging area. Is this what you had in mind? Keep in mind it only looks good and isn’t fully functional yet.”
That means that the HR account thinks what the employee account wrote is bad, too. Both posts are bad extremes.
As an employee, if i find a prospective colleague who doesn’t ask about what they’re supposed to be doing at all, I’d be wary of them, too.
Massive disrespect for not learning a thing.