Hacker News new | past | comments | ask | show | jobs | submit login

What's worse is when you do not think that the Smart TV registered your button press and you send another after a second or two. Then you'll get two keypresses queued up and fire at once and then you have exited your app/screen/etc. Yay. DirecTV's apps (even on their latest Genie DVR) are the worst - you hit the right button and wait about 8 seconds for the apps to load. Why even bother? Someone surely tests these things and sees the laggish behavior and just say, "Fuck it! Good enough! Ship it and never update it!"



Most of the time, in my opinion, and from my experience, is that non-functional requirements are never defined from their business analysts, and it's the same in many places.

A lot of places won't define performance requirements, as it's not their forethought to do so. They care about functional requirements, and if it meets those, then in their mind, their work is done. I've worked in several places (big names, too), that don't define non-functional stuff until after their beta is shipped and people start complaining.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: