![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Apr. 27th, 2004 11:01 amhaving a tv on is like being in a room where a bunch of people are interacting with each other and completely ignoring you.
(no subject)
Apr. 27th, 2004 11:01 amhaving a tv on is like being in a room where a bunch of people are interacting with each other and completely ignoring you.
a tale of geekness
Apr. 16th, 2004 09:54 amdue to exposure to dungeons & dragons, and misc computer games in which the wizard unit can cast a wall of fire to burn up naughty units that try to pass through it, i've always pictured a computer "firewall" as a burning wall of fire surrounding the network.
i was disappointed to realize that it's really from a standard wall between buildings or sections of a building meant to keep fires from spreading quickly.
from towering magical wall of flames, to standard off-white office wall. sigh.
i was disappointed to realize that it's really from a standard wall between buildings or sections of a building meant to keep fires from spreading quickly.
from towering magical wall of flames, to standard off-white office wall. sigh.
a tale of geekness
Apr. 16th, 2004 09:54 amdue to exposure to dungeons & dragons, and misc computer games in which the wizard unit can cast a wall of fire to burn up naughty units that try to pass through it, i've always pictured a computer "firewall" as a burning wall of fire surrounding the network.
i was disappointed to realize that it's really from a standard wall between buildings or sections of a building meant to keep fires from spreading quickly.
from towering magical wall of flames, to standard off-white office wall. sigh.
i was disappointed to realize that it's really from a standard wall between buildings or sections of a building meant to keep fires from spreading quickly.
from towering magical wall of flames, to standard off-white office wall. sigh.
I think of a name. It has to be catchy, and cool, and good for sales and searches.
I think of a file extension, and search to see if it exists.
I ponder the various types of visual studio projects, and frown, and choose mfc app.
I choose options. I grumble.
I create the project. I growl at the stupid names and structure they use. 'hlp'?? Yes let's just abbreviate everything stupidly and put most every type of file in the root directory.
I move things out of root directories, creating hierarchies good for cross-platform development.
I modify the project settings with a text editor to find the new files where they are now.
Visual Studio barfs and tells me it can't open the new project, and doesn't say why.
I try to fix.
I try to repeat all of the above with tweaks here and there.
I give up.
This sort of procedure has served me well for the last decade, but i think i might need to start modifying it, particularly if i ever want to create actual software.
Sometimes i get beyond the above stage, perhaps by bypassing it and ignoring the stupid hierarchy, and then i create a GUI layout without defining exactly what the program is supposed to do, and then i create a complex rational system of prefixes and suffixes for various identifiers, then i change everything and go through the code to make it pretty in the new way, then i almost get to the point where i can start adding actual functionality, then i give up because it's too boring to do the basic GUI functionality because i want to be working on the higher level things and it's taking too much time and i have to do X instead.
This alternative procedure also may need some modifications.
I could write down the steps i know i should take, and then follow them, but that's perhaps too sensible.
I think of a file extension, and search to see if it exists.
I ponder the various types of visual studio projects, and frown, and choose mfc app.
I choose options. I grumble.
I create the project. I growl at the stupid names and structure they use. 'hlp'?? Yes let's just abbreviate everything stupidly and put most every type of file in the root directory.
I move things out of root directories, creating hierarchies good for cross-platform development.
I modify the project settings with a text editor to find the new files where they are now.
Visual Studio barfs and tells me it can't open the new project, and doesn't say why.
I try to fix.
I try to repeat all of the above with tweaks here and there.
I give up.
This sort of procedure has served me well for the last decade, but i think i might need to start modifying it, particularly if i ever want to create actual software.
Sometimes i get beyond the above stage, perhaps by bypassing it and ignoring the stupid hierarchy, and then i create a GUI layout without defining exactly what the program is supposed to do, and then i create a complex rational system of prefixes and suffixes for various identifiers, then i change everything and go through the code to make it pretty in the new way, then i almost get to the point where i can start adding actual functionality, then i give up because it's too boring to do the basic GUI functionality because i want to be working on the higher level things and it's taking too much time and i have to do X instead.
This alternative procedure also may need some modifications.
I could write down the steps i know i should take, and then follow them, but that's perhaps too sensible.
I think of a name. It has to be catchy, and cool, and good for sales and searches.
I think of a file extension, and search to see if it exists.
I ponder the various types of visual studio projects, and frown, and choose mfc app.
I choose options. I grumble.
I create the project. I growl at the stupid names and structure they use. 'hlp'?? Yes let's just abbreviate everything stupidly and put most every type of file in the root directory.
I move things out of root directories, creating hierarchies good for cross-platform development.
I modify the project settings with a text editor to find the new files where they are now.
Visual Studio barfs and tells me it can't open the new project, and doesn't say why.
I try to fix.
I try to repeat all of the above with tweaks here and there.
I give up.
This sort of procedure has served me well for the last decade, but i think i might need to start modifying it, particularly if i ever want to create actual software.
Sometimes i get beyond the above stage, perhaps by bypassing it and ignoring the stupid hierarchy, and then i create a GUI layout without defining exactly what the program is supposed to do, and then i create a complex rational system of prefixes and suffixes for various identifiers, then i change everything and go through the code to make it pretty in the new way, then i almost get to the point where i can start adding actual functionality, then i give up because it's too boring to do the basic GUI functionality because i want to be working on the higher level things and it's taking too much time and i have to do X instead.
This alternative procedure also may need some modifications.
I could write down the steps i know i should take, and then follow them, but that's perhaps too sensible.
I think of a file extension, and search to see if it exists.
I ponder the various types of visual studio projects, and frown, and choose mfc app.
I choose options. I grumble.
I create the project. I growl at the stupid names and structure they use. 'hlp'?? Yes let's just abbreviate everything stupidly and put most every type of file in the root directory.
I move things out of root directories, creating hierarchies good for cross-platform development.
I modify the project settings with a text editor to find the new files where they are now.
Visual Studio barfs and tells me it can't open the new project, and doesn't say why.
I try to fix.
I try to repeat all of the above with tweaks here and there.
I give up.
This sort of procedure has served me well for the last decade, but i think i might need to start modifying it, particularly if i ever want to create actual software.
Sometimes i get beyond the above stage, perhaps by bypassing it and ignoring the stupid hierarchy, and then i create a GUI layout without defining exactly what the program is supposed to do, and then i create a complex rational system of prefixes and suffixes for various identifiers, then i change everything and go through the code to make it pretty in the new way, then i almost get to the point where i can start adding actual functionality, then i give up because it's too boring to do the basic GUI functionality because i want to be working on the higher level things and it's taking too much time and i have to do X instead.
This alternative procedure also may need some modifications.
I could write down the steps i know i should take, and then follow them, but that's perhaps too sensible.
