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?

On some crops yes, you spray all kinds of things after plating. On other crops you don't dare passing a tractor around them, else they would be ruined.

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.

Vendoring thousands of tiny libs is even worse. Trusting many lesser known, tiny libs is more risky than few, big well known ones.

Also, they are not vetted and there are much more opportunities for an attacker to sneak in a backdoored lib on the edge of the dependency graph.

Finally, due to vendoring there's no way to receive timely drop-in security fixes for all dependencies from a trusted source.

One can both vendor and use the package manager to fetch updates. Just add the node-modules directory to your VCS.

The thing with node is that AFAIK it requires you to have libraries for what in most languages would be in the standard library. Maybe someone should start a "stdnode" project where the most popular / successful libraries for generic tasks are integrated into a dependable, maintained de-facto standard library, with an eye on quality and sanity, and community / Joyent funding.

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.

Well, even seasoned devs admit that writing memory safe C is always a tough task. But sometimes when you have 512kB of memory, you are bound to make some memory acrobatics.

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.

Most modern cars can/do use fully synthetic oil, which can last ~10k+ miles.

2013 or newer yes, but anything older it's recommended ever 3000 or less.

Kinda. The difference between this and twincharging is that the supercharger is spooled by a belt driven by the crankshaft rather than an electric motor. This means that the rotational speed of the turbine (and therefore boost pressure) is proportionate to the current engine speed whereas a 48v electric motor can spool the turbo to 30,000RPM and provide full boost pressure at any engine speed.

Anonymous strangers successfully handled the crowdfunding: https://arstechnica.com/information-technology/2014/09/fans-...

> 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?

It's anecdata, and I'm sure it's regional, but around me, there's vastly more "digital content marketing" jobs than development jobs (front or backend, much to my chagrin).