Tung Nguyen

Check out this short, clear, and helpful video by Matt Pocock on using the Red -> Green -> Refactor approach of Test-Driven Development (TDD) with Claude Code. I've been using this approach, and find it to work really well. I'll be updating my workflow with Claude Skills to keep Claude Code more focused and not try to create too many tests at a time. Have you tried this approach?

4

I thought this was a good and very reasonable talk by Eleanor Millman on how to prioritize projects for a platform engineering team: https://lnkd.in/gaYtUHRH A few insights I took from it: - Unlike product features which can be more directly tied to revenue, platform engineering work is a couple steps removed. But that doesn't mean it's unimportant! Far from it, platform engineering projects can make everyone at the company more efficient, able to produce higher quality software, etc. - While "urgency" is always going to be a factor, you don't want to just be putting out fires, you want be able to prioritize work which is "high impact" ... even if that impact isn't felt immediately. - Good rule of thumb: prioritize "highest impact for lowest effort". - The talk has some ideas on what factors to choose for impact, and how to blend them. For instance "speed of development" is one factor, "cloud cost optimization" might be another. The weighting of different impact factors can change over time, depending on the needs of the business. I would say that a lot of companies don't have much methodology here but I can really see the value in codifying it. You can always change the methodology or the weighting if it's spitting out results that don't pass the smell test or you really feel it is leading the company astray. Clarity can give the org more freedom to put resources behind projects that would otherwise never be taken on. When things are unclear, prioritization still happens implicitly, but the decisions tend to be a lot more random and fear-based and the org is worse off as a result.

15

3 Comments

During the "Ambient Agents" meetup last week, Brace Sproul gave us a walkthrough of Open SWE, a coding agent built on Langgraph. Open SWE monitors GitHub issues. When it gets a new one assigned, it kicks off a multi-agent architecture with a Manager, Planner, and Programmer. It can receive messages from users at any time during the process and incorporate them into the state. Check out the slides for diagrams explaining each agent: https://lnkd.in/g3PnNHqG And the code: https://lnkd.in/gY68TKYy I found the takeaways really interesting: * Summarization is hard: Especially with code changes that can get quite long, you literally can't send the entire context history to the LLM, and highly detailed old diffs may distract it. IIRC, the agent sends the last 20 messages, and summarizes the changes before. * Agentic > hard coded: Open SWE tends to use the agentic approach of "here are your tools, pick which one to use" for almost all tasks. Except for one.. * Explicit error handling: When an error happens, Open SWE stops everything and focuses on resolving the error. Otherwise, it could get too far afield and be unable to get back to a good place to solve the error. (Hopefully I didn't mis-represent anything I heard!) #Langchain #Langgraph

93

3 Comments

okay here is a wild chain: Claude Code builds, secures, plans, improved it Open Claw runs it Codex is what Open Claw runs Codex writes software Cron jobs manage AARP, security, api cost tracking/alterts Claude Code re-assess outcomes, redesigns skills, knowledge, Open Claw agents improve. Write new and more code. Pretty crazy tech stack!

5

1 Comment

Breaking: Claude Code just introduced Sub-Agents You can run your own custom Agents. Using the /agent command Based on an agent file format, written in markdown. Custom system prompts, custom tools. Making it very easy to create your own agents. Previously I made a REST api for Claude Code, meaning so I could script things from a browser. Now, I can create teams of sub agents, working together on a problem. More info on the feature: https://lnkd.in/g3H4_q7E You would think they are paying me, I'm just hyped because this allows Spec Driven Development to be even easier.

73

23 Comments

"How much does custom software cost?" Here's the real answer (with sources): → Simple MVP: $15K - $50K → Mid-complexity: $50K - $150K → Enterprise: $150K - $500K+ (Source: FullStack Labs: https://lnkd.in/e3BpwwP6, Jellyfish Technologies: https://lnkd.in/eBsR8MUK) But here's what most people miss: Scope creep adds 20-50% to most projects. The fix? Clear requirements + the right partner. At Iron Forge Apps, we use AI-powered workflows to cut delivery time by 40%—without cutting corners. Full breakdown with hourly rates, regional pricing, and real examples 👇 https://lnkd.in/evzjdvBv

4

The ROI isn’t just speed—it’s transfer. Prompting patterns I used for: - Survey design → also work for interview guides. - Terraform reviews → also work for policy checks. - Meeting digests → also work for PRDs. Learn once, apply everywhere.

5