News for hackers. Stuff that matters.
Re:Teach Yourself Programming in Ten Years by gabriel on Thursday May 15, 2008 @11:21PM (#191393)
Even though an old and previously posted article, is anyone listening? Or maybe it's a question of beliefs?

Because I think another aspect to look at this article with is that learning how to hack is fine, though start-ups should be focusing on the toughest problems, and ignoring history (how things got to where they are today) won't help anyone.

All of you working on the next social platform better beware of the history.

Re:Teach Yourself Programming in Ten Years by Tichy on Friday May 16, 2008 @02:51AM (#191536)
Listening to what, exactly? "I suck, because I haven't programmed for 10 years"? What exactly is the message here?
Re:Teach Yourself Programming in Ten Years by gabriel on Friday May 16, 2008 @02:59AM (#191546)
My message is that it's one thing to learn how to hack, but another part of it is learning why hacking is the way it is in order to figure out what to work on today.

Some things change fast, others don't. Most don't take the time to understand this--the best will.

Re:Teach Yourself Programming in Ten Years by aaronblohowiak on Friday May 16, 2008 @05:14AM (#191617)
when you've programmed for 10 years, how much further do you hope to be than you are now?
Re:Teach Yourself Programming in Ten Years by Tichy on Friday May 16, 2008 @07:24AM (#191676)
I have actually programmed for more than 10 years. My current impression is that I will probably never become a specialist for anything and will just have to make up things on the go, because technology changes so fast.

Maybe I have acquired some kind of taste, but then I always think about the many successful PHP projects out there (PHP is horrible in my opinion). So maybe even that "taste" is overrated. Just doing it seems to be all that counts.

Another thing is that I somehow try to optimize for the changing demands, and try to become faster at picking up stuff. I try to make it seem normal to pick up a new technology, rather than a reluctant effort. Not sure if it is the right way to go, though, and I also don't have a system for it.