Mikey Clarke
1 min readNov 7, 2021

--

Argh. Ain't that the truth. I've just started working at a new company, which shall remain nameless. The more I learn about its systems and coding practices, the more I'm becoming resigned to it being one of those overly rushed places that produces sloppy, poorly written code, then spends the next months chasing "glitches" that never should have escaped into Production.

My current colleagues claim they're being "aggressive". Aggression itself I actually think is a good idea ... but there are a gazillion ways to implement aggression. Some are a hell of a lot more sloppy than others. Their specific implementation choices are very sloppy indeed. Their code bases are ... aah. Not the best. They have feeble test coverage, minimal docs, almost no comments, and the docs and comments that do exist are wrong half the time anyway.

It's a penny-wise-pound-foolish attitude. I've only been there about three months, but already toying with once more rolling the coding-shop dice, and yet again searching for a better job. That sucks, too, because this one pays really well.

--

--

Mikey Clarke
Mikey Clarke

Written by Mikey Clarke

Hi there! My snippets and postings here are either zeroth drafts from my larger novels, or web-app tutorials and other computery codey musings.

Responses (1)