thisago's blog


As if it was faded to a bloat collapse instead maturity

How can we avoid refactors and the apparently inevitable health decrease in a codebase with time?

This is frustrating. Something is missing.

How does big techs handles this issue? Do they really solve with a real solution, or with more money being invested?

It seems that software lifecycle is too small, and it's mandatory to run in circles.

As if the timeline of most of softwares ends in a bloat collapse instead progressive maturity.

For sure, there's more to learn.