Hacker News Reader

Probably a case of “Logically this makes sense but let me branch and do it manually to make sure” and never got back to it.

I have code like that. A return then some body of sane looking but outcome unknown code.

View on HN

The old adage of "There is nothing more permanent than a temporary fix" comes to mind.

the PoC is production

I use `#####` as a sentinel for things that must not be committed, and have a git hook that checks my commits to ensure that marker is not present in the `+` side of a commit delta.

I feel like it's fine to commit and push that code to some non-master branch, and what really helps is a CI check to verify that code doesn't merge to master.

I use git to sync work between multiple computers, and I want to be able to sync work-in-progress code that should absolutely never see the light of day, so I feel like committing and pushing it to a WIP branch is fine.

Even if you only use one computer, I think it's a good idea to push these things so that if your HDD fails you can pick back up where you left off, even if it's code that's not ready to actually merge yet.

I try not to let code like that make it into git and into the wild. But this is a sane solution to prevent a very bad day.

Reply on news.ycombinator.com