[capableweb]

You become a guru developer when you realise that judging any code based on any metric without knowing the full context is often misleading. Yes, in general removing code is good, but does that mean removing the full project and committing that is the best change you can do?

[jeffrallen]

You become a transcendental developer when you think "Bury it in the desert. Wear gloves." and are enlightened.

[tryauuum]

my system administrator background says yes, sometimes wiping the whole project is the best idea

Imagine that you are developing a storage with an s3-compatible API for internal use. Maybe you should give up and install CEPH instead

[capableweb]

Imagine you're developing a storage with S3-compatible API that is meant for public consumption, but you don't actually have something to store. Then yeah, bad idea to write some sort of storage system.

Point being, yes, of course you can come up with 1000s of examples where it's good/bad to delete all code. The point of my comment wasn't "It's never good to remove all code for a project" but rather "If this change is good or not depends on variables from outside the Git repository".