18

Any one else’s kinda enjoy the process of removing tech debt? always thought it felt good to rip out old shit to put in shiny new shit

Comments
  • 1
    Better would be to rewrite the whole thing and use the correct tech directly.

    Saves a lot of work later on.
  • 4
    Yeah. I have written 17 functions for 17 different type of messages, where code was 95% same. Then my friend taught me how to use enum with struct-like types in Rust.

    260 line of code, gone. Reduced to the atoms. I used Rust to destroy Rust code. Never going to be rewritten.
  • 3
    Depends of the bolognese level of spaghetti.

    I once refactored just one component and fucked up totally unrelated screens on the app. For example, I refactored items table on cart and fucked up account settings loading screen.

    Took me 4 days to detangle that shit!
  • 1
    @max19931 trying to do things perfect from the start gets you nowhere. It's part of why agile is so popular. Most of the times you don't know enough beforehand. Also your and your team's skills improve as do the tools.
    Our service has an input method that was used for initial load and later thought for adding more bulk changes. As It turns out we have now a better way to add bulk changes. So in less than a year the whole input method is obsolete. Without it though we would not have a live service...
Add Comment