52

What's your story when you had to scrape your code, for the better, when you went working for days and had to remove it all?

Comments
  • 2
    I've had to toss out an entire ecosystem from frustration but that's a story for another day. ;P

    This month alone I dumped most of my experience of Java EE to move to Spring/Hibernate in the hopes of an easier to use framework. I was right.

    ....Guess I don't dump code as much as entire projects. Code is salvageable at the end of the day.
  • 7
    Many great devs will tell you the best and most satisfying commits are those that delete hundreds of lines of code
  • 2
    My current project git repo stats looks like a horizontal vase.. each push i delete a few hundreds lines of code and write another few hunders in place.. i felt a little bad about this for a while, but i am starting to see the fact that i'm not standing in place, i just focus on perfecting what i have done previously.

    I think it's an important mindset to focus on perfecting code rather than simply add more
  • 0
    This should in fairness be used in the rarest of rare cases.

    99% of the time, it's easier to fix one mistake at a time and clean it up, rather than throw it out and rewrite, raining introduction of new bugs.
  • 0
    Truuuee. Some of my team members hate me for removing their code sometimes [ after asking them to change]. They don't see the bigger picture. 🤷🏻‍♀️
  • 0
    A competitors code?

    Then, yes.
Add Comment