WhatsApp for business communications? Jesus
Whatapp is for business, and signal is for official government communication
Both are quite secure but neither of them stop an idiot on one end or the other from sharing the contents with the public.
I have been thinking about this and there are 4 messages I could receive that would illicit a similar response. I would ask if the system is down and if it is up, I have 2 people that would be forced to take the day off. Mainly because they never read any documentation throughly and can’t follow instructions.
“good morning, I’m about to destroy the backend” is exactly the energy I’d welcome from a colleague frankly.
I think the outage that followed as we fumbled to replace it would probably be cheaper than the ongoing maintenance after a few months
I’ve seen plenty of back ends that needed to be destroyed.
nsfw Kenneth Williams
Are we still talking about code?
Wait, you guys were talking about code?
Amen…
Used properly, repairing pretty much anything with a sledgehammer will ensure it’ll never break again.
In my last job we called that “optimizing”, after a colleague (who usually only did frontent work) used the opportunity when everyone else was on vacation to implement a few show-stopping bugs in the backend and put “optimized backend code” in the commit message. He did the same thing a few months later during the next vacation period, which really solidified the joke.
Worked with a guy that would always say I’m refactoring X and it would usually give us weird issues and bugs. So after a while the team started calling it refucktoring
Do it and I destroy your backend.
Have you dropping tables like you’re Mankind in 1999.
Sick reference
Out of control.
Narrator: The deployment proved that it wasn’t a typo after all.
What is this magical job where two typos land you a day off, no questions asked?
Tech CEO
A typo in software development or other shell based work could completely ass womp a system in ways that could lose a company lots of money.
Oopsies on prod systems, even with an outage window, can really fuck shit up. Seemingly small mistakes can quickly snowball into systemwide outages.
It’s wild to me how some places I’ve worked are like locked down, all the infrastructure is in terraform or whatever and can be deployed immediately… and other places are like “ssh into prod with the credentials from confluence, edit the config in vim, and paste the new code into a new file”
One of those is Amazon prior to chatgpt, the other is Amazon a few weeks back.
Confused the “deploy to PROD” with “deploy to staging” again huh?
Oh, look at Mr Many Environments here, he’s too good to test on prod like the rest of us do.
Every groups have a “testing”. Some also have a “production”.
Well, I have 2 testings!
One short term and the other, long term.
