Ercan Aydoğan retweeted
Linus Torvalds let Claude Code fix the Linux page cache. Then reviewers found a race. thenewstack.io/torvalds-clau…
Ercan Aydoğan retweeted
Introducing PGSync 🐘
Real-time PostgreSQL replication. FREE. OSS
Built in Rust. 🦀
Postgres 16 / 17 / 18.
No extensions. No triggers. No complex setup.
→ snapshot
→ replicate
→ stream changes
→ track WAL
→ recover from crashes
→ resume automatically
→ keep databases in sync
~15 MB RAM during streaming.
Built for developers. Built for AI agents.
Open source.
xitter.gq/alxshp/status/21078790…
Introducing pgrun.dev 🐘
🚀 KILL your local database. NOW!
Stop creating local and staging databases manually.
That’s the old way. The new way:
→ Every agent gets its own Postgres.
→ Every PR gets its own Postgres.
→ Every CI run gets its own Postgres.
Created in seconds.
Used.
Destroyed.
Databases should be disposable.
xitter.gq/alxshp/status/21024376…
Ercan Aydoğan retweeted
Want to see what tok/s you'd get? Or what the best model would be if you did buy that expensive graphics card?
Now you can. Benchmark mode now in llmfit.
Based off real user data. github.com/AlexsJones/llmfit
Ercan Aydoğan retweeted
Three days ago I left autoresearch tuning nanochat for ~2 days on depth=12 model. It found ~20 changes that improved the validation loss. I tested these changes yesterday and all of them were additive and transferred to larger (depth=24) models. Stacking up all of these changes, today I measured that the leaderboard's "Time to GPT-2" drops from 2.02 hours to 1.80 hours (~11% improvement), this will be the new leaderboard entry. So yes, these are real improvements and they make an actual difference. I am mildly surprised that my very first naive attempt already worked this well on top of what I thought was already a fairly manually well-tuned project.
This is a first for me because I am very used to doing the iterative optimization of neural network training manually. You come up with ideas, you implement them, you check if they work (better validation loss), you come up with new ideas based on that, you read some papers for inspiration, etc etc. This is the bread and butter of what I do daily for 2 decades. Seeing the agent do this entire workflow end-to-end and all by itself as it worked through approx. 700 changes autonomously is wild. It really looked at the sequence of results of experiments and used that to plan the next ones. It's not novel, ground-breaking "research" (yet), but all the adjustments are "real", I didn't find them manually previously, and they stack up and actually improved nanochat. Among the bigger things e.g.:
- It noticed an oversight that my parameterless QKnorm didn't have a scaler multiplier attached, so my attention was too diffuse. The agent found multipliers to sharpen it, pointing to future work.
- It found that the Value Embeddings really like regularization and I wasn't applying any (oops).
- It found that my banded attention was too conservative (i forgot to tune it).
- It found that AdamW betas were all messed up.
- It tuned the weight decay schedule.
- It tuned the network initialization.
This is on top of all the tuning I've already done over a good amount of time. The exact commit is here, from this "round 1" of autoresearch. I am going to kick off "round 2", and in parallel I am looking at how multiple agents can collaborate to unlock parallelism.
github.com/karpathy/nanochat…
All LLM frontier labs will do this. It's the final boss battle. It's a lot more complex at scale of course - you don't just have a single train. py file to tune. But doing it is "just engineering" and it's going to work. You spin up a swarm of agents, you have them collaborate to tune smaller models, you promote the most promising ideas to increasingly larger scales, and humans (optionally) contribute on the edges.
And more generally, *any* metric you care about that is reasonably efficient to evaluate (or that has more efficient proxy metrics such as training a smaller network) can be autoresearched by an agent swarm. It's worth thinking about whether your problem falls into this bucket too.
Ercan Aydoğan retweeted
CONTROL
Atomic governor
Transactional guardrails for billing, state coordination, and execution policy.
All for safe exucution. Available now via clawstack.dev
#OpenClaw #agents #ai #mcp
Happy Fridays builders.
If you guys build something around #openclaw
I am providing / building secure sandbox, agent fleet platform. I love to hear Feedback.
@clawstackdev
Even you can get free env if you join beta list.
Feedback is the King.
Happy Fridays builders.
If you guys build something around #openclaw
I am providing / building secure sandbox, agent fleet platform. I love to hear Feedback.
clawstack.dev
Even you can get free env if you join beta list.
Feedback is the King.
Ercan Aydoğan retweeted
Stop building on shared clouds. Run agent workloads on dedicated hardware with atomic state, zero-trust backhaul, and deterministic rollbacks. #OpenClaw #clawstack
What is going on with claude code.
Is this influencer paid to ads.
Now everybody sharing their magical claude experience like;
“ I am using it, finish our one year coding to 1 hour.”
During my AI #Receptionist project, switched Excel to tracescore.io
#Lead enrichment and #scoring.
Includes Google maps, LinkedIn, spending research. It has #AI based sector search. You don’t need to ask search this website. It is doing for you auto.
During my AI #Receptionist project, switched Excel to https:://tracescore.io
#Lead enrichment and #scoring.
Includes Google maps, LinkedIn, spending research. It has #AI based sector search. You don’t need to ask search this website. It is doing for you auto.
Ercan Aydoğan retweeted
my linkedin engagement tanked for 3 weeks
went from 100K+ views per post to 8K
tried everything - different hooks, different formats, nothing worked
then i spent 2 hours analyzing competitors
here's what i did:
went to apify
found twitter scraper tool
entered 3 competitors who were crushing it
downloaded their last 50 tweets as JSON
uploaded to claude project
asked one question:
"why are they getting massive engagement and i'm not?"
AI came back with brutal insights:
"your hooks have become formulaic - 'most people do X wrong'
theirs are more varied and pattern-interrupt"
"you're explaining concepts
they're telling stories with lessons embedded"
"your posts are educational
theirs create emotional reactions first, education second"
next day i posted using their patterns
result: 43K impressions, back to normal
here's the system you can use:
step 1: identify who's winning
not who you like
who's actually getting results in YOUR space
step 2: scrape their content
apify for twitter/linkedin/instagram
$39/month plan is enough
download last 50-100 posts
step 3: strategic fields only
don't download everything
just: full text, engagement metrics, date
keep AI's attention focused
step 4: upload to claude
create project called "competitor analysis"
upload the JSON file
step 5: ask the right questions
"analyze engagement patterns - what's working?"
"compare their hooks to mine [paste your posts]"
"what are they doing that i'm not?"
step 6: apply immediately
don't just learn
implement same day
the beauty of this:
you're not guessing why competitors perform better
you're using AI to systematically reverse engineer what works
i do this monthly now
scrape top 5 performers in my space
upload to claude
get pattern analysis
test their approaches
my engagement has 3x'd in 6 months
because i'm not creating content in a vacuum
i'm learning from what the market already proved works
works for any platform:
- linkedin posts
- twitter threads
- instagram captions
- youtube titles
find who's winning
scrape their content
reverse engineer the patterns
apply to your business
Ercan Aydoğan retweeted
Big moment for Postgres!
AI coding tools have been surprisingly bad at writing Postgres code.
Not because the models are dumb, but because of how they learned SQL in the first place.
LLMs are trained on the internet, which is full of outdated Stack Overflow answers and quick-fix tutorials.
So when you ask an AI to generate a schema, it gives you something that technically runs but misses decades of Postgres evolution, like:
- No GENERATED ALWAYS AS IDENTITY (added in PG10)
- No expression or partial indexes
- No NULLS NOT DISTINCT (PG15)
- Missing CHECK constraints and proper foreign keys
- Generic naming that tells you nothing
But this is actually a solvable problem.
You can teach AI tools to write better Postgres by giving them access to the right documentation at inference time.
This exact solution is actually implemented in the newly released pg-aiguide by @TigerDatabase, which is an open-source MCP server that provides coding tools access to 35 years of Postgres expertise.
In a gist, the MCP server enables:
- Semantic search over the official PostgreSQL manual (version-aware, so it knows PG14 vs PG17 differences)
- Curated skills with opinionated best practices for schema design, indexing, and constraints.
I ran an experiment with Claude Code to see how well this works, and worked with the team to put this together.
Prompt: "Generate a schema for an e-commerce site twice, one with the MCP server disabled, one with it enabled. Finally, run an assessment to compare the generated schemas."
The run with the MCP server led to:
- 420% more indexes (including partial and expression indexes)
- 235% more constraints
- 60% more tables (proper normalization)
- 11 automation functions and triggers
- Modern PG17 patterns throughout
The MCP-assisted schema had proper data integrity, performance optimizations baked in, and followed naming conventions that actually make sense in production.
pg-aiguide works with Claude Code, Cursor, VS Code, and any MCP-compatible tool.
It's free and fully open source.
I have shared the repo in the replies!
“Stop building AI Wrappers. Start building Vertical Infrastructure.”
I spent my Saturday refactoring my entire AI Receptionist stack. Why? Because ‘Script Kiddie’ code dies at Customer #10.
I moved a messy Python loop to a Multi-Tenant Go Architecture.
#saas #buildinpublic





















