the 'user story' presented: - didn't identify the user - did't identify why the user needs a more generic api - what a more generic api would look like ... etc

the 'user story' presented: - didn't identify the user - did't identify why the user needs a more generic api - what a more generic api would look like ... etc Granted, it was just a quick demonstrative HN post, not an actual user story being handed to an engineer -- but it was very much framed as a incredibly open ended task. I personally have mixed feelings on user stories vs tasks when it comes to the backend. Most managerial folk I've dealt with have an aversion to using anything internal to the company as a 'user' -- taking 'customer' a bit too literally. In the grand scheme of things, I don't care...I've reached an exhaustion point with pedantry around tickets. Is it clear what needs doing? Is it clear what done means? Great.