From the article: > I stress that it’s not specifically JIRA itself which is guilty of this. All of the above is implicit in the notion of reducing software ar

From the article: > I stress that it’s not specifically JIRA itself which is guilty of this. All of the above is implicit in the notion of reducing software architecture and development to a set of “tickets.” JIRA’s great sin is only that of being the most successful and widespread ticketing system. The notion of specifying a software project with a set of tickets is itself the enemy. Hope that saves ppl from this terrible clickbait