I haven't disappeared.
It has been busy at work, but then again it always seems like that.
I have been working on a program (non-game) that I originally thought of two years ago.
Why the long break on the program? At the time I felt that it wouldn’t be accepted even if it was finished (plus I was told it was being worked on), so I burned what I had done to a CD and set it aside.
So why start again? Because it is two years later and same problem is still there and as far as I can tell there has been little progress on addressing the problem much. At this point I’m working to get a simple version working and present it to the “right” people (or just put it in front of a lot of people until I find the right one). If nothing else it is improving my programming skills, I seem to spend more time reading about design and about programming, then I actually spend programming. Also it probably earn me a few brownie points for trying to solve the problem, even if the program I come up with isn’t adopted.
I have to admit that I’m happy that I kept the old code (even as poorly written as it is), because I’m using a free library as part of the program and it saved me from having to re-figure how to use it purely off the manual pages (which aren’t bad in documentation terms, but they lack examples).
I have gotten the basics all pretty much in place and with a much cleaner programming style. Now I have the hard part of me, making it do what I want it to do. ;)
Why the vagueness on what the program will do?
There are a few reasons:
First: I really don’t want talk in to much detail about work here. *See earlier posts*
Second: If the program is adopted, it would leave a trail here.
Third: I don’t want someone taking my work and beating me to it.
Fourth: If I can’t do it and scrap the whole thing, no one will know I was working on it in the first place. ;)
I have been working on a program (non-game) that I originally thought of two years ago.
Why the long break on the program? At the time I felt that it wouldn’t be accepted even if it was finished (plus I was told it was being worked on), so I burned what I had done to a CD and set it aside.
So why start again? Because it is two years later and same problem is still there and as far as I can tell there has been little progress on addressing the problem much. At this point I’m working to get a simple version working and present it to the “right” people (or just put it in front of a lot of people until I find the right one). If nothing else it is improving my programming skills, I seem to spend more time reading about design and about programming, then I actually spend programming. Also it probably earn me a few brownie points for trying to solve the problem, even if the program I come up with isn’t adopted.
I have to admit that I’m happy that I kept the old code (even as poorly written as it is), because I’m using a free library as part of the program and it saved me from having to re-figure how to use it purely off the manual pages (which aren’t bad in documentation terms, but they lack examples).
I have gotten the basics all pretty much in place and with a much cleaner programming style. Now I have the hard part of me, making it do what I want it to do. ;)
Why the vagueness on what the program will do?
There are a few reasons:
First: I really don’t want talk in to much detail about work here. *See earlier posts*
Second: If the program is adopted, it would leave a trail here.
Third: I don’t want someone taking my work and beating me to it.
Fourth: If I can’t do it and scrap the whole thing, no one will know I was working on it in the first place. ;)