Hacker Timesnew | past | comments | ask | show | jobs | submit | byamit's commentslogin

The article mentions (and I agree) that OKRs aren't meant to be used for employee evaluation but rather provide a user focus on what they need to work on.

It's easy to lose sight of what your goals are when you're knee deep in a problem, so OKRs are helpful to remind you what you originally set out to accomplish.


I got excited because I thought Part 2 had finally come out. Definitely a great visualization for folks new to the area.


http://meyerweb.com/eric/tools/s5/features.html#controlchart

A couple useful shortcuts there depending on what you're trying to do.


I saw that. Typing '1'+<RIGHT ARROW> advances slides, but doesn't load the full slide.

Bad presentation design.


+1. An additional interface would be great. Looked at doing something similar a while back and quickly realized I would need multiple endpoints. One endpoint would be for trusted users who could automatically add to the stream, while a 2nd endpoint would require manual approvals. It would help prevent awkward moments when friends decide to have "fun" after a couple drinks.


I've been involved with a couple conferences before and agree with wholeheartedly with the post.

  As a conference chair, you’re responsible for delivering on every promise to the attendees and sponsors! Stop and reread that line.
This is key. I've seen situations where teams bring on too many volunteers who promise all sorts of things. The chair is optimistic at the beginning since they have a large team. Eventually, about 1/3rd of the team will flake and the chair is left holding the bag. The remaining volunteers are pushed to uphold all the promises and the stress collects.

It'd be great if you write a follow up post going into more details about your experience.


I'm gonna write a series of posts breaking down the chunks of the work and experiences. This is just the first.


Yeah - have to say this is the most amount of work I've had to do just to sign up for a newsletter.


Okay, thanks for the input, and sorry about that. We'll change that.


We did a quick fix for now, so it's easier to sign up. We'll pt the input form on the site itself soon.


I recently discovered http://www.cockos.com/licecap/ which lets me take screen captures and save them as gifs. Definitely helpful when trying to capture CSS animation bugs.


Good read - I'm actually putting together something with a partner so definitely agree on making sure the agreement has a buyout clause.


It's interesting but how does it handle the case where the user navigates away before the counter hits 0?


If a feature request doesn't align with the product's vision, it's perfectly fine saying no. If the vision itself is flawed, then the product is not likely to succeed.


Every vision is flawed, because we are fallible. The question is what we do about that. Do we keep the product nailed to the flawed vision until the last user has gone elsewhere, or do we use feedback from reality, from users telling us what they need, to improve the vision?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: