afgrant

Unfortunate language/protocol name reusal. Watch out for these.

https://www.se.com/ww/en/download/document/998-2095-18-12-19...

“Required several coordinated actions” is the key moment for reflection.

Maybe they prioritized it low, assigned it to a group of 3 devs, and it functioned the first time they demoed it to management, so it shipped. All other devs would’ve been working on their in-house software.

I haven’t heard of a single software job in the last decade that offers anything resembling “training”. You sink or swim based on your previous knowledge, what you can glean from the codebase and coworkers, and how skilled you are at self-teaching.

Does Postgres no have online backup built in? All of the other major DBMSes do.

It’s the same as trying to tell everyone to stop buying gasoline for a day.

My phone is always with me when I drive and has a data connection that a car can tether to.

Everyone: Please stop using ‘#’ as an href placeholder. Don’t make your ‘<a>’ elements rely on events. If you want to replace their events with others, go for it. But please make them work at the base level.

If your MacBook battery is recent and lasting for less than 8 hours, you’re doing something very unusual.

When the encoding relies on differentiating between lowercase and capitalized characters, you’re hitting a high level of ambiguity. Hexadecimal UUIDs don’t have this problem.

128 bits versus 64 bits is a deal breaker?

It exists, but I wouldn’t call that “lucky”, or a selling point.

It’s just a 128-bit value that’s hexadecimal encoded. What can be controversial about that?

The hazard of base64 is the use of '+', '/', and '=' characters, which most HTTP engines treat as special.

Are there modern databases that can’t readily index on a 128-bit value?

It’s a sales pitch for base58 that I’m not buying at all. According to the code segment, they include numeral “1” but exclude lowercase “l”?

0-9 and a-f are unambiguous and widely understood. They’re more “human readable”.

Is this any better than the Wireshark database? https://www.wireshark.org/tools/oui-lookup.html

For the benefit of the future reader, I’m guessing you meant “CJS”, short for CommonJS.

Houses are tightly coupled to lives. Even if you escape the house, you might not survive the smoke inhalation from the surrounding trees.

The “unlicensed” aspect was never preventing this. Do you deny the basic benefits of end-to-end encryption?

I don’t get why you would conflate temperature degrees with angular degrees. They have nothing to do with each other.

If employees are getting paid salary, getting health insurance, getting retirement contributions, they’re by-and-large not going to quit

I’m in the same mindset. My 2009 MacBook got regular OS updates until 2017, then security updates until 2019. I replaced that one with an M1 Air and it’s been smooth sailing.

I’ve looked at my work from 7-8 years back and realized that it’s actually better. I’m not sure yet what this means.

… and Exxon, and Shell, and BP.

I would be interested in hearing of any instance where Firebase costs created financial hardship.

A minority of gas stations in the US use this system.

Are local weather conditions not generally available for all airports at all times?

In what nation?

The “lifetime of the hardware” is defined by the lifetime of the supporting software, which ultimately boils down to the popularity of the platform you’re on