Neither did I, but once that point was brought to my attention...I figured it can't hurt to further define the two...as clearly there are discrepancies...not sure if it's an actual definition...but it certainly cleared up any confusion I hadJcart wrote:Didn't realize there was a difference
TODO lists
Moderator: General Moderators
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
- John Cartwright
- Site Admin
- Posts: 11470
- Joined: Tue Dec 23, 2003 2:10 am
- Location: Toronto
- Contact:
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
Not solely for the sake of nomenclature...but don't you find it's analogous to problem solving...Jcart wrote:I'll keep in mind to use the proper term next time
It's like that thread I started a while back inregards to config data being immutable or volatile...I believe most swayed in the direction of the latter...but still a large portion said immutable...
To me, this says two things:
1) Configuration as a computer programming term is not clearly defined
2) When ever something isn't clearly defined you potentially introduce human error
Wherever you have conflict you have problems...IMHO it makes sense to simplify the problem of "he said, she said" and clearly define the difference between the two. Like design patterns help you further abstract a programming problem...you can think of explicit definitions as doing the same thing.
Now instead of arguing with your co-worker about whether or not config data is immutable or a TODO entry is trivial or verbose...by definition alone you both now understand what exectly each party meant - no fuss.
For me it's just another method of problem decomposition added to the software development life cycle...that was the only point I was trying make...
Cheers
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
- Christopher
- Site Administrator
- Posts: 13596
- Joined: Wed Aug 25, 2004 7:54 pm
- Location: New York, NY, US
I am not sure I agree with those two. A TODO list is simply a list of items describing things to do -- whether statements or questions. A Task is a piece of a larger job or project. It may or may not be a compilation of TODO lists. I get the sense that a TODO list is a time limited set of tasks from multiple sources.Hockey wrote:1) TODO list is a collection of terse statements
2) Task is a compilation of TODO lists
(#10850)
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
Ok fare enough. Everyone is going to have their own definition...I guess what is important is that you and your cohorts agree on a definition (either as a company policy or project, etc) and stick to that definition. It's helps prevent the problem of human error, miscommunication, etc...arborint wrote:I am not sure I agree with those two. A TODO list is simply a list of items describing things to do -- whether statements or questions. A Task is a piece of a larger job or project. It may or may not be a compilation of TODO lists. I get the sense that a TODO list is a time limited set of tasks from multiple sources.Hockey wrote:1) TODO list is a collection of terse statements
2) Task is a compilation of TODO lists
Personally a task is just a higher level or more abstract outlook (typically structured in fashion) of a vague problem...whereas TODO lists, are as you've said, time sensitive but in my case trivial regardless of whether they are questions, comments, etc...
I estimate project time based on an enumeration of very simple todo's which when grouped togather form a task.
For instance a task might sound something like:
From the following statement, I further decompose the problem into a trivial TODO list:Implement a createUser() method. Return values are either TRUE on success or FALSE on failure. If the user ID doesn't already exist, then create it and flag the account as "pending". if the account already exists - exit early and report an error. Some other checks we need to perform is geo-addesses making sure they coincide with postal codes.
This is off the top of my head...but i'm sure you get the idea...1) Check if user ID is valid and if it exists, exit on TRUE otherwise continue.
2) Check user address and postal code are in same region. Continue with step 3 on TRUE
3) Create user account, flag as pending - until confirmation email is received.
Cheers