4 ms·
Here's some management issues OP might be referring to. - Who is going to provide support, bug fixes, documentation, manuals, etc? - What happens if you leave
by GartzenDeHaes 5y ago
Here's some management issues OP might be referring to.
- Who is going to provide support, bug fixes, documentation, manuals, etc?
- What happens if you leave? Can our other devs maintain this?
- Did I mention documentation?
- Did you get this approved by the architecture committee?
- Why didn't you follow our process improvement policy?
- We are a Java shop, so can you rewrite it in Java; you know this, so why didn't you write it Java?
There's also people issues with the other devs who may not like OP's tools or want to change their process.
- peterangular 5y agoHaving worked in an enterprise this list is 100% accurate. For better or worse (I think it's the latter) enterprises are all about coloring inside of the lines. If you color outside of the lines you may experience functional success in parallel to professional/social failure. Large orgs/enterprises aren't about solving the problem - it's about the ceremony around solving the problem expecting the problem to solve itself eventually. Going around that ceremony can/will be seen as "going rogue" and will often end in termination of some sort. If the company wants/needs someone outside of that ceremony they will likely go "hire a consultant" vs. trying to find solutions within the ranks. I'm not supporting this - I'm just saying it's how it is at the majority of larger companies that I've worked for/with. Honestly I think it sucks and stands in the way of real problem solving.
- mring33621 5y agoAgree 100%. Also, there are some very quotable things in your comment. "experience functional success in parallel to professional/social failure" is my favorite, though. Thank you! Source: I work at a huge bank.
- BatteryMountain 5y agoPerfectly spot on. It's not about being malicious/apathetic but rather the things you mention above.