Most likely a must watch.
@AmpCode and @pidotdev are pioneers to, instead of adding more and more features that could overbloat the harness just to prove that they can keep uptodate with the latest feature to make you a "100x engineer", remove features that they think are not necessary from first principles and have rightfully earned their place as part of the harness. And if a user deems something as important to them, they can just add their workflow as a flexible plugin.
Literally living the "best part is no part" principle.
So having insights on that thought process is something i am definitely interested in to really see what they deem the most important components in a coding harness.
I think most people underestimate the thought process and just pure fundamental knowledge and confidence that goes into removing features that people reason by anology think are useful.