Show HN: Focus on what matters – who should do what
opp.io@opp.io should !describe the #product before dumping you to a signup screen. I'm not grabbing headphones just to watch a video slowly describe what can be conveyed in text.
You are right. We got rid of more detailed explanations because it converted better, but we will try showing more of the product.
Attila
it converted better
Nevermind me then, I will never understand people.
Hmmm... Hungarian notation for task delegation. Interesting.
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.
+1 for WHEN. I like the ~ for When since a lot of dates are ballpark estimates, at least in planning stage.
Choice of symbol has some degree of being arbitrary and I only preferred '@' for when because we (at least in USA) often specify time that way. E.g. "meet for lunch @2:00pm". However, I can see that '@' might feel like a fragment of an email address John@xyz.com.
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.
I also often use @ for specifying location. See you @office, @home.
How do you feel about '>' as WHEN indicator?
(I am one of the guys behind opp.io)
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?
http://en.wikipedia.org/wiki/Hungarian_notation
> 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.
Wow, didn't know that. Thanks for sharing, I really learned a lot!
One place I worked had a coding standard based around hungarian notation. For some reason I hated it, but I kind of like Perl's sigils.
So it's like latin declinations?
I guess you mean declension. Are you a Spanish speaker? It's a mistake I usually make too, being the expected translation of "declinación".
Yes, it's comparable to declension, though Hungarian notation is prefix and not part of the syntax, while declension is postfix and has syntactic meaning.
Yes, that's what I meant. I'm a Portuguese speaker ("declinação"). I should have checked the correct translation. Thank you for understanding what I meant and correcting me.
I'm always afraid to come across as pedant or judgmental, but I enjoy being corrected to improve my English so I posted it anyways :) Glad it helped.
I am also for @who should !do #what ~when
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.
I don't agree with the verb tagging personally. It's irrelevant, isn't? Someone need to "do" something. The particular word choice doesn't impact the necessity.
@who is the assignment
#what is the task name
@when is the due-date
!do is pointless to specify.
`do` isn’t always the verb, though.
@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?
You include the word like normal, I'm saying tagging it isn't going to be helpful in the long run. Not to mention you're already including the word "should" and now a bang too? Could have very simple language detection to identify the verb if that's the goal.
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"
While we use the word "should" on the landing page, in conversations is more flexible, hence the bang.
"@Meritt, can you please !inform the #delivery"
This is the best simplest interface for getting things done I've seen. Awesome! Are you open sourcing this?
hi humanarity, not in the short term, but will allow API integrations.
I liked the notation thing, are there any other examples of applications that work like this, with a notation system that normal people can use (and do not feel like they are programming)?
"should" - not the best verb, but cool idea nonetheless.
Erik, how would you phrase it?
"x should y" ==> "it (modal:may|might|would|could|will)? work(s)? (for|(for us)? if) x (to)? y" / "x y-ing works"
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 :)
What if the receiver chooses what tone of language they want to receive in. E.g. "terse" or "nice" options.
Nice ! ... an app idea in that somewhere... :)
amazing :) keep it up!