I spent a long time trying to become good at C++. This was also a mistake.
I ignored Python for a good 2 years because of indentation. Again, a huge mistake.
Great suggestion on anger inducing articles/comment sections. I was just thinking it would be nice to do sentiment analysis and incorporate the emotional vector into both the dynamic rules and the layout. At least put a badge on the discussion so I can know to stay away.
Since it has affordances for speed, it encourages one to make fast code, but this is rarely needed. Making fast code is a trap.
Trying to become good or very good at something also puts you in direct competition with others doing the same thing. I did not have time to compete, so it wasn't a big differentiator for me.
C++ helped me learn when do give up, and when to refocus my attention in areas where I can have greater impact. I wish I was a little more technically and philosophically mature before I undertook C++. Having concrete goals is a huge clarifier and allows one to judge something with a much better light.
w3m, nice! I tried lynx, w3m, eww (emacs) lately, and liked w3m the most, but found it terribly slow on many sites. In particular GitHub. Just measured 12 seconds for loading my Profile. lynx takes 5s. Opera takes 2s.
Do you have similar experiences?
> Know your prejudices and look for information that challenges them.
How do you prevent the two of these from coming into conflict?
uh... wtf?
See also Mike Acton (Engine Director @ Insomniac Games): https://www.youtube.com/watch?v=rX0ItVEVjHc
OO is handy in enterprise software where there are lots of developers who may not understand why things are the way they are, they just need to do something. In big, complex systems where a lot of things are going on, if you give someone a noose, they will hang themselves. OO can protect data from some (of course not all) unintended consequences.
* Avoid headlines that make me angry, unless the news is really important. The discussion is never worthwhile, don't even bother.
* WSJ, Bloomberg, and WaPo won't let me read articles with w3m, so I skip the article. If the topic is tremendously interesting, I'll check the comments.
* TED and nautil.us are the information verison of empty calories. I've never gained any long term benefit from reading them.
* Javascript framework churn is intense. It's not worth trying to keep up with the details unless you do web development. If, like me, you don't, it's still worth reading the headlines to keep abreast of what frameworks are popular, what paradigms they embody, and who's pushing them. This changes every six months or so.
* It's always worth scanning the comments in threads about programming languages. There are some really interesting people who sometimes jump into those threads and blow your mind.
* Know your prejudices and look for information that challenges them. My prejudices are that I think Windows is lame, that MacOS is infuriating, that Javascript is terrible, that vim is better than emacs, and emacs is better than IDEs, and object orientation is a failed paradigm. So I look out for articles that have a different point of view. I've learned that Microsoft has some really interesting technology, that Apple is infuriating even to its own users but it doesn't matter because they're sitting on the world's biggest pile of dollar bills, that Javascript is usually unnecessary but occasionally useful, that kakoune is even better than vim, and that nobody agrees about what object orientation even is.