![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Hooray for geeking!
Dec. 18th, 2005 05:03 pmThis morning I lost time in geeking again. I've been batting about the idea of a check-in timesaver program for a while, mostly in my head, and I've been meaning to start drafting up a requirements document in my spare time. I mentioned that to Darkside last night.
It seems that mentioning things to Darkside is a good thing, because before I knew it this morning, I had about a 3/4 page of requirements for the simple system, and was cheerfully telling Pink Shirt Guy about the idea.
Pink Shirt Guy found the idea good, started counting off on his fingers the number of people who'd need to be involved to develop such a thing, and told me to send it off to the manager whose office is one over from the corner office when I was done with it.
I poked at the requirements a little more, then spent a good chunk of time working on an HTML mockup of the thing. I was still hard at work on that when my opposite came in. I ran the concept past her, and she thought that would be so cool.
The draft requirements document and the html mockups have been sent off to the manager in question. They don't do anything -- they just look cool. There are two pages, one in People List mode, and one in Seating Chart mode. They demonstrate people in each of the four modes: in the right booth, absent, in the wrong booth, and logged in but not on the list. Temp Andy Adams is behaving perfectly. Jim Kirk is nowhere to be found. Mike Zorro (the company's designated Test Login) is here, but just a little out of sync with everybody else. Susan Ivanova came in for an extra shift and needs to be added to the list.
I swear, it took longer to convince the computer to let me create an HTML file than it did to actually write the requirements document. The playing-with-HTML itself was longer, but that's because there was all sorts of tweaking and tables and I was writing this from the ground up in Notepad, because I'm not a developer and I don't have those tools. Plus my forms are dreadfully rusty. I know it's all crap and will have to be torn out completely to make the actual system, but it looks pretty smart as a mockup. (Management? Is probably not going to see any difference between the mockup and the actual product, and gods help me if I get an over-inflated reputation for my 1337 c0de skillz, because I am so, so shite at coding. Fortunately Management has real geeks who can tell her that this is just a mockup and to not expect too much from the n00b.)
If this goes nowhere, it's a Sunday morning spent in restful leisure. If it goes somewhere, I'm going to be more thrilled than a very thrilled thing.
It seems that mentioning things to Darkside is a good thing, because before I knew it this morning, I had about a 3/4 page of requirements for the simple system, and was cheerfully telling Pink Shirt Guy about the idea.
Pink Shirt Guy found the idea good, started counting off on his fingers the number of people who'd need to be involved to develop such a thing, and told me to send it off to the manager whose office is one over from the corner office when I was done with it.
I poked at the requirements a little more, then spent a good chunk of time working on an HTML mockup of the thing. I was still hard at work on that when my opposite came in. I ran the concept past her, and she thought that would be so cool.
The draft requirements document and the html mockups have been sent off to the manager in question. They don't do anything -- they just look cool. There are two pages, one in People List mode, and one in Seating Chart mode. They demonstrate people in each of the four modes: in the right booth, absent, in the wrong booth, and logged in but not on the list. Temp Andy Adams is behaving perfectly. Jim Kirk is nowhere to be found. Mike Zorro (the company's designated Test Login) is here, but just a little out of sync with everybody else. Susan Ivanova came in for an extra shift and needs to be added to the list.
I swear, it took longer to convince the computer to let me create an HTML file than it did to actually write the requirements document. The playing-with-HTML itself was longer, but that's because there was all sorts of tweaking and tables and I was writing this from the ground up in Notepad, because I'm not a developer and I don't have those tools. Plus my forms are dreadfully rusty. I know it's all crap and will have to be torn out completely to make the actual system, but it looks pretty smart as a mockup. (Management? Is probably not going to see any difference between the mockup and the actual product, and gods help me if I get an over-inflated reputation for my 1337 c0de skillz, because I am so, so shite at coding. Fortunately Management has real geeks who can tell her that this is just a mockup and to not expect too much from the n00b.)
If this goes nowhere, it's a Sunday morning spent in restful leisure. If it goes somewhere, I'm going to be more thrilled than a very thrilled thing.
