Comment by JamesSwift

17 days ago

I think its clear the team is drowning. They are just trying to keep their head above water. They have massive adoption, high churn in the underlying models, and unlimited numbers of github issues opened every day.

Should it be solved by now? Yes. If anyone on the team is dogfooding it in a typical tmux environment, its painful. But lets give them some leeway here.

9 comments

JamesSwift

Reply
jjayj  17 days ago

This is a massive commercial product with a serious issue (everyone knows about the flickering) that hasn't been solved for months now. I don't think leeway is warranted.

catlifeonmars  17 days ago

To your point, I’d say the dev team deserves some leeway, but the employer (Anthropic) is raking in the $$$ and doesn’t deserve any sympathy for underfunding the CC team.

  • JamesSwift  16 days ago

    Do you suggest hiring 1000 extra devs to close the issues? At some point, it doesnt actually scale. Whos to say they havent hit that limit already?

    • catlifeonmars  16 days ago

      Funding doesn’t _necessarily_ mean hiring more devs.

      To your point about hiring 1000 devs not solving anything: I agree. For a project of this scope, you’re probably going to peak at one or two 3 person teams with at least one principal dev per team with deep experience in the tech stack and in architecting/building TUIs in general. I would hope their devs are making a relatively lucrative salary too, to attract talent.

      I have no idea what the internal structure is so this is just pure speculation: judging by the backlog of issues on their GH, they could use better community management and developer relations. I suspect they’re riding on the existing hype/community interest to fulfill these functions but that only provides a piece of the puzzle.

      1 reply →

dymk  17 days ago

Nobody is blaming the individual engineers here. The team as a whole can take the blame.