4 ms·
Personally, I'd leave. I've never been good at trying to introduce those sorts of systemic cultural changes. My own experience is that those have either to co
by mgkimsal 16y ago
Personally, I'd leave. I've never been good at trying to introduce those sorts of systemic cultural changes. My own experience is that those have either to come from above, or be endorsed and supported by management. Without that support (or directive) efforts will fail, and you'll possibly upset people along the way (although you may upset them anyway).
As it is, if you choose to stay, you may ask for a definition of 'productive' that they're using against you. Is it lines of code? Time to get 'feature x' 'live'? Something else?
Once you have a definition, quantify the issues you're seeing - the number of bugs that are introduced by 'fast' developers is probably a prime candidate. Ask that bugs be documented - either over a short time period or just outstanding bugs everyone knows of.
Get everyone to understand that speed != quality, and that getting stuff done 'fast' is most likely a false economy. If you can get everyone or almost everyone to agree on some of those basics, you can then propose some new processes and measure the effect.
None of this will be quick, and it might not be adopted at all. But... I'd suggest documenting this dispassionately, no naming of names or pointing of fingers to specific people.
If you are having problems getting up to speed, anyone else probably would as well, so even if they decide to fire you, they won't get anyone else to be as productive. That's probably not actually true - it would depend on how they measure productivity. If it's just a matter of people throwing code out in to production without worrying whether it works or not, then yeah, someone else might be more productive than you. But it is a false economy over the long haul. Also, any new person coming in has a huge learning curve, because there's institutional knowledge gone by not having documentation, unit tests, etc.
If they really truly do not see that, it's probably better for your own sanity to find something else. But given the job situation, do what you can to make your case without stepping on anyone's toes.