The title: Chief Token Officer.
The job: own the code and split @gabimonchaβs token anxiety 50/50.
Fair deal. Thrilled to join @formidablebldrs as co-founder. Letβs build π«‘
Meet our new Chief Token Officer!
β
@le_alecs, CTO of https://t.co/HQhVn0PtTc and Codex Ambassador for Romania is joining Formidable Builders as our new Co-founder. He will be the man in charge of the entire codebase and also share @gabimoncha's token anxiety.
Another piece of organizing our @formidablebldrs GTM Skillathon: a live submission board.
The submission skill helped teams submit their projects. The board made it possible to see what had come through.
It pulled from the same GitHub submission records, giving participants and organizers one place to check the state of submissions as the deadline approached.
The lesson Iβd reuse: make the outcome as visible as the submission process. Once someone submits, they should be able to check that it worked.
Follow our Luma calendar for future events: https://t.co/y86j8FwSQP
I became a Codex Ambassador for Romania a few weeks ago. Naturally, one of my first events is in Oxford π¬π§ π .
1 Oct @ @OxfordSBS: Prof. Stephen Roberts highlight talk on what 30 years of Bayesian ML says about today's coding agents, then another talk on agentic engineering with Codex.
Free entry, drinks & $50 credits for everyone who shows up.
Come say hi! @DavideZilli, Bernardo and the rest of AIOI R&D Lab will be there.
Register: https://t.co/d892dJAIqM
Kudos @paw_lean for supporting this!
Weβre sharing a solution to the Navier-Stokes Millennium Prize Problem, one of the deepest problems at the frontier of mathematics.
The proof was produced by a group of agents, using an OpenAI next-generation model significantly more capable than GPT-6 Astra.
The problem concerns whether the description of smooth three-dimensional fluid motion modeled by the Navier-Stokes equations can break down. It has remained unresolved for roughly 90 years.
At our @formidablebldrs GTM Skillathon, βsubmit my projectβ was something you could ask your agent to do.
We gave teams a GitHub template and a submission skill. It checked their files, helped them submit, and returned either an acceptance or what needed fixing.
I evaluated the submissions on my MacBook, so having the same format for everyone mattered.
The lesson Iβd reuse: make submitting easy before people start building. Put the requirements and the checks inside the workflow theyβre already using.
Hereβs the template: https://t.co/b1d5xD6yin
Follow our luma calendar to be the first to know about future events like this: https://t.co/y86j8FwSQP
Built some skills, broke some things, made some friends π€
We took over Builders House for a day and turned it into pure productive chaos
Together with the @OpenAIDevs Codex and @apify, we hosted Europeβs first Agent Skill Hackathon
A lot happened. A lot of skills got shipped!
I just coined a new term:
Agent saturation
/ΛeΙͺdΚΙnt ΛsΓ¦tΚΙΛreΙͺΚΙn/
is a state in vibe coding in which a developer, intending to fix bugs and rapidly build features, begins a session by parallel-prompting multiple agents (typically more than five) using goal, ultrawork, and multi-hour sessions. While each agent performs its task, the developer continues to spawn additional agents in order to work faster. Each new agent produces the impression of working hard. Eventually, so many chats are open that the developer's own context becomes saturated. The developer loses track of which agent is doing what and ends up asking each one what it was working on. By the end of the day, none of the implemented features have been tested, no PRs have been merged, and the code shipped is of far lower quality than what a single session would have produced. The developer realizes that more would have been accomplished by working on a single feature at a time in a single chat session.
@formidablebldrs packed Builders House for Europe's first agent skill hackathon, powered by @OpenAIDevs Codex and @apify!!
π 81 registered. 69 checked in. 34 teams had two and a half hours to turn a real GTM problem into a public, reusable Codex skill.
We also owe several teams a correction.
Our AI evaluation had issues and unfairly flagged some submissions for fabrication.
We reviewed the evidence after the event and updated the podium:
π 1st: Peak AI + agentmarkup @cochinescu@elitepax@AnimaFelixApp
π₯ 2nd: ArminSHaf + Signal Obscura @tudorandre1
π₯ 3rd: Adrian Ciubotaru @sumnuz + Brand Expansion AI
Honorable mention: Missing Answer @andiradulescu
If you participated, watch your inbox for your Codex, OpenAI and Apify credits.
π Shoutout to our amazing juries @MarrComSt@DragomirMiruna@alexgavril!!!
π€ Last but not least, huge kudos to my good friend, co-organizer, AI hyper, builder, co-founder and logistics whiz @gabimoncha!
Thanks again @paw_lean for supporting builders in the region through @OpenAIDevs!
Every winner, skill and repo:
https://t.co/t4YD1G2UaW
Which skill would you put to work first?
Tonight I'm judging the GTM Skillathon at Builders House (AFI Park 1, Bucharest).
The brief: in 2.5 hours, alone or in a pair, build one agent skill that fixes a real go-to-market problem using real web data. No code required. You ship a public GitHub repo, the organizers run it live from one laptop, and every team gets two minutes.
Doors 17:00, build starts 18:00, submissions close 20:30 sharp. The system rejects anything late, so submit early and resubmit as you improve.
Prizes: $2,000 / $500 / $250 in credits plus 3 months of ChatGPT Pro for the top three. Everyone approved gets Codex, OpenAI and Apify credits.
If you're coming, bring one specific GTM problem you've actually had. The narrow ones win. "Find every SaaS in Romania that posted a sales job this month and draft the first email" beats "automate outbound."
Everything submitted stays public under MIT. Don't ship what you wouldn't publish.
Starter and rules: https://t.co/iBY2467JaT Event: https://t.co/8GA8z4zofq
Jury: @DragomirMiruna (Planable), @alexgavril (Promocrat), @MarrComSt (Korena) and me.
LFG π
You claim you value mindfulness but you carry your MacBook everywhere.
Fair.
But Iβve realized burnout isnβt always about working too much.
Sometimes itβs about spending too much time on work you donβt care about.
I took my laptop to the Dolomites. I still opened it. I still worked.
And I genuinely enjoyed it.
Rest matters. Boundaries matter. But so does having work that gives you energy instead of only taking it away.
Before assuming you need to do less, it might be worth asking:
Do I actually like what Iβm doing?
My @OpenAIDevs Ambassador Swag Pack arrived!! So pumped!
Where GPT-6 tho??
Kudos @paw_lean for all the support π€
Stay tuned for the most exciting events in partnership with @OpenAI πͺπ