Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What I learned from this post:

* The author thinks startups are better than large companies

* The author thinks senior developers at large companies are older than startup developers --- else, why bring up age?

* Despite admonishing his protagonist to learn one new language per year, the author believes "career rust" is a problem of age --- else the story would have worked with a 28 year old dev still writing in PHP.

* The author really likes unit tests.



I thought it was interesting that this cycle takes 20+ years in this author's world.


I've worked with many 28 old wring in PHP4. But, somehow, I feel that there is hope for them - someone 50 year old dog might show them the light.

I've made John 50 because I wanted to make it too late for him to fix things (although he still stands a pretty good chance to get back on track). Do not wait for something to happen. Stop repeating "Will read this book after the next release" - start reading now in you spare time.

Improving constantly is the main moral of this story. It has nothing to do with age.


You did not just gain credibility by saying "50 is too late for him to fix things".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: