cpinto

Thanks for participating in the discussion Felix. A big issue for me - not sure if others suffer from this - is that it’s next to impossible to track work in progress, especially with when there are artefacts involved or reports etc. Things that require multi-day work of back and forth and reflection.

Chat is a horrible interface for this, having to scroll up and down across lengthy conversations to try and pick up a thread.

I’m really sorry but I really fail to understand why this massive push to “chatify” everything. A task with its own context and multiple chats feel like a much better approach to work. Even if the work is spawned from a main chat window - eg “Claude we need to work on XYZ” and it creates a task to track this piece of work.

Further, recurring tasks again are really really hard to manage with a chat interface - which of the 10 chats has that question that the recurring task raised?!

And of course all this UX debt will likely stand in your way of building reactive items - ie spawning a task in response to some outside event. Think an inbound email being handled by a prompt that triggers a task and creates a draft response ready for my review and approval. Very hard to do with chat windows.

That’s not feedback, just a non-constructive opinion. As someone else wrote above, if you’re so precious about it then help out the devs of the project and submit design PRs.

I'll offer a different perspective on this: for years we (product/c-suite people) constantly got push back that giving a goal was no longer enough, we had to articulate the path to the goal in excruciating detail.

If I need to think about the solution that hard, I may just as well take it all the way, remove the middleman and get some efficiency back.

There's still a way out of this mess though. All it takes is for folks to take shared ownership for hitting the goal and bring their expertise to the table to help draw the path to the goal.

You’re absolutely right, but just to a point. It should be easy to clearly quantify the desired financial outcome of a sprint, but not of its components. I don’t want to spend a single minute figuring out the financial outcome of a single ticket.

Have you tried writing rules for how you want things done, instead of repeating the same things every time?

what are the plans to support design systems? no one seems to be able to do this. prototyping doesn't happen in a vacuum, I'll always want to use the design system we spent months building in Figma.

How many things on the internet do you really need and that are paid for via advertising?

NullPointerException, ie crash; I assume, but I’m a business guy

exactly! I do not understand the British obsession for preserving insane amounts of crooked-walled buildings with horrible insulation ratings. zero historical interest, 100% NIMBY-ism. then the general populace mopes about the lack of housing, and dreams 15-minute cities without realising the only way to solve both is tear down what’s taking up space and build tall instead.