newobj

Timescale is a relative measure.

Sure, public jobs program, or sell it. In case you can't tell my comment is hyperbolic, but I feel like we should start at a point of hyperbole and move backwards to reality instead of what's happening right now: fuck all, on a geological time scale.

An ordered list of officers of the company who go to jail depending on how many years must be served as determined by sentencing. Assume something like 10 years per person. If it's 300 years of sentencing, then 30 people. If the sentence exceeds the list of people, the company is nationalized. (And everybody goes to jail.)

Whatever it takes to sleep at night man

"Oops the computer did the war crime"

I'll ask again, who's going to jail?

Ok, that's a crime then, right? So who's getting charged?

What? They were still asking these Mt Fuji ass questions in 2016??

Came here to ask about this too. I was doing CSG stuff in the early 2000's and got physically and mentally sick from the pure hell that floating point accuracy created for me. Literally led me to quit my job. Full crashout. iykyk

They're still a thing

if you get into a config system that's complicated enough, and has modularization or inheritance, you'll know that the semantics of "remove this" "add that", override this, default to this, this stuff is hard to express in most config languages, or worse, you start enforcing application level semantics. when you have turing complete language you just ... do those things. we reduced the configuration data of a tool suite once by 90%+ by moving from json to python. there was a tremendous amount of duplication and overlap, with tons of TINY exceptions and variations. it was so hard to see those differences, brittle to maintain, things would get stale, ... moving to python you basically had the "base" thing expressed in one file, and a bunch of tiny delta files encoding the exact deviations. All those deviations were of the forms I described above. Adding a thing to a list. Removing a thign from a list. Overriding a whole list. Do a thing if not already done. And so on. It's also then easy to build all kinds of diagnostics, validators, etc, right into the same framework, without having to munge the data into some other form first.

God bless you

Interesting variation on the "I cut you choose" game mechanic!

that may have been true in product orgs but the infra and dev infra orgs were pretty strong imho.

Google is historically terrible as a product company (and has succeeded in spite of that) As their technical innovations become less of a moat (we're already there) they won't be able to win on engineering alone (they are no longer winning on engineering alone)