Alejandro Martinez

@alexito4
561 Followers
248 Following
2.4K Posts
Software Crafter, Mobile Captain at LifeWorks & Fake Youtuber l APIs are UX for developers. | languages geek #swiftlang lover โค๏ธ and self proclaimed async-pro
Webhttps://alejandromp.com
Youtubehttps://www.youtube.com/channel/UCfiBFlVY8s-tmJGDMNCd26w
Linkshttps://links.alejandromp.com
๐Ÿ“š Fictionhttps://pulubiworlds.com

As part of my ongoing series about agent harnesses, I just published โ€œAI doesnโ€™t remember your project, Markdown doesโ€. https://alejandromp.com/development/blog/ai-doesn-t-remember-your-project-markdown-does/

You know when a fresh-chat with AI seems to know things about your project? Well, AI doesn't know it, the harness does the job.
So we build it ourselves to see how it works.
No magic!

AI doesn't remember your project, Markdown does | Alejandro M. P.

In the previous post, Have You Built an Agent Harness Yet?, we built a tiny harness in Swift. We gave it a loop, a prompt, and some tools, and with that it already had most of the features we are used to with modern AI. No magic. Just autocomplete, and a harness deciding what the model gets to see and do.

Alejandro M. P.

Have You Built an Agent Harness Yet?

If you use AI coding tools every day and still think there is some mystical magic behind them, build a tiny agent harness yourself once.

I wrote about it, from chat loop to tools, turns, boundaries, and file edits, all in Swift.

No magic. No frameworks. Just models, loops, context, tools, and engineering.

https://alejandromp.com/development/blog/have-you-built-an-agent-harness-already/

Have You Built an Agent Harness Yet? | Alejandro M. P.

For years I have repeated a thing that I still believe. Every programmer should write a promise library once. I think agent harnesses are the 2026 version of that exercise.

Alejandro M. P.
Today is Sant Jordi.
The day to gift books ๐Ÿ“š and roses ๐ŸŒน.
A day of romance, literature and tradition.
People in the streets, books everywhere, and people carrying roses for their loved ones.

RE: https://mastodon.social/@mattiem/116414622566755635

Wow! So grateful for Matt continuing the detective work! Thanks to him now we have an answer and my brain is happy ๐Ÿ˜Š

As I was updating TCA for Swift 6, a small SwiftUI warning sent me down a much longer rabbit hole than expected.

Closures, @MainActor, multiple SE, Swift 5 vs 6 modes, and the danger of stopping at the first explanation that seems to fit.

A Small SwiftUI Warning and a Long Journey to Understand It
https://alejandromp.com/development/blog/a-small-swiftui-warning-and-a-long-journey-to-understand-it

A Small SwiftUI Warning and a Long Journey to Understand It | Alejandro M. P.

I was migrating to a newer version of The Composable Architecture, which meant there was a list of deprecations to clean up. One of the things on that list was adding InferSendableFromCaptures as an upcoming Swift feature flag across all our package targets.

Alejandro M. P.

And yes, this is about the isolation changes again :P

So concurrency is possible in a single "thread", not parallelism. And we've decided to use "@concurrent" to switch off the main thread.
I know it's my fault, brain is still processing... or better, re-processing ๐Ÿ˜‚

Once, I happily called myself an expert on Swift Concurrency. Not only because I knew how to use it, but because I (thought at least) deeply knew how it worked, its goals and decisions. Now I can't say that anymore ๐Ÿ˜‚

We would like to thank Mega Crit for another year of sponsorship. This time, upgrading to Corporate Platinum! We were supposed to post this earlier but we were all busy playing Slay the Spire 2 ๐Ÿซก

https://fund.godotengine.org/

As I was reading some old threads on the forums, I had a moment of nostalgia that I had to immortalize.
The Swift Concurrency Transition I Learned to Love https://alejandromp.com/development/blog/swift-concurrency-approachability-transition
The Swift Concurrency Transition I Learned to Love | Alejandro M. P.

There was a period during the Swift Evolution Concurrency discussions that I remember very fondly.

Alejandro M. P.
Duh, I think I found it: links like /web/statuses/... seem to open in browser, while canonical links like /@user/id open the app much more reliably on iOS.