onder_ceylan
This is not sustainable for the industry. People are already burning out, quitting the profession, or chasing an exit.
Agentic software development lifecycle should be covered completely by the agents for day to day work, where people build and maintain the specs, guardrails, and agentic engineering systems around the agents.
I've built https://letsship.ai with this vision, and it's the only sustainable way of working for me.
I'm interested to see the total inference cost of a ticket type, that's why total cost is compared. Even though most of the cost is there in other stages, there's still huge difference even with one variable configuration in the loop.
The cost of each builder is also shown in mission breakdown, but good feedback for extending some of the tables, thanks!
SHIP users configure each specialist agent with a pointed harness and a model of choice, along with skills, memory and any tool integration. These agents then are operated to work together and deliver a reviewed, gated, tested outcome.
Show HN: Ship – The operating system for agentic engineering
Ask HN: Is anyone interested in engineering focused coding agent course?
I've built a Claude Code course initially to help out my friends and colleagues to get more efficient with coding agents - see it at https://code-agents.aiI published the content I was telling to my circle as a docs style course material and so far people seem uninterested. And, I would like to understand why. Curious to hear your thoughts on this.* Do you think that course content as...
If you're an engineer, tell me why you're NOT interested in such a course/format please.