3 ms·
It really boils down to this: if it ain’t broke, don’t fix it. If it is broken, and no one else seems to see that it’s broken, then it’s your job to convince e
by jmole 5y ago
It really boils down to this: if it ain’t broke, don’t fix it.
If it is broken, and no one else seems to see that it’s broken, then it’s your job to convince everyone else that it’s broken so that “fixing it” becomes part of the The Goal.
- Aqueous 5y agoThough this can also backfire. I observed a huge architecture error in the central data structure / schema of our system. Everyone agreed that it was a huge problem so I got put in charge of fixing it. Of course when you build an entire system around a bad schema, it gets baked through every inch of that system. Over a year later and it’s mostly fixed, but my career has stalled and I took the major hit to fix it.