2 ms·
Skilled developers but unlistening management who didn't understand software development or how the software itself worked, coupled with proliferation of non-de
by 72deluxe 7y ago
Skilled developers but unlistening management who didn't understand software development or how the software itself worked, coupled with proliferation of non-developers taking the helm and dictating deadlines, "procedures" and illogical mandatory time-consuming processes where "designers" were separate to developers but didn't know how to write any code, leading to dead-end development that had to follow said mandatory illogical procedures. Dysfunctional testing "department" that didn't know how the software worked despite being there for a decade and relied on "technical support" for basic computer tasks relating to the software being written, eg add an ODBC connection. Lack of any formal technical designs, specifications or comprehensive documentation. Constant criticism of developers for taking time actually doing their job or wanting to improve things versus the spreadsheet army surrounding them. Minute micromanaging and justification of all time spent doing anything. Lock down of development machines because someone somewhere once ran a dodgy exe they were emailed. Code reviews involving sarcasm and belittlement. Most over-complicated code ever known to man with focus on prior optimisation (eg ordering of class members to stop any padding). A billion COM objects. Confusion that developers never ever stayed!
I went part-time elsewhere. Who cares if I earn less. At least I'm not shouted and sworn at all day any more. I do miss some of the devs though.