The big banks launder far too much Mexican drug money to allow that to happen.

Is an object with no external links to it truly online? Is it offline? Is it in a superposition of online and offline?

The mind boggles.

I'm guessing they're happy selling cider and don't have any interest or expertise in servicing computers.

A parking brake on an automatic and a handbrake on a manual are not built the same.

At any rate, at those speeds, the handbrake probably wouldn't have helped much.

assert should be compiled away in production code. :-)

And yet, unchecked input is the root of almost all software vulnerabilities

Except for the causal loop.

Personally, I liked 12 Monkeys.

All I know is that I'm still waiting for my goddamn hover board!

As long as he doesn't create an alternate universe where Greedo shot first, Vader made C3P0, the Force-sensitivity is a bacterial infection, and force-ghosts got 20 years younger, we should be just fine.

Right... polar bears it is then!

Still no sign of oil. What a f*ckin waste!

I don't see a lot of games released here in which you get to play a Pakistani agent conducting ops in the states.

The question presumes that developers are choosing to write crappy code and just need to be convinced to write good code. That's silly. Either they're capable of writing good code and want to, or they're not. If you have to convince people to write good code, then you have poor developers.

That's not to say there aren't external factors that degrade the maintainability and robustness of the code, and the questioner suggests things are rushed to get stuff out of the door.

You can try to get management's agreement to terms regarding technical debt (that is, that time will be given post-release to deal with technical debt). If this cannot be agreed to, or the managers reneg on an agreement, then you can just start estimating your work upfront taking into account (a) the effort it'll take to do things with minimal technical debt, and (b) the refactoring of existing crud that you'll need to do in whatever areas you'll have to work with.

Things like improving new team mber ramp up time are fuzzy and speculative. If you can make the improvements you want, then you can look back to see how those improve. Gather that data so you can advocate for more changes with some data to back your arguments, including the value to the company in saved hours, increased turnaround time (after the initial investments for undoing the crap that's already there).

Above all, prepare to go the extra mile to do the sorts of refactoring you want to do, including spendig long hours. If you're not motivated to do that, then you should ask yourself if you really care enough about the product/company to make that level of personal investment. If not, then learn to coast by their standards, or seek another team/company that provides the work environment you're looking for.

That makes up for me stalking their aisles for products and then buying them online for cheaper.

Yes, the early 80s, when the big issue was what time it was in America.