We’re introducing Dynamic Workers, which allow you to execute AI-generated code in secure, lightweight isolates. This approach is 100 times faster than traditional containers. https://t.co/c36Vkb7I0R
“It’s reasonable that your 3 person team can deliver this within 2 months, by trimming scope and focusing on the core functionality.”
Oh Claude, my poor friend, you are the “3 person team” and the usage budget just got reset!
@forgebitz@alecsiemerink Hi Klaas, my question would be: how do your customers track the value of citations? With classic SEO, you had this pipeline "keyword A -> ranking #1 brings X impressions -> this results in Y clicks -> this leads to Z signups". Are you able to track citations in a similar way?
These 4 images will tell you all that you need to know about #Atlassian.
1) -257M in 2025, 2) 10K shows extremely high costs in admin, R&D, and employe comp, 3) in the 10K they spoke of growing HC even further. 4) Stock price will never recover
The maintainer had to close a total 14 AI PRs for this issue. Most of them had a "🤖 Generated with Claude Code" in the description. AI Slopocalypse.
@steipete keeping it real as always:
https://t.co/b1MwE6C1wK
You can now use Claude Code and GitHub CLI directly inside Perplexity Computer.
We gave it an open issue on Openclaw. Computer:
→ Forked the repo
→ Wrote a plan to fix the bug
→ Opened Claude Code and implemented it
→ Submitted a PR via GitHub CLI
Each LOC makes only ~$2 in profit a month. By refactoring, @levelsio could reduce LOC and boost his profit-per-LOC. That would show everyone he’s a super duper, hardcore software engineer 😆
Programming was deeply satisfying work to me. Work for hours/days before getting the payoff of the code working well on your machine. I’m feeling so much friction now to open the editor and do this kind of task by hand, but also increasingly depressed with the nature of work in an AI assisted dev workflow. Back and forth prompting seems to eat at my soul. Need to find a balance that brings back some of the toil.