π€ Ahh. If you’re in UAT you know what I’m talking about.
We’ve got devs who are diligent, conscientious and make sure their code works. π
And then we have those who… aren’t, and don’t. π
I get it I get it.
“But it’s so booooring to make sure there’s robust error trapping and it’s composable and well-architected yadda yadda yadda. I just want to BUILD you know?”
But IT NEEDS TO PASS QA.
I don’t give two monkeys ππ if you find it boring or not.
Sadly vibe coding amplifies this problem, because they don’t know what went wrong as they didn’t actually write the code.
AND AI kinda makes stuff up and kinda lies about it. π«
At the moment, TRUST is at a premium, and is the easiest way for you to get an edge over your competitors.
Do what you say you’re going to do.
Adopt excellence as a core value.
It pays to care about the work that you do and the people you serve.
Because people notice π…
When your code just works.
Or when it’s broken, and you’re able to figure out why and FIXIT. β€οΈ
πTrust.
πExcellence.
Be known for these two things, and you future will be pretty AI-proof.

