192 reputation
4
bio website
location
age
visits member for 3 years, 7 months
seen Nov 20 at 16:06

Jan
9
awarded  Popular Question
Jun
24
accepted Objected oriented application exit
Jun
23
comment Objected oriented application exit
I guess what I have the most problem with, is that the DoAutoUpdate() function requires the program to exit if its going to work. It's not like it would be nice. If you try to update with out exiting, it is going to fail. Isn't it bad to write a function that relies on the caller to "finish" what you started in order for what you want to happen to actually work?
Jun
23
asked Objected oriented application exit
May
6
accepted How do you get consistency in source code / UI without stifling developer's creativity?
May
6
awarded  Scholar
May
6
accepted What's the best way to store documentation associated with a code project?
May
4
comment How do you get consistency in source code / UI without stifling developer's creativity?
It can be more trouble to judge the "value" sometimes than to determine the consistency. Here's another case... we print out pages, sometimes out of the report engine, and sometimes non-report pages are printed. It certainly has a value to have each page of each report have page numbers. If you're not in the habit of maintaining consistency, how are going to remember to check that this Print-out has all of the little things that might be easily forgotten (like page # or printed date).
May
4
comment How do you get consistency in source code / UI without stifling developer's creativity?
It seems like the style guide gets too large to be followed if you try to have a guide for everything. Also, it seems like you're just being a pest if you point out "you didn't use the proper style on when you did that", please fix. Unless you just go in and clean up the other developers mess every time he does anything.
May
4
asked How do you get consistency in source code / UI without stifling developer's creativity?
Apr
15
comment What's the best way to store documentation associated with a code project?
We have tried to use doku-wiki, but it is very tedious to use (try to fix a word doc typo is 10 tedious steps), plus no multi-user support on who is editing what. There were also lots of warnings and limitations about file size and file extension that really just annoyed more than helped. I got no buy-in on using it from the other people in the company. I see great potential, but not for my company unfortunately.
Apr
15
awarded  Supporter
Apr
14
comment What's the best way to store documentation associated with a code project?
Our 'wiki' solution is either a link to the network share (or link directly to files on the network. The disadvantage there is there's no version control of that. Or you download/edit/upload the file into the wiki, which is a 10 step process any time you want to edit it to fix a typo.
Apr
14
comment What's the best way to store documentation associated with a code project?
Earlz, We use VSS for version control, and it doesn't tie us to using VS to manage it, however VS appeared to provide a very nice way to group everything (code and documents) together (except it doesn't).
Apr
13
awarded  Student
Apr
13
comment What's the best way to store documentation associated with a code project?
We have 3-4 right now.
Apr
13
asked What's the best way to store documentation associated with a code project?