5 ms·
The problem here is the author’s development process. There’s an “old” programmer adage in regard to version control: merge early, merge often. It addresses t
by bfung 8y ago
The problem here is the author’s development process. There’s an “old” programmer adage in regard to version control: merge early, merge often. It addresses the author’s issue directly.
So yes, it’s not the code that’s bad. It the development process. Bad (ok, fine, inexperience) developer.
https://queue.acm.org/detail.cfm?id=1643030 https://queue.acm.org/detail.cfm?id=1643030
- unionpivo 8y agoThat's the point. There is always something you haven't thought of (or did wrong), once you get to certain level of complexity.
- sifoobar 8y agoRegardless of language. You'll have different kinds of bugs, but as long as there are programs they will contain bugs. Or the languages themselves will, or the libraries used, or the OS. Assuming the presence of bugs/failures and providing powerful tools to deal with them like Erlang is a more realistic option if you ask me.