{ BBA ~ MBA | Gamer 🎮 } Opinions are my own. Co-founder @ThalozUS 🇺🇦 💙💛 #StandWithUkraine #NearshoreTalent #Recruiting #AI_Teams
Montevideo, Uruguay
Joined September 2007
- Tweets988
- Following1.8K
- Followers440
- Likes2.4K
Pablo García retweeted
now that we all agreed to not review most of the code any more, CI became the next bottleneck
at agent speed, if our CI pipeline is simply "run all the build, lint, tests", it'll become a major slow down
here are a few things i suggest for how to optimize:
1. balance load between CI and CD
CI protects main branch. CD protects production. if you can tolerate some delay in deploying your main branch to production, then you can do less in CI and do more in CD
for example, for a cross platform app i made my CI pipeline skip most mac and windows tests because linux already covered the same functionality
the tradeoff is occasionally i'd catch a mac or windows-only bug in CD before release, but in exchange, my CI pipeline became 15x faster - well worth it
2. modularize your codebase such that changes are isolated
then you can make your CI only run build, lint, test for the module being touched
this requires careful consideration for cross-module protocols. they should likely be their own modules, so when they do change, you know you probably need to test all dependent modules
3. for large modules, invest in test selection
in CI, try to only run tests that are covering the areas being changed. doing accurate test selection is not easy though, and often requires continuous tuning
i have a nightly loop specifically doing audit of past test runs and tweak my test selection to be more accurate. a big codebase of mine got pretty good at this - 20x faster CI compared to running all tests, and almost never miss any real problem
🤡🤡
The r/OpenSource subreddit has officially banned anything using AI. In any way. Violators will be permanently banned.
Which means… r/OpenSource will ban anyone submitting anything that, in any way, involves… the Linux kernel.
reddit.com/r/opensource/comm…
Pablo García retweeted
I kid you not, sometimes I talk to an AI and they are stunned by my insight into architecture
Oh boy, went from 20 PRs a day to ~120.
Not on @poteto levels but after a couple perf iterations and getting a beefy dedicated worker box it should jump again.
Fun times.
Pablo García retweeted
Hey, it is Wednesday
OpenCode hacked
eMudra had picked a private key value of 4, thus everything is now deemed unsafe.
PHP, running 70% of the internet, has an insane hack...
Happy getting internet getting humped day
Pablo García retweeted
Great.. now i have to invest into claric a new system one model for extracting values...
STOP RELEASING COOL NEW THINGS, ITS A HUGE PAIN IN THE ASS
Pablo García retweeted
Since the American President announced the energy ceasefire a week ago, Russia has deliberately attacked Ukraine’s energy and oil and gas sectors 76 times. Last night alone, there were strikes on substations in the Vinnytsia, Zhytomyr, Khmelnytskyi, and Odesa regions. Tens of thousands of families remain without power. Energy workers and repair crews are working virtually around the clock to restore electricity supply. Overnight, the Russians also struck residential buildings in our regions. As of now, 12 people have been reported injured, including two children. Two people have been killed. My condolences to their families and loved ones. This morning, there was a strike on an agricultural enterprise in Volyn. All necessary services are working at the site.
In total, over this past week, the Russians have attacked Ukraine with almost 2,700 attack drones, 1,700 aerial bombs, and 66 missiles, most of them ballistic. The main targets of these strikes are energy facilities – the Russians are trying to cause a blackout. And America should see that Russia is not taking any reciprocal steps in response to sanctions relief or agreements. On the contrary, they take every signal of an opportunity to make money as proof that their bet on war is paying off and they can keep fighting. It is because of this position of Russia’s that the war continues, not because Ukraine is rightfully defending itself. It is Russia that must face pressure for peace to have a chance. Thank you to everyone who understands this and helps.
My god how many ads on "excuse me Jev can what?" "Anthropic just drop a course" do I have to ensure?
Block
Block
Block
🙄
Pablo García retweeted
I no longer see any compelling reason to believe that taste is some permanent boundary LLMs won’t cross. It’s already happening.
Pablo García retweeted
I think I have experienced “AGI”…
Just did a 30-minute “phone call” with @bot. Together we got back to about 20 emails, organised my calendar for the week, wrote a proposal for my team, ordered lunch for my family, booked (and paid for) a hotel, and arranged a cab to the airport. It also gave me some great advice along the way.
Did it all 100% “hands free” with my baby fast asleep on my chest.
If this is what life is like with superintelligence, I am all in.
Pablo García retweeted
We were able to fine tune an open weight model (Qwen3.5-9B) on proprietary internal data at @coinbase, and it out performed frontier models, at much lower cost and speed, for a specialized task (fraud prevention in this case).
I think we'll see more of this pattern inside companies. The frontier models are amazing generalists. But increasingly you'll see specialist models out perform on more narrow tasks, either working on teams, or by themselves.
We're making it easy to fine tune models internally for our employees. We even have a skill for it in our internal harness that makes it easy to spin these up and start training them:
"/fine-tune-and-serve-llm I want to fine-tune Qwen for payments risk review. help me get started"
I imagine we'll have some backend services that could be replaced entirely by this new architecture.
Pablo García retweeted
Introducing ChatGPT for Dishwashing
GPT-6 achieves state-of-the-art results on dishwashing benchmarks for long-running jobs and difficult stains.
The Navier–Stokes Millennium Prize Problem is a $1 million challenge about whether the equations describing fluid motion can break down. In this video, I accidentally found a counter-example while trying to optimize my dishwasher. But in reality, OpenAI used 10,000 AI agents to find a proof in 88 hours: openai.com/index/navier-stok…
Parody of the original GPT-6 Astra ad
@OpenAI #ChatGPT_Partner #chatgpt
Credits:
Written and Directed by Joma
Co-Writer - Henry Connor Coan IV @coan_henry
Production by Dauntlus Studios @dauntlus.studios
Producer/Co-Director - Marcus Liew @dauntlus
Camera Operator - Amos Lee @amoselijahlee
Art Director - Alethea Soo @aletheasoo
Art Assistant - Alicia Lim @aliciatkl_
Assistant Editor - GPT-6 Astra
Music: Tensions Run High by Soundridemusic
youtube.com/watch?v=Ly9H63SL…
Pablo García retweeted
everything i know about managing agents i learned from the amazing programmers and computer scientists that came before
constraints in your codebase are freeing for both humans and agents! this has always been true, but if you were a small dev team you likely never had to think that deeply because you could trust your fellow programmers to write code and review well
but large companies have had to solve this problem since even before agents. because before you had agent slop, you had human slop. lots of engineers wrote bad code out of necessity (eg backend engineer forced to write frontend or reverse). the solution to this was constraints: lint rules, smarter compilers and diagnostics, high quality tests, investments into observability, and so on
the arrival of agents just means that big company problems are now everyone's problems. the good news is that none of this is really that novel: it's just good engineering
youtube.com/watch?v=GqmsQeSz…
This.
The end user does not care about your pitch-perfect code.
It solves a need or it does not.
Whatever is more efficient at doing that wins. We like it or not.
codebases have always contained slop. we have always been okay with this because code rarely needs to be perfect, outside of mission critical "hard" (eg embedded) software.
swe is a unique form of engineering because you're often building something that constantly evolves and is almost organic - user tastes change, your mental models evolve, and features come and go.
admittedly, i and many others who've been coding for a long time were initially (like back in 2024) skeptical that agents would write production code. "but what about all the slop that would enter our beautiful codebase?".
well, even before, we had human slop, and there was a lot of it! if we're being truthful, most people call "code i didn't write" slop. the reality is that 99% of people (i include myself in that number) don't even know what Good Code looks like, let alone be capable of writing it. i would propose that Good Code is:
• correct
• bug free
• fast and cost efficient to run
it has always been exceedingly difficult and expensive to write truly Good Code, because for the longest time (maybe @bendlang will change that), code was not something you could cheaply and formally guarantee to have all 3 of these properties. this is why writing hard software is much more difficult and expensive, because depending on the use case, you may only get one chance and so you have to be right from the start.
but the vast majority of software we use does not need to be Good Code to provide value to users. in fact, it is very likely that most software we use is not formally verifiable! we accepted some bugs in exchange for velocity and progress, so we rely on tests and o11y instead and have adopted a more incremental approach. this is a good thing!
agents help us move faster, and if you're open to the idea, are capable of helping us write better code. it won't be Good Code (that is still expensive), but it is likely to be much better on average at scale.
the new craft of swe is to figure out how to do this. it's your job now! if your productivity with and without agents is not significantly different, you're doing something wrong. but it's not too late to embrace it and use it as an opportunity to learn a whole new skill tree