According some articles written by senior programmers, it seems 'writing' is very important to geeks.(or, so called programmers) And I found three big reasons why geeks should write.
First.
As human memory isn't always perfect and code can always go longer and more complicated any time, it is really important to write a log while you code. Especially when you do a debugging job, it is possible that you get completely lost with no clues. The logs you left while coding would be a 'clue' in this case, of where to start, and how you would solve an issue.
Second.
You can get use your notes as a future reference. Even if you solve an issue in your code, it doesn't mean you'll never make a same type of mistakes again. By writing logs on issues you've solved, you can use it as a reference, which will save your time.
Plus, you can learn lessons from your log. It's much like making a note on math questions that you don't fully understand, so you can review over times. From the logs you wrote, you can review on the mistakes you've made, and understand the problem and solution better.
Third.
Writing as a 'communication skill' is also important asset to programmers. In most of cases, coding and designing software works are co-op works, rather than individual. Writing notes on your code will help other programmers/co-workers understand how your code works and what it is about. The code without writing is pretty much 'pointless'.
Since posting logs on SLOG is a form of 'writing as a geek', I'm looking forward to improving my coding habits.