4 ms·
One big issue I have (and I'm trying various solutions around it) is code upgrade. Let's say we are doing something one way - step 0, and we realize "hey, gues
by sonaltr 8y ago
One big issue I have (and I'm trying various solutions around it) is code upgrade.
Let's say we are doing something one way - step 0, and we realize "hey, guess what' there's a better way" - let's call it step 1). Now going forward all new code is step 1, and touches to old code is step 0. Later you realize - there's an even better way - let's call this step 2. Now going forward you have step 2, step 1 and step 0. This process continues - but people who worked on this leave - leading to technical debt. This carries on for a few iterations and now you are on step 50 (49, 48, ...).
I have no idea how to deal with this problem.
I personally feel more micro-services would be better - but I also don't want to jump the gun since we were not too big a company at that point (and being profitable with our runaway took all priority)
- bradstewart 8y agoIt's a hard problem to deal with. I try to make sure the "better" way is "better enough" to warrant a change, knowing the technical debt that will ensue.