Attila
Nevermind me then, I will never understand people.
In any case, this wouldn't work for me because it's missing a critical declaration of WHEN. Missed deadlines are more often discussed in failed projects' post mortems rather than wondering WHO dropped the ball.
I would've used '@' for WHEN and maybe '~' for WHO. But maybe we're getting into sigil hell.
The tilde '~' because UNIX/Linux alias for user's home directory. Hence the "who". I do admit that's a meaningless reason for any mainstream audience.
What's Hungarian about it? :)
When is definitely important, we have it on our roadmap. We picked @who because of @mention. Does it come natural to you?
> Hungarian notation is an identifier naming convention in computer programming, in which the name of a variable or function indicates its type or intended use.
http://en.wikipedia.org/wiki/Hungarian_notation#Relation_to_...
> For example, in some forms of BASIC, name$ names a string and count% names an integer. The major difference [...] is that sigils declare the type of the variable to the compiler, while Hungarian notation is purely a naming scheme not enforced by the compiler.
I think you have a good idea for "one time only, not planned tasks".
Don't try to make this the next project management tool. Just a syntax/app to handle last minute, unplanned and delegation tasks.
@who is the assignment
#what is the task name
@when is the due-date
!do is pointless to specify.
@JoeBloggs should !do #CakeBaking
vs
@JoeBloggs should !bake #Cake
EDIT: oh, I see, you tagging verbs more generally. I disagree. It adds context.
@JoeBloggs #Contract by Friday.
What about the contract? Review, sign, amend, shred?
Tagging things implicitly groups them and imbues the ability to search/filter/organize by them. I just have a hard time envisioning a useful scenario in which you're looking at "Show me the # of taks by verb used"
Example:
"@Peter should !find all copies of the #cat dossiers &across the datacube"
==>
"It works if @Peter !find all copies of the #cat dossiers &across the datacube."
:)
should implies "duty, obligaition or correctness" while "it works" connotes shared mission, and implies the hearer's choice to act or not, which is correct and respects their agency. "Duty, obligation or correctness" could easily trigger ego responses leading to inefficient conflicts.
BTW -- I love the straight up "No." it would be cool if you could touch and hold "No" to get a list of weasel words and excuses!!
Or just a simple "I decline."
haha :)
