3 ms·
This approach is what creates technical debt. It's a method useful for startups only. Businesses who have moved on from startup status need to switch to a qua
by lugg 7y ago
This approach is what creates technical debt.
It's a method useful for startups only.
Businesses who have moved on from startup status need to switch to a quality first approach.
Deprecation should only be on the table if your original design was flawed. And then only if you are certain you are fixing that particular design flaw completely. So many times have I seen rewrites due to a poor design just create the same design flaw in the new system as a compromise because changing the database would be too hard.
And even then, I strongly question the need for isolation/deprecation like this. It says a lot about your company and creates a broken windows atmosphere where it's ok to push shit because it will eventually be replaced anyway.
"Wanting typescript" is a shitty excuse for putting a business critical system up for adoption.
Literally nobody will want to deal with it within a year. After that, your business critical function, likely one that makes money, is no longer maintained and impossible to change.
Enjoy your growth stagnation.
- seveibar 7y agothere are several good reasons to isolate and deprecate 1) web technologies change frequently, junk is accumulated over time if new tooling and updated dependencies aren't adopted- this is more effective in deprecation 2) iteration speed is faster ultimately code that makes up infrastructure or the foundation of micro*s should be quality first (e.g. auth, kubernetes, microfrontend compositor) but other things should focus on shipping and iteration.
- vikingcaffiene 7y agoWhy don't you ask a couple follow up questions about the situation before you slide into the comments and deliver judgement on a something you know nothing about? > It's a method useful for startups only. this is a start up. So yes it's useful. > Deprecation should only be on the table if your original design was flawed. It was. > It says a lot about your company and creates a broken windows atmosphere It says a lot about what kind of person you are to come at me with a statement like this. The entire reason this approach is being done is to deal with broken windows genius. > "Wanting typescript" is a shitty excuse for putting a business critical system up for adoption TS is one of many changes we are adding to deal with the "broken windows" you so snidely commented right before delivering this one. Isolating the part that makes this shift impossible without a lengthy and expensive re-write is absolute the right approach as we can continue delivering features, address tech debt, and leverage this critical piece of software until we can migrate it to the new infrastructure. > Enjoy your growth stagnation. Enjoy being a smug asshole.
- rumanator 7y agoYou're reading too much (and filling in the blanks with your assumptions and imagination) from a honest and objective comment from a fellow regarding his personal experience. I'm glad he shared his experience with us, but your post only adds noise to an otherwise interesting discussion.