Australis13

This is one case where I think Windows is appropriately designed for its target audience.

We work in protoduction.

Nope, just inherited a colleague’s codebase when they left. It’s years later and I still haven’t sorted it all out.

As someone who has inherited code like that, I would like to strangle the first programmer in the comic.

Make sure it’s not whitespace sensitive and requires explicit typing, just to mess with everyone.

Ouch.

I have actually encountered those sort of potential differences between ground planes. They can indeed wreak havoc under the right circumstances.

Indeed! Covers most of the instances where I would otherwise have to use find.

I can’t decide whether to laugh or cry.

I think it’s just that we’re possessive/protective of “our” code, even more so if one is passionate about programming. We’ve put a lot of effort into it, then somebody else comes along and “ruins” our “perfect” (to our eyes) formatting/styling!

Some linters can do both. Getting one set up as an automated job whenever code is pushed to the repo is on my TODO list…

I felt that. I have a colleague whose coding style is different to mine and whenever they work on code that I originally wrote, I have to resist the temptation to modify things to camelCase.

Thanks for that. A very interesting read; I am inclined to believe the author, given how they describe the failure of processes.

Indeed. I’d hardly classify this as going “rogue”; rather, inadequate guard rails in place for this application.

The browser addon “AdNauseum” can help with that, although it’s not a complete solution.

Ugh. If I need to collaborate with my colleagues, I’ll visit their office; I don’t need (or want) to hear every phone call they make or their music escaping their headphones.

I cannot stress enough how much I hate open plan offices and am so glad I do not work in one.

That is better than a fuselage failure, but still disturbing if you’re correct - surely there are checks for exit door plugs since it would be at higher risk of failure.

Multiple news articles are reporting that this aircraft had its post-production certification only two months ago. For a problem of this magnitude to develop in such a short time is very disconcerting.

Huh? What does how a drive size is measured affect the available address space used at all? Drives are broken up into blocks, and each block is addressable.

Sorry, I probably wasn’t clear. You’re right that the units don’t affect how the address space is used. My peeve is that because of marketing targeting nice round numbers, you end up with (for example) a 250GB drive that does not use the full address space available (since you necessarily have to address to up 256GiB). If the units had been consistent from the get-go, then I suspect the average drive would have just a bit more usable space available by default.

My comment re wear-levelling was more to suggest that I didn’t think the unused address space (in my example of 250GB vs 256GiB) could be excused by saying it was taken up by spare sectors.

Of course. The thing is, though, that if the units had been consistent to begin with, there wouldn’t be anywhere near as much confusion. Most people would just accept MiB, GiB, etc. as the units on their storage devices. People already accept weird values for DVDs (~4.37GiB / 4.7GB), so if we had to use SI units then a 256GiB drive could be marketed as a ~275GB drive (obviously with the non-rounded value in the fine print, e.g. “Usable space approx. 274.8GB”).