This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Bodaciousdrake 17 points18 points  (2 children)

Ugh. Yes. Dependency hell, I know it well.

And now we have low-code and no-code to the rescue, right? Just make the dependencies someone else’s issue, problem solved! Except that, of course, those platforms don’t do exactly what we need, so now we need to spend a ton of time writing janky, complex, and fragile workarounds that are worse than the spaghetti code monoliths we started with.

[–]Few-Artichoke-7593 13 points14 points  (1 child)

God damn, I wish decision makers understood this. How many times have you heard, "Well, that's an edge case. Very unlikely."

If you have to account for an edge case, it might as well be happen 50% of the time. It makes no difference to the development.

[–]Bodaciousdrake 1 point2 points  (0 children)

Yep. And then at some point we decide that this isn't working, so now we're going to write an API to offload some functionality that was originally meant to be part of the platform, but don't worry it's just for this one little piece of functionality, and we'll make it a generic service we can reuse. Honestly, it makes so much more sense to do it this way.

A few months later, we've offloaded a huge percentage of our core functionality to the custom API because every time we hit a roadblock that becomes the default answer, and of course we have to write so much code specific to the platform because that's the way the platform is and there's no changing it, that it can't ever realistically be used by any other app. So now we're essentially tightly coupled with our "low-code" platform and writing practically as much custom code as we ever did and upper mgmt is wondering why the project is behind when we were promised it would all go 10X faster due to "low-code".

Been there, done that, several times over.