341 karma · joined March 6, 2022
I think we're going to find the opposite in a few years.
Sure I guess it's technically avoiding rot by updating but the fact I don't need to touch it makes the point moot.
> Fwiw, and I know this is a nitpick, but anything built purely on open source libraries should be technically buildable forever. Especially if you keep it local (e.g. cached node_modules for npm)
Technically isn't very useful when my server needs to update npm/node for security reasons.
Large parts of the web are powered by npm.
The vast majority of those sites, if not actively developed, will not be able to build within a year's time.
I'd be curious to know if the defect remains while stirring until frozen.
I'm shocked.
FWIW, the majority of things on that list aren't what I'd consider covered by any auth library I know of.
It's mostly people just not using their authentication, diy or not.
Crypto is the thing I won't touch with a ten foot pole.
When I said backend above I meant company backend / API / services.
The rest of us just don't have that many files to refactor when we change things.
I don't really hate ide's, I get the appeal, and sometimes it works out useful. It's just that most of the time it comes back to enterprisey software being the source of your problems, not the lack of features in your editor.
Fix your linter and autoformatter.
You don't pay me to lint code.
My trick is to write the wtf in pending review then go and look later in the day if it's still valid. Often I just needed to eat something and I'll be over it.
The funny part was that they linked to it and called it a coding test.
Why does everyone forget Yemen?
Is it because it's the Saudis again? Or is it because Obama did it? Or because Trump continued it? Or is it because Biden said he would end it but didn't?
https://youtube.com/watch?v=hFkngrRDdaA
Inflammatory comment I know. Tell that to the 100s of thousands being genocided.
The true DevOps.
That code in 2005 was better in every way.
Context: just learning loopback API framework. What a steaming pile of overengineered garbage.
I'm assuming you mean your comment, not the post itself.
> The reason that you need to do things the ops way is because ops knows how to run applications in production
Stability in production is one metric. Ops overindexing on this metric is exactly what causes the friction with developers.
Developers are trying to ship value to customers.
Uptime is only one part of that equation and for most businesses, it's not even a very important one.
The author points this out near the end. DevOps can't convince devs to use ops techniques if all the reasons for using those techniques are based on the flawed assumption that development velocity isn't important.
Can't exactly tell whether it was better before or now.
The discipline policies were pushed by the race training.
Because from what I see he's both called Intel on it's bullshit and still worked with them on a professional level.
Same for amd.
As for apple, they funded a whole new Apple channel without Linus precisely because he knows he couldn't be unbias.
It's kind of rediculous to claim he's a fanboy in one sentence then claim he's just a shill in the next when the evidence contradicts your first statement.
When the government gets involved.
Till then, build your own internet backbone or get back in line.
Fwiw, I don't agree with this but net neutrality died a while ago. Both the left and right political movements have had ample opportunity to fix this problem but they've made their bed. Now they get to lie in it.