concede_pluto

If writing code paid no better than flipping burgers, I would still do it, because I enjoy efficiently solving challenging algorithm problems. I don't enjoy failing to solve them because I'm continually being prevented from remembering something clever I just thought of. If I only get to spend a couple of hours in the zone where I belong, either I'm in the wrong role or the wrong industry.

I thought it was till, plant, harvest, and in between you just wait for nature to take its course. Do they have occasion to patrol a field with tractors more often than that?

There's nothing especially awful about left-pad being its own package, the disaster was because a huge number of developers were betting on npm to somehow be highly available (despite being donated by its admins at no cost and with no committed SLA) rather than vendoring their deps.

Unless they somehow withdrew money from it, it can only be underfunded because it was always underfunded.

Why nitrogen? Is air too corrosive?

>The thing is, one can write memory safe code in C.

One can generate safe C code. We have ample evidence that a human being can't sit down and write it.

For every car I ever owned before this year, they recommended an oil change every 3,000 miles (a little more than two months for me) or at most three months. I don't know if they got that much better or the recommendations were loosened to match observed problems.

> I have asked every person who has turned me down what I could do better.

I wouldn't say anything either. There's no upside. Why risk giving any kind of ammo to someone with a grievance they want to justify?

She says she's a frontend developer and a nerd, so why is she pigeonholing herself in these "digital content coordinator/content marketer" fad jobs instead of moving up from PHP?

If they aren't qualified to design with least privilege, what are they qualified for, beyond maybe cat videos?

There's an alarming list of behavior MySQL got negligently wrong at some point. That code is mostly still present (you can't prevent a client from enabling it!) and I have to assume some of the maintainers who thought it was reasonable are still involved.

And not everything on the list has a fix available. Off the top of my head, there are still broken storage engines that can't rollback, not all of them can be disabled, and STRICT_ALL_TABLES won't stop you from writing to them. Some foreign key constraints are supported while others are parsed and then silently ignored.

This. You don't want to reimplement all your validation in each of your applications (plural!), and you're in for a nasty surprise if you think your entire organization has only one application using your database now and forever.

There's a strange theory that banks and brokers had to be forced to reluctantly write bad loans, when in fact they were desperate to write more once they had a way to dump the risk on clueless speculators.