Hacker News Reader

I code like this. It wasn't always the case, but at some point I had the realization that everything I do can be undone, reset, restarted, or otherwise restored and no longer have any fear about digging in and utterly gutting a piece of code if I can imagine a way to make it better.

This philosophy now has a name - and I like it.

View on HN

"everything I do can be undone, reset, restarted, or otherwise restored"

This is so key.

Software companies in general need to emphasise this so that builds are easy, CI is a given and continuous deploys are a no-brainer.

> This philosophy now has a name

I worked with someone who went into what he called "samurai coder" mode. He'd get his digital sword out and start chopping up the enemy (bad code). We were in an environment where everything could be undone, reset, restarted, or otherwise restored, so his swordplay worked.

Reply on news.ycombinator.com