

It’s an answer 🏴☠️
It’s an answer 🏴☠️
Getting too much money reaaaaally fucks with your head. Becoming a billionaire should count as a brain injury.
My exit condition is when the stack overflows
Javascript should say “you are a masochist and a nerd”
Company holidays mean you’re lazy? Bro needs to get a grip.
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.
Gotta get the kids started on associating themselves with our brand now. Subvert the competition asap.
No that’s not how LinkedIn works. If a job lists specific qualification tags like that, it marks those tags with symbols and colors them red or green to indicate if your LinkedIn profile has those qualifications listed. Those can be education requirements, certifications, skills, etc. That tag shows that their profile doesn’t have a bachelor’s degree listed.
Salmonella is eliminated at 165F. Cookies get to around 190-205F when fully baked. So there’s at least 25 degrees Fahrenheit between completely safe from salmonella and fully baked cookies.
I often prefer slightly undercooked baked goods.
I took a principles of programming languages course a while back and got to touch on a lot of these old languages. My professor had huge hard-on for Lisp. Don’t get me wrong. The simplicity of the language is admirable. But reading and parsing that shit gave me headaches. No me gusta.
Serving multiple data streams
200: “I gotchu, bro. Here you go. Have a good day.”
401: “You’re not on the list. Get lost.”
402: “Pay me or get lost.”
403: “Everyone get lost.”
404: “You are lost.”
500: “Ooopsss.”
501: “Knew I forgot something…”
504: “I can’t do this shit all day.”
A bit in Freedom units is 2 metric bits because it wouldn’t be freedom units without unnecessary confusion. A metric bit is equivalent to a freedom unit lil’bit, because it’s smaller than a bit. A bite (no relation to a byte) is 25 lil’bits because saying 25 ones and zeros outload is a mouthful. A hot dog is 4.2 bites or 105 lil’bits because that’s how many bites it takes me to eat a hot dog. A hamburger is 6.4 bites because it takes more bites to eat. A double with cheese is 7.8 bites. A whole hog is 233 hot dogs. A stampede is 23146 hamburgers.
My Scrum Master is nice, but her role seems to mostly revolve around enforcing documentation standards, coordinating refinements and retrospectives, tracking metrics on task completion, and maintaining our Jira board. She doesn’t have a lot of involvement with the specifics of development, delegation, or how we execute our tasks.
You can really see the “made in China” on the costumes