Programming wisdom from articles, books, comments & videos. Learning from other's experience.
“Everyone has a million bad words in them. Only once they’ve written those million words can they start writing well. So get writing!”
"The only way to write good code is to write tons of shitty code first. Feeling shame about bad code stops you from getting to good code"
"Code is art and every artist wants to go back and redo their bad works. But the best thing to do is learn and move on to create better art." (comment)
Practical Lesson: when reading a file in Java line-by-line, don't concatenate every line to a String variable. Use either Builder or read the whole file using Files.readAllLines or Files.readAllBytes - more info on SO
Most postmortem blog posts are teary affairs explaining how something went wildly wrong and how this will not happen again, but we think postmortems are useful for any major change, whether a success or failure. It’s great to learn from mistakes, but it’s also useful to learn from successes that demonstrate due diligence to the only true shortcut: Do things right the first time.
- Make notes, note everything you learn and/or will use/do again.
- Maintain simple but reasonable notes hierarchy
- Before you start using some new cool tool/program/etc, think if you really need this for a particular project. The fact that a lot of people use something, doesn't mean that it can be useful for my particular case OR it's a good solution to a problem (sometimes using simple bash script may be better than learning new tool, its workflow and adding unnecessary complexity)