

That isn’t a bad thing. On the contrary, according to the open-closed principle, you should strive for writing code you never have to touch again.
That isn’t a bad thing. On the contrary, according to the open-closed principle, you should strive for writing code you never have to touch again.
Ah yes, the “fuck it, no-one is going to use this” code.
That image you linked requires authentication to download.
I think the homeowners are right regardless. You don’t need to be a genius to figure out that even a moderately higher population density increases transportation demand. Even doubling the density could affect traffic considerably.
Now before the haters come out: I’m not saying that the transportation demand must be addressed by more or bigger roads.
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).
I think it’s more accurate to say that water is readily available in places where humans are likely to go. Because, you know, humans don’t tend to go where there is no water.
I’ve never heard of an open sandwich [Edit: until now], but then again English isn’t my mother tongue. To me, a sandwich has always been food between two slices of bread.
Shouldn’t a sandwich have two halves of bread? There’s only one here. Canapés and Hors d’œvres are usually small, aren’t they? A Mettbrötchen takes several bites to eat and is usually eaten as a meal, not as a starter.
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.
Don’t they get their taste back when they reach room temperature again?
I hadn’t considered bureaucratic obstacles… that sucks.
Well, I commented that before I learned that OP is in New Mexico.
Have you noticed that there are now three ways to enter block-formatted, monospace text?