This also has the added benefit of making a lot of money even by engineering standards in the right organization. Looks for large enterprise companies where custom demos and new customer hypercare are standard. I've been on the other side of the table a few times and often pre-sales cycles are months long and contracts start in the $2-4M range. Those are the places where sales engineers will be treated as first-class citizens and not just "hey grab one of the engineers for this sales call."

"Unmonitored transit" like the way almost every human being in the history of the world has moved from one place to another? Please.

You'd never had a discussion about firearms with the average person then. Good luck.

An 80% lower exists purely to comply with US gun laws. That's exactly why they're legal.

It depends on if you think private surveillance should exist to help the property owner in court, after something happens to them, e.g. the taxi driver getting robbed or the Waymo getting vandalized, or if you think private surveillance should exist solely to pipe any and all actual or imagined crimes to law enforcement in real time.

Private surveillance that immediately sends any and all crimes to law enforcement is indistinguishable from government surveillance and should treated the same way.

Don't worry we know you were alive in the 70s just from you including a hyphen in that emoticon (and everyone knows I was alive in the 90s because I said emoticon and not emoji) ;)

You're not responding to their point, though. If data centers were built only in poor areas because of classism, they're correct that there probably wouldn't be a lot of data centers in one of the richest areas in the country. And there are. So if you want to make a convincing argument that data centers are classist you should probably have a response to that beyond "well you just don't have any empathy."

You are not required to repeat uncited and likely incorrect suppositions.

Okay and where are yours or literally anyone else's citations in this thread? Because I don't see any citations on any other comments and every other explanation could be just as equally as wrong without them. Why don't you go reply with this to every comment here? I'm sure everyone will appreciate you for it.

Yours is the only one that is "I thought I heard once ${completely false thing}. I could be wrong though."

Wow, screw me for actually being honest, I guess. I'll remember to sound more authoritative next time so no one questions my statements rather than trying to honestly invite others to share additional clarifying information. Thanks! You're totally correct!

(Was that enough of an ego stroking for you? I can praise you more, if you'd like.)

It must be nice to work on such small-scale systems that you can reasonably expect PRs to be this quick.

I don't know it has as much to do with scale of the system vs the general architecture. E.g. the system I primarily work with these days has millions of lines but most PRs are for a small changes which are well contained in scope by the overall architecture.

It's a cultural thing, but you can do incremental PRs towards a large goal. Giant PRs that are expected to be reviewed never really seemed worth it imho.

I don't think a PR needs to be tens of thousands of lines for a review to take more than 20 minutes. I've worked on projects where you can't reasonably get a branch set up and running somewhere to test it within 20 minutes if you need to set up dependencies, peripherals, external systems, etc.

reasonably you should already know what the code and project is supposed to do before they even start writing code, so you can get directional feedback in.

then you are maybe reviewing 1 out of 7 PRs that implement the agreed upon change