Sebastian Garces

Senior Software Engineer @ACMEGeneralCorp | US Marine

[Sebastian Garces @gsgarces]

@ashtilawat Sounds familiar

[Sebastian Garces @gsgarces]

@Austen Saw this making rounds a few weeks ago.

https://t.co/EATipvLcVA

[Sebastian Garces @gsgarces]

@gauntletai week 7

Built ChatBridge this week: an AI chat platform where third-party apps run inside the conversation.
One adapter interface, three protocols:
• iframe + postMessage (interactive apps)
• MCP over SSE (dynamic tool discovery)
• REST + OAuth2 (authenticated APIs)
To the LLM they all look the same, just tools it can call.

[Sebastian Garces @gsgarces]

Week 3 @gauntletai

Exploring large legacy codebases is painful.

So I built LegacyLens - a RAG-powered TUI that lets you query them with natural language.

Dataset: GnuCOBOL (a COBOL compiler written in C).

Pipeline:

• Chunked and embedded the entire codebase (took a few iterations to get chunking right)
• Semantic vector retrieval
• Cross-encoder reranking of top results
• LLM synthesis layer

You can ask things like:
“How does GnuCOBOL process command line arguments?”
and it returns the relevant code + explanation with references.

Features:

• Code explanation
• Dependency mapping
• Impact analysis
• Pattern detection
• Bug pattern search
• Business logic extraction
• Documentation generation
• Translation hints

Latency:

Mean: ~3s
Median: ~2.5s

Stack:
• Python TUI
• Vector search + reranking
• Gemini-2.5-flash-lite

Timeline:
Assigned Monday at noon
Submitted Wednesday at midnight.

I also used this week to refine my AI development workflow - built some useful skills, set up a better agent orchestration flow, and improved the loop around reviewing code, generating PRs, and working with git worktrees.

Felt noticeably more productive this week.

[Sebastian Garces @gsgarces]

Week 2 @gauntletai - Final Submission.

Built an agent on a brownfield repo (Ghostfolio) via a drop-in AI widget injected with a <script> tag.

Containerized standalone agent, JWT-forwarded auth, LangGraph + ReAct loop, tool calling for portfolio analysis, holdings, and market lookup.

69 evals covering golden paths, edge cases, multi-step tools, and adversarial prompts.

Learned a ton this week.

[Sebastian Garces @gsgarces]

Day 7 at @gauntletai - first final submission 🚀

Shipped the first full version of our canvas collaboration app.

In the last ~48 hours alone:

Added AI-assisted image → board insertion

Implemented presentation mode

Built undo / redo

What’s wild isn’t just the features — it’s how fast the build → feedback → iterate loop gets when you treat AI as part of the engineering workflow, not a side tool.

Quick Loom walkthrough of the current build: https://t.co/yCqx5NKMA9

Still early, but this is already changing how I think about shipping software.

More to come over the next weeks.

[Sebastian Garces @gsgarces]

Day 5 at @gauntletai

Canvas collaboration prototype done.

Designing, building, and iterating at this speed with AI feels like cheating (it’s not).

Loom walkthrough for the curious 👇

https://t.co/skNmhOyWgL

[Sebastian Garces @gsgarces]

Day 1 at @gauntletai

This app was built in 24 hours.
The pace you can move at with an AI-first approach still blows my mind.

Pumped to have joined - sharing my journey over the next 10 weeks.

https://t.co/vl2ojCsVi6

[Sebastian Garces @gsgarces]

@RockWallBibles It's def doable. When I ordered a Bible I used Figma to help me visualize the different options. This would be an extremely helpful feature. If you need any help, let me know.

[Sebastian Garces @gsgarces]

@Austen I got diagnosed last week - I guess it’s a good thing I’m starting the gauntlet in a few days

[Cursor @cursor_ai]

Read more: https://t.co/F76ABPYfgw

[Sebastian Garces @gsgarces]

@gauntletai Excited to get started

[Sebastian Garces @gsgarces]

@ashtilawat Is this a separate application process than the regular Gauntlet? And why would someone apply to this over the other? Will cohorts be separately or combined?

[Sebastian Garces @gsgarces]

@Austen Will they pay $200k/yr? Gov tends to pay low salaries.

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[Sebastian Garces @gsgarces]

@RealMattCouch This guy is a Marine DI - I was just waiting for the eye balls!

[Sebastian Garces @gsgarces]

@rauchg @vercel @v0 @nextjs Better offline support, service workers, background sync api, pwa, ability to better configure caching strategies… etc…

[Sebastian Garces @gsgarces]

@andrii_sherman @_alexblokh @bloberenober Check constraints and user defined functions would be great.