It's because we developers don't get to see the big picture anymore and it's not our fault. Software development stopped being a craft. Now it's just an assembly line.
Some product owner who barely understands the tech hands you a Jira ticket. It has a list of requirements, and your job is to make the ticket go away. You don't know why you're building it. You don't talk to the person who will use it. Your only job is to close the ticket.
Every single bug you listed? I can tell you exactly where it came from.
Of-course Chrome's tab groups are broken. The team was measured on shipping the feature, not making it work. Fixing it is tech debt, and tech debt never gets prioritized over the next shiny new thing on the roadmap.
Slack shitting the bed when you change network? That's the price of "moving fast and breaking things," except we never go back to fix them. We just live with the rubble.
And the stuff that seems intentionally hostile. That's what happens when the goal is just juicing some engagement metric. The user's sanity is never part of that equation.
Don't even get me started on the "Agile" theater. We do all the meetings, the stand-ups, the retros. It's a cargo cult. It's a way for management to pretend there's a process while they just demand more features, faster. And when stuff breaks, they blame us for not "trusting the process."
So no, you're not just yelling at clouds. You're seeing exactly what this broken factory produces every day. Your frustration is completely justified.
As soon as I saw the announcement , tried again and created a working design skill that can create design artifacts following the brand guidelines.
While these improvements seem incremental, they have a compounding effect on usefulness.
My AI doomsday calculator just got decremented by anothet 6 months.