Re:Software Engineering at Google (2017)
by lordnacho on Friday January 04, 2019 @06:27AM
(#18823257)
Isn't it essential for mental organisation? How do you think about what's different about a set of changes without some sort of DAG?
[ Parent
| on HN ]
Re:Software Engineering at Google (2017)
by username90 on Friday January 04, 2019 @05:41PM
(#18828427)
They are grouped by linking them to issues in the issue tracker. All commits will then get a link to the issue and the issue gets a link back to the commit. This way you can easily track and read the full context of old changes.
Example issue, note that public ones are not associated with commits: https://issuetracker.google.com/issues/122326181
Re:Software Engineering at Google (2017)
by yjftsjthsd-h on Friday January 04, 2019 @08:18AM
(#18823748)
Just do one thing at a time? Today, I am working on X; my commits are for X, and details are in the commit message.
That breaks as soon as you have to interrupt working on Nice To Have Feature X to working on Inportant Bugfix/CVE Y.
Re:Software Engineering at Google (2017)
by addicted on Friday January 04, 2019 @10:28AM
(#18824630)
How often does that happen to an individual developer though?
Once a month? In an averagely well run company even that may be towards the higher end.
Should your entire development strategy be based on a once a month occurrence?