I’m in leadership at a place where we ship software to hundreds of millions of devices every other week and sure, it sucks to maintain legacy products, but you never sunset something without one hell of a grace period and plenty of warning. And not without feature parity if you’re rewriting to escape tech debt.
There isn’t a valid excuse. They brought this upon themselves and their users knowingly and if they did it without knowing the consequences, that’s even more alarming.
Ship a new app then. Sonos already do this for older products.
Whoever the fuck thought a massive regression for every single customer was the perfect thing to deploy with no option for rollback needs to stop working in software.
Internet Archive has your back
Two things come to mind:
-
Do we need compliance regulations on minimum testing infrastructure etc for kernel-level development so that dangerous bugs can’t be mistakenly released?
-
Kurtz has a history of this calibre of issue under their leadership (both at CrowdStrike and at McAfee); why does this keep happening under their leadership and what can we learn to instruct other orgs not to make the same mistakes (e.g. via CISA directives)?
The Brenaissance continues!
If you just want geo coordinates, you could use any open source app and copy+paste them into a note or something.
Gosh that’s awful and I’m so sorry for you.
If you’re into gaming, this entire channel is full of hilarity.
80 world-class engineers sounds like more than enough people. It’s not like Valve struggle to acquire talent and are thus forced to have teams and teams of juniors who are masters at building tech debt.
Valve will likely be hiring and retaining the kinds of engineers who love a good refactor and appreciate the time and space to do that rather than some product manager pressuring for the next shiny shit they wanted yesterday.
And Steam is their money printing machine that keeps them free to do whatever they want. It’s no surprise their team have stayed invested in continuing to build out the best gaming platform of all time.
80 talented, passionate, and healthily paid engineers > 800 junior, sleep deprived, and struggling to buy groceries “coders”.
Fucking finally.
Supposedly the predecessors to the ancient Greeks mistook the skull of a breed of small elephants as the skull of a one-eyed giant.
No ash or dark fumes emitted - I assume did something clever underground to capture or filter it. But plenty of steam billowed out of the cooling tower. During cooler parts of the year, the steam would freeze and turn into snow which was a lot of fun to go and have a snowball fight in late autumn.
But then again, I’m possibly just blissfully ignorant and lung cancer will get me any day now.
Whilst it’s nowhere near as big of a contributing factor as those mentioned above, the election was also called during the time of year the largest number of people are holidaying.
Fully agree. People travel for thousands of miles to see the windmills in the Netherlands. They’re no different and the beautiful white and curved designs makes them look like a true wonder of modern engineering achievement.
Fuck yes. I live very close to a wind farm and can see them from my window. They’re marvels and, alongside the several local solar farms too, it’s such a positive feeling knowing that, regardless of the weather, clean energy is being created.
I know plenty oppose these things but having grown up next to a coal power plant, I’ll take a stunning wind turbine any day over those giant cooling tower monstrosities.
You’re right. They’re terms far older than web development. In general the front is the abstraction while the back is the logic/processing. It started as a term for old, large (room-sized) systems where there were front-end machines such as plugboards or terminals, with back-end machines being the CPUs, memory, etc.
Conway’s Law applies in this respect; the mess in governance of Nix has produced a product that reflects that mess. Nix started a beautiful movement but like many first movers, they rarely reap long-term rewards.