Ask HN: Is there a name for the “rebuild it” phase of becoming an architect

[BasiliusCarver]

I went through it and I’ve seen others think the same. It’s where you think you know the best way to do something so the old software is just plain wrong and “needs to be completely rewritten” but you don’t really have enough context to understand the business cost vs reward of a rewrite.

  X axis == time  
  Y axis == confidence

  |    :     :     /
  |    : re- :   _/
  |   /:write:\_/
  | _/ : it! :
  |/___:_____:______

I feel like it sits somewhere in this but I’m sure there’s a better term https://en.wikipedia.org/wiki/Overconfidence_effect#Overestimation

Edit: I screwed up the ascii chart a couple of times...

[kstenerud]

I've always known it as the bulldozer phase.

Followed by the in-flight-engine-replacement phase.

Followed by the isolate-and-refactor phase.

Followed by the fuck-this-im-outta-here phase.

[tempxyz]

Yea, every time you inherit a project you didn't write.

[BasiliusCarver]

Love it when you do the “who wrote this” git blame and it was <myself@now-2y>