Reputation
4,258
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
9 23
Newest
 c#
Impact
~83k people reached

Apr
6
comment Writing an Overall test plan for a system?
"test plan" is well understood in Software Development Life Cycle. It is the formal specification/documentation for comprehensive system testing. One might argue that without a test plan testing is essentially ad-hoc. I expect to see test plans for military systems. Unit testing, if required, would be in there; but this is only one aspect of thorough system testing. The testing plan's complexity is generally commensurate with system complexity.
Apr
1
comment Rule of thumb for deciding which class a method belongs to
not "almost", but definitely,
Apr
1
comment Rule of thumb for deciding which class a method belongs to
You are assuming these are mutually exclusive. Why?. But the same "game - season - total stats" (or whatever) class (aka data structure) better be involved at the bottom of it.
Apr
1
comment Creating a new table referencing older one vs just creating a column
#1 will be a bitch to query and otherwise deal with, over time, within in the larger context of the entire application. #2 is a cross-reference table, easy to maintain and fast in a join because all it is a matched pair of indexed keys - user ids, and contact ids.
Apr
1
comment Should I add redundant code now just in case it may be needed in the future?
The conditionals may be redundant logically, but the code blocks are not redundant. If rows == null then you should execute all the code shown.
Apr
1
comment Should I add redundant code now just in case it may be needed in the future?
Much to learn you have, young Padawon. much, much easier to enhance the code with new behaviours, because I don't have to go back and ensure that all the relevant checks are in place. ... less one thing.
Mar
27
comment Using flat files vs database/API as a transport between a frontend and backend
Mega-dittos. And make sure you document the file format(s), maintain it, and distribute it. Next: The OP bullet about "uneducated staff ... poking around"; if that is a true concern then y'all have systemic problems. In our "lone developer" culture the worst that happened to us was some incompetent coding and collective ignorance as original coders left over time. I got there 20-ish years after it started and we had a maintenance nightmare.
Mar
27
revised Repeating a process can be a situation for method overloading?
added 148 characters in body
Mar
27
answered Repeating a process can be a situation for method overloading?
Mar
17
comment Per my design requirements, does this design hierarchy seem reasonable?
By structure I mean a class design, whatever that might be. I don't mean a linked list, tree, etc - the "classical" meaning of a data structure.
Mar
17
revised Per my design requirements, does this design hierarchy seem reasonable?
added 586 characters in body
Mar
17
revised Per my design requirements, does this design hierarchy seem reasonable?
added 274 characters in body
Mar
17
answered Per my design requirements, does this design hierarchy seem reasonable?
Mar
17
comment How to convince “old” co-workers of the merits of OO for certain applications
Upvote. In spades, dude. Caveat: the following is about human nature, not COBOL. ... One time, at band camp, we, a shop of mostly very experienced COBOL guys, were in an Ada course. I was shocked, stunned, gobsmacked that most could not understand what in COBOL are simply non-concepts like typing, scope, and parameter passing. Another time, you should have seen the WTF looks I got when all I did was use "scope terminators" introduced later in COBOL.
Mar
17
comment Dividing up the work of a large code merge among multiple people?
+1 R.H comment. ".. more frequently..." says it succinctly, @BenCottrell more thorough answer notwithstanding. No matter what your repository management plan you must commit frequently. At first, proper use of the tool will seem counter-intuitive but you must make that crucial "version control leap of faith" and use Mercurial as intended. P.S. from my old-head perspective modern distributive version control tools are truly liberating. P.P.S. google "forward integration"
Mar
17
comment Programs = Data Structures + Algorithms
state and structure are not the same thing.
Mar
13
revised A property that can represent both a single date and a date range: How to properly model that?
added 50 characters in body
Mar
13
revised A property that can represent both a single date and a date range: How to properly model that?
added 252 characters in body
Mar
13
answered A property that can represent both a single date and a date range: How to properly model that?
Mar
13
comment A property that can represent both a single date and a date range: How to properly model that?
down vote for ..ToString() [to] determine the state. ToString() should just "report" the state. State is determined in constructors, property setters, and so forth. And, I'm just not seeing anything in the OP that suggests there is or should be a "summary state"