Some reflection, dammit
I've noticed in this in some other areas of my schoolwork - I tend to underestimate what I've done, thinking that excellent work is really only OK, decent work is bad, etc.
(This is probably a good thing, because it gets me to the 'excellent work' level. :))
I believe that's the case with my Python work - although I've discusses this with my adult committee members on occasion, and they all seem to recognize that I've learned quite a lot in this field (programming) this year.
"To me programming is more than an important practical art. It is also a gigantic undertaking in the foundations of knowledge." - Grace Hopper
I believe I certainly will keep up with my Python work after the project is done and over with. I've heard it said that computer science can be as much of an art as a science, and I've also heard that some artists are eternally not-quite-satisfied with their work, always returning to modify what may be a very good piece.
If I was not occupied with other programming tasks, and other school business, I would definitely return to some of my old programs, even as far back as Number Guessing, something I wrote way back in 2006 when I was just learning about loops.
With some of the programs, I'd keep the original, and make a copy to folder called 2nd-version, or something like that. That way, I would have the original saved, to look back on.
For stuff beyond Hello World, there's an actual task the program's working on, even a simple one.
I see it as something like this:
Back when I wrote the starting-step programs, I was like a carpenter with only a few basic tools (screwdriver, hammer, etc.)
By taking a crack at a 2nd version, it might be like coming back to the projectwith several new power tools.
I have heard about the Senior Project in general that many people take their specific Senior Project skill with them, especially if it parlays well into a career. And shoot, writing programs can pay very well if one knows what one's doing.
I swear, I actually like writing code. (when I get it to work - when I don't get it to work, I just swear, period.)
(I wonder how Chuck Wooters, SWW class of '06, came along with his pilot's license - that is one Senior project I remember well from when I was an underclassman)
And there's got to be something that carries over in terms of the Senior Project process in general, although that's harder to pinpoint.
4 Comments:
> With some of the programs,
> I'd keep the original, and
> make a copy to folder called
> 2nd-version, or something like
> that.
How about just creating a tag for version 1 in your subversion repo and continuing development along the trunk?
Good idea. Explain how.
(I'm guessing you'd plunk some sort of code in the /tags branch...)
http://svnbook.red-bean.com/en/1.0/svn-book.html#svn-ch-4-sect-6
Wups. The address got cut off. Try this:
svn book: tags
Post a Comment
<< Home