Earlier quoted context omitted.
> has our executive team furious And yet they will continue to spend wheelbarrows full of money with Anthropic because they want so badly to reach the point where they can fire you.
I think there is alot of baseless fury behind your words, but my regular interactions with my leadership dont lead me to think they have the end goal of replacing labor. We're blessed to have leadership with technical backgrounds, so the tools are regarded more as significant intelligence enhancers of already exceptionally smart engineers, rather than replacements. Doesnt seem to us to be wheelbarrows of money, when…
Claude.ai unavailable and elevated errors on the API
131–140 of 277 posts
Re: Claude.ai unavailable and elevated errors on the API
#132Re: Claude.ai unavailable and elevated errors on the API
#133We're officially down to one 9 of uptime over last 90 days: https://status.claude.com
Re: Claude.ai unavailable and elevated errors on the API
#134If this can happen to Anthropic, imagine all the companies building on top of Claude Code for live products. Hopefully the industry is learning that competent problem solving human engineers are still very much needed when you have increasingly deceptive non-deterministic genies running your production stack.
Re: Claude.ai unavailable and elevated errors on the API
#135Re: Claude.ai unavailable and elevated errors on the API
#136Re: Claude.ai unavailable and elevated errors on the API
#137Re: Claude.ai unavailable and elevated errors on the API
#138The spend at my organization has reached beyond the $200,000 per month level on Anthropic's enterprise tier. The amount of outages we have had over these past few months are astounding and coupled with their horrendous support it has our executive team furious. its alot of money to be spending for a single 9 of reliablility.
Not sure how much of a productivity gain a 2.5 million per year it is?
Re: Claude.ai unavailable and elevated errors on the API
#139Earlier quoted context omitted.
Our expense is roughly around 12.3 software developers when you break it down across all people related expenses. But we've spent alot of time and energy prior to this focusing on our ability to measure our software development output across multiple teams. The delivery improvements are not evenly applied across all teams, but the increases that we have seen suggest a better ROI than if we had hired 12 developers.
I guess if you think about your teammates as purely inputs and outputs and not people that can improve and contribute in the workplace in other ways.
You will also find that many problems in the harder sciences do not get easier by throwing more bodies at them. Comments like these remind me that some project managers think they'd be able to delivery a baby in 1 month if they simply had 9 women.
Re: Claude.ai unavailable and elevated errors on the API
#140Earlier quoted context omitted.
I think there is alot of baseless fury behind your words, but my regular interactions with my leadership dont lead me to think they have the end goal of replacing labor. We're blessed to have leadership with technical backgrounds, so the tools are regarded more as significant intelligence enhancers of already exceptionally smart engineers, rather than replacements. Doesnt seem to us to be wheelbarrows of money, when…
Not ever hiring juniors and eventually mids is just replacing labor with extra steps.