kryptonianCodeMonkey

Damn. You understood the assignment. Also, I was sure that story was going somewhere else horrifying.

So you're nostalgic for the Golden age? How old are you?

Least surprising news of the day

Actually, I just got it for free from my Playstation plus membership, one of this month's free downloads. Just wasn't sure if it was even worth my time

I never played it after the terrible reviews and after seeing the ugly busy ui/damage splatter. It especially hurt as a fan of the Rocksteady batman games and huge DC comics fan. Did the updates help? Is it better? Worth a play?

She was going to be talking anyway

There's certainly some reasonability to that. However, if the person decides to terminate service, maintaining the grid doesn't become any cheaper for the power company. The lines are already installed, the connections made, and the company will continue to upkeep your connection all the way up to your home, even if it is terminated locally. They'll do that just in case you or future homeowners no longer generate power and wish to continue service, and your neighbors will likely still be using it anyway. So by that same reasoning, maintaining a just-in-case service connection that you don't typically need because you generate your own power also doesn't result in increased maintenance costs to the power company. So there is also an argument to be made that that cost shouldn't be pushed to them, but to the power drawers that the power company actually wants to serve anyway, the ones motivating them to build more grid in the first place.

I test my own code/scripts in dev when I'm working on it. QA usually tests acceptance criteria in test environment. And then staging is used for production data testing for performance and identifying missed edge cases. Actually, we sometimes use dev and test interchangeably when multiple people are working on the same repo, so the lines are a little blurrier than that.

Same. Early on as a new dev, I failed to performance check my script (as did my qa tester) before it was released to production, and that was my first roll back ever. It was very unoptimized and incredibly slow under one of our highest density data streams. Felt like an idiot that I was good with it's 1-2 second execution time in the dev environment.

As a data engineer, testing with production loads is critical to performance checking, as well as finding edge cases where your assumptions about what can be expected in the data are curb stomped and send you back to the drawing board to cry and think about what you've done.

Alright, kinda funny. But don't clap back by meeting him at his level with petty renaming fights. It will just justify his stupidity in his mind and he'll rush to rename everything else that has Mexico in the name (or any Spanish for that matter) because that's the kind of 14 year old logic be works on. Then we'll be renaming cities, counties, and even states in an asinine display of "dominance". Instead, clap back by calling him a weird ineffectual manchild that wouldn't know dominance if it was rubbing its testicles across his spray-tanned wrinkled face and watch him squirm as he tries to figure out how to respond and ultimately lands on "No! You!"

Knock some of their teeth loose and they can do the whistling part themselves