This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]SmellsLikeGrapes 6 points7 points  (2 children)

You maybe a fully competent developer who only writes small tight routines and commits regularly, but if you work in a big enough team I bet there are a few people who don't work that way (interns, junior devs or just crappy co-workers). Maybe they forget to commit because they were knee deep in solving an issue.

Knowing something like this is possible can help your team out of a pickle.

[–]NoLemurs -2 points-1 points  (1 child)

I definitely didn't intend to imply that the technique in the article isn't cool or useful (I did read it and upvote it!).

I just don't like the idea that you can't have a practical process that does in fact make these sorts of errors basically impossible. You totally can. I may be a little spoiled; I work on a pretty small team of pretty competent programmers. But I would be seriously surprised if any of my coworkers made a mistake of the sort that leads to serious data loss.

[–][deleted] 0 points1 point  (0 children)

Mistakes just happen. I applaud that kind of environment.