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.
Show this thread
-
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.
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.