From novice to master, and back again (2013)
blog.djmnet.org
From novice to master, and back again (2013)
1–10 of 150 posts
Re: From novice to master, and back again (2013)
#2the difference is that nothing I've ever worked on will ever be public or useful beyond a small private business which doesn't even exist anymore.
Re: From novice to master, and back again (2013)
#3Re: From novice to master, and back again (2013)
#4Re: From novice to master, and back again (2013)
#5yes. I think most of us who programmed in the trenches are familiar with forgetting what we've done... the difference is that nothing I've ever worked on will ever be public or useful beyond a small private business which doesn't even exist anymore.
Re: From novice to master, and back again (2013)
#6Re: From novice to master, and back again (2013)
#7Re: From novice to master, and back again (2013)
#8yes. I think most of us who programmed in the trenches are familiar with forgetting what we've done... the difference is that nothing I've ever worked on will ever be public or useful beyond a small private business which doesn't even exist anymore.
Think of the people you've helped get their jobs done over the years. That's worth more than author credit in the colophon of a man page.
edit: or the program the man page is documenting!
Re: From novice to master, and back again (2013)
#9Before I began my studies in Zen, I thought a tree was a tree and a stone, a stone.
When I started to study Zen, I could see that a tree was not a tree, and a stone was not a stone.
Now that I am a Zen master, I know that a tree is a tree and a stone is a stone.
-- Source: my buddy in college
I think you come full circle to learn that you can only keep so much in your head at one time and that you're always in some sense loading up what you need for the next month or three. At least this time you knew to look for the man su command, and remind yourself of the work you did, that you shared with all these other people.
Re: From novice to master, and back again (2013)
#10Granted, I have specific code tells, which helps, but like the article mentions I have forgotten the why or the bug that I fixed that required specific changes.