I wrote up something similar a few months ago called "Everything I Have Ever Programmed": https://www.linkedin.com/pulse/everything-i-have-ever-progra... I recommend taking a bit of time to do a similar write-up, it comes easily and you'll probably be surprised by the sheer amount of stuff you've worked on, and might see some interesting patterns.
I'd like to write something like this, but I'd be unemployable if any potential employers actually read it. Old enough to have learned to program on an Apple II while they were still in production == too old to work here.
Tavish’s excessively long programmer biography
31–40 of 54 posts
Re: Tavish’s excessively long programmer biography
#32When I read things like this, I end up feeling a lot of sympathy for kids who are trying to learn programming and "computers" nowadays. I count myself as very fortunate that I started learning programming back in the 80's when not much was expected out of computers, since they were so (relatively) underpowered. I feel like I was able to learn programming concepts at a much more leisurely pace than you're expected to…
Re: Tavish’s excessively long programmer biography
#33Re: Tavish’s excessively long programmer biography
#34I started programming before the author was born.
Yeah me too. If his bio is "excessively long", I dread to think how mine would turn out or have to be titled.
Re: Tavish’s excessively long programmer biography
#35When I read things like this, I end up feeling a lot of sympathy for kids who are trying to learn programming and "computers" nowadays. I count myself as very fortunate that I started learning programming back in the 80's when not much was expected out of computers, since they were so (relatively) underpowered. I feel like I was able to learn programming concepts at a much more leisurely pace than you're expected to…
This is a good point—I see a bunch of people overwhelmed nowadays on forums about languages, frameworks, paradigms, ideas, etc. So many! I know we say "just pick one, it doesn't matter" but still, not an easy choice.
Reading "Masters of Doom" I couldn't help but feel that the technical constraints that existed at the time bred craftsmanship that seems hard to justify these days. Still trying, though.
Re: Tavish’s excessively long programmer biography
#36Here's Tavish's blog post from 2011 about it: https://evolvingweb.ca/blog/my-internship-at-evolving-web
Tavish, thanks for the kind words. We learned a lot from you too!!!
Re: Tavish’s excessively long programmer biography
#37While you can certainly read biographies of famous individuals they are often too long and are often fringe cases anyway (not representative of others in the field). Also often biographies are written after or near the end of ones career so facts maybe hazy and or contextually irrelevant by the time they are published.
For software development this is no so difficult as most developers are transparent and blog but for many industries this is not the case.
Re: Tavish’s excessively long programmer biography
#38What's the point actually? I mean, I admire the diligence required to write it all down but how should this change my outlook on programming? The general idea is 'in order to be a good programmer, keep doing computer stuff'. Do we need extensive biographies full of details to learn this?
But there are still some similarities -- his reasons for learning vi(m) and (La)TeX were basically the same as mine -- word of mouth from people who knew more.
Re: Tavish’s excessively long programmer biography
#39Why is this interesting?
"Interesting" is in the eye of the beholder. If you don't think it's interesting, then it's not. Don't ask the internet to help you form an opinion.
Just kidding. I think it is telling this is on the front page - I was arguing with fetus' until now ;)