And don't forget second guessing choices you made because 'there has to be a better way of doing this', but there isn't.
Show this thread
When doing a large programming task, coding is only half the work. The other half is writing small essay that tries to clearly explain everything you did.
-
-
-
Ok that's a lie. There is, but it would take several weeks, a lot of code refactoring, a huge risk of breaking all the things and like anyone has time for that.
Show this thread
End of conversation
New conversation -
-
-
I have been known to make mammoth commit logs. They're an artform.
-
Honestly they should have gotten us to write commit messages and review descriptions in University instead of actual essays.
- Show replies
New conversation -
-
-
I add sections, bullet points, code details, and everything, it's like writing an e-mail XD I once added references to lines in the code with comments on them XD
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Half!? 80/20 is what i tend to find. 80% docs, planning, testing. 20% code. Usually less time coding :p
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
50/25/25 thinking about the best way to do it / doing something else / deciding what to name the variables
-
My first job got someone in to do a talk entirely on variable naming and it was super helpful. But there are always some that'll haunt us.
End of conversation
New conversation -
-
-
There are definitely those people whose change descriptions are basically always two words, e.g. "fixed bug", "latest sdk", "performance improvement"
-
Those are always the most helpful when going the file history to figure out why something broke.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.