Hacker News new | past | comments | ask | show | jobs | submit login

Every team I’ve worked with has had an informal locking method that gets used for really disruptive work. Instead of locking files in the VCS, you tell everybody that you’re going to be doing X, try not to make changes around that, and coordinate with that person if you really need to make changes on the same stuff.

I think the informal technique works better since it’s a lot more flexible, but the basic concept is very useful.




That works until someone has a few beers at lunch and proceeds to come back and start smashing things (been there :)




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: