Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Giving concrete examples is something Feynman talked about a lot too. It is easy to talk abstractly about anything but in the end, something real and relatable must exist. When I deal with enterprise software, I prod the sales guys to tell me what the feature really means and does. Sure, it will streamline the sales order approval process but what does that entail? Outlook add ons? Browser popups? Notifications over SMS? Excel reports? Or 12 different screens that users have to click refresh on all day? My users will interact with something in the end. Show me the screenshots of all that already.

When I write business software, I dig in for details with my users in the same way. I understand you want me to fix the document printing process. Unfortunately that is too vague to write code for. Let's find out exactly what it is that needs fixing. Usually after some digging in, I change a button or two and it is now fixed!

It is hard work to be exact, precise, and specific. Being general is too easy.



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

Search: