Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Good question - though I don't think it's a problem of broken process, but an absence of processes like you listed above. That's when these types of "solutions" are devised/used.


Two things I've learned in my years as a developer:

1. Sometimes the best process is old fashioned communication between people with common sense.

2. Never underestimate the power of a rubber chicken.


>1. Sometimes the best process is old fashioned communication between people with common sense.

I most wholeheartedly agree. Git, or a Source Control Shingle cannot replace effective communication. In fact, a solving a merge conflict is much more painful than a quick discussion.




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

Search: