31–40 of 102 posts
1. Number of active users of language matter more than the language itself.
1.a Fads come and go.
2. Math matters.
3. Elaborate design/architecture before programming is a waste of time. Emphasis on elaborate, not architecture.
Use an IDE, not VIM
Use a good (for your platform/language) IDE, not VIM.
If you aren't sure what a good IDE looks like try Intellij as a safe default.
Also it's still worth learning VIM.
Use an IDE, not VIM
Learning Vim has been one of the best professional choices I've made.
With dynamic languages I've seen a couple of IDEs that weren't able to actually deliver the refactoring or search tools they promised.
What you were left with was a large, slow editor with a poor keyboard interface.
I'd rather be closer to the operating system in Vim or Emacs and add refactoring using external tools like tern, rope, godoctor, etc.
Terminal based tools allow you to work anywhere and support easy collaboration using things like tmux.
"9. Trying to understand everything is a lost cause. In the beginning, I tried to chase down the “why” to every problem I encountered. This isn’t necessary." Nonsense. That is literally the worst advice you could give to an aspiring programmer. It is precisely necessary to get to the bottom of your programming problems and bugs, that's the stuff that increases your knowledge and lets you understand systems deeply. Be…
No, but more than one can work wonders for productivity if you are looking up documentation while coding, so you don't have to constantly alt-tab and forgetting where you were.