

Real talk: I wish more orgs place a high value on QA. A good QA team is worth it’s weight in gold and helps prevent a lot of stupid mistakes.
Real talk: I wish more orgs place a high value on QA. A good QA team is worth it’s weight in gold and helps prevent a lot of stupid mistakes.
No good deed goes unpunished.
One time I worked on a team that had a ridiculously high defect rate. Stuff was constantly getting kicked back from QA. Management kept piling on all kinds of convoluted processes to try to reduce the number of defects which only made things worse.
I started really hammering the need for doing a root cause analysis as part of bug/defect tickets. Don’t just fix the bug. Make sure you understand what caused it and link the bug ticket to the ticket that caused it.
Big surprise (not really), 90% of the bugs and defects were being caused by like 3 people.
Your comment made me think of some of the PM’s whining about adding one story point for doing an RCA because apparently it’s better to just ignore the problem and keep pumping out shitty broken code as fast as possible.
Why are they spending billions on this?
Greed.
Remember when the Governor of Missouri tried to have a guy arrested for notifying the state of Missouri that they had a breach in one of the state websites, making peoples PII publicly visible?
That’s the kind of idiots you’re dealing with here. “We added you to a group chat by mistake and it’s all YOUR fault.”
Yes. Because they’ll store everything in MongoDB.
PO: “Why does it seem like it takes a really long time to develop new features?”
Dev: “I’m glad you asked! We’ve got this piece of code (points at smoldering pile of spaghetti) that literally has to be changed every time we do anything. The person who wrote it has been gone for like four years. No one knows how it works and it’s central to the entire application. I would estimate that this easily doubles the time it takes to work each ticket. I’ve created a set of stories to rewrite this code. We just need your approval to bring it into an upcoming sprint.”
PO: “Can’t… Hear… Breaking… Up… Bad connection…”
Dev: “Uhhh… This isn’t a Teams meeting. You’re sitting in the room with us right now.”
PO: …
Dev: “We know you’re still here even if you’re not moving.”
PO: …
Jokes on him. A lot of corporations will gladly tell Orange Julius whatever he wants to hear, true or not, as long as there’s a financial incentive to do so.
The US is currently shooting itself in the face and Russia is embroiled in a war that it can’t actually win.
All China has to do to reap the benefits is not interrupt.
Oh yeah. Fire the team responsible for pen testing. That’s real smart.
/S
Take a car that’s stuck in reverse, slap a 454 Chevy big block in it. You’ll have a car that still drives the wrong way; but faster.
In posts on X following the incident, Tesla CEO Elon Musk called the incidents “terrorism” and said the company “just makes electric cars and has done nothing to deserve these evil attacks.”
OK buddy.
Bet you $1,000 the credentials are stored in plain text.
My first thought when reading the OP was “Who the hell touches anything on a Friday evening? That sounds like a good way to end up working the entire weekend.”
My experience has been more like:
“We’ve scheduled the wedding. Not only have I not asked her out, but the [potential] bride is guaranteed to be completely turned off by the whole idea. I won’t know that because I’m not going to ask her opinion about anything until she ghosts me three weeks before the wedding.”
Pats top of Dell Optiplex
“Good boy.”
Since you’re already working in C#, an ASP.Net Core backed, with whatever database you prefer, will do what you want.
You could self host it, but I wouldn’t call that easy. There are plenty of cloud providers that can integrate with your preferred git repo and really streamline the build and deployment process. I run a few applications as “Apps” on Digital Ocean. Once you get it configured properly, deployments are quick and easy.
Mini split is currently in the backlog. It will be closed as “not planned” three years from now.
Something for poor people to worry about.
“Full Stack Dev” AKA Backend Dev who knows just enough about CSS to be dangerous.