4 ms·
I've heard the phrase "never invented here" syndrome, but that doesn't seem to be what you're getting at. That term refers to a kind of disfunction where peopl
by geebee 10y ago
I've heard the phrase "never invented here" syndrome, but that doesn't seem to be what you're getting at. That term refers to a kind of disfunction where people are so terrified to the NIH syndrome that they'll shoehorn into an existing application, no matter how much contortion is required, simply to avoid developing their own code base.
- mmsimanga 10y agoThat is an interesting angle. Part of my problem is that I work in a huge corporate company that has been around around a while so has quite a number of legacy systems. I am loathe to introduce new layers of complexity and that does sound like "never invented here" as you describe it.
- phhlho 10y agoI would agree that adding a new layer of complexity is to no one's advantage. A strangler application that becomes symbiotic with it's host can be a terrible thing. I think the key angle to always consider: how will this new thing reduce overall complexity, now or over time? Maybe it means biting off a smaller chunk of the problem then you would like to keep the overall system sane. Or on the flip-side, keeping the new thing under wraps longer and running it in parallel with so you can thoroughly vet it before attempting to replace it. And sometimes, you just have to decide that you won't be the person to try to 'repair' an application, particularly an old and stable one. Make the point change necessary for your need, call it a day and look for better opportunities elsewhere within the environment.