Hard disagree. User stories are a great pithy way to describe a high-level need with a supporting reason. They usually take only a few minutes to write quite a

Hard disagree. User stories are a great pithy way to describe a high-level need with a supporting reason. They usually take only a few minutes to write quite a few and in group exercises we've been able to generate many very rapidly. The task/ticket however (and work to be done) is separate and derived from the user story. This can dive into architecture choices, _why_ this solution and _why not_ that one, specific implementation details and steps to achieve those. Both types have their pros and cons and work best when used together because they serve different people and different goals. Don't write something off just because you saw a post make it to HN p.1 - try things out for yourself and decide based on _your_ team and _your_ needs.