DonationCoder.com Software > Post New Requests Here

IDEA: Discrepancy Trainer

(1/3) > >>

mouser:
Ok i'm trying to post smallish ideas here, in hopes people will find something they like to do for their NANY 2010 projects.

Here's an idea i had a while ago for a utility designed to help people become more accurate and realistic about their predictions and promises in terms of deadlines.  Most coders I know underestimate the time it will take to get something done, or how much we can get accomplished in a given period, etc.  At the start of the day it feels like you can achieve anything.. at the end of the day you wonder where the time went..

So, here's the idea:

Program shows a list view with columns for:
Item description, Measurement description, Predicted Value, Actual Value, Accuracy

I'll give you an example:
I start out by adding a new item with the following column values:

* Item description = Finish reading new book on Planning Algorithms
* Measurement description = Number of days to finish (starting on Nov 15, 2009)
* Predicted Value = 21
That says i hope to finish this book in 21 days.

Then when i actually finish the book i go back to the program and add how long it really took:

* Actual Value = 63
Then the program can calculate the last column for me:

* Accuracy = 30% (shown in red since i took longer than i said, meaning bad)
You dont have to use days, thats why i have a separate column for measurement description.  You could instead have an entry for how many pages of a novel you can write in one week for example, or how many pounds you can lose on a diet in one month, etc.


Other bonus features:

1) show a running average of accuracy at top.
2) have view modes for: show all, show incomplete, show complete
3) add a date-added column
4) allow soring on columns

JavaJones:
Cool idea, and useful for more than just programmers, to be sure!

- Oshyan

nudone:
yes, very interesting. i think i'd find it useful too.

SleepingWolf:
Great idea, perfect for students to test their heavy mettle! One question, how are you getting the above accuracy? I'd have thought it should be (63/21)*100 = 300%, not 30%. But I'm no expert, just guessing here.

mouser:
i just did the reverse (21/63) but there are lots of functions you could use, as long as they were heuristics for accuracy.

Navigation

[0] Message Index

[#] Next page