Thoughts expressed here are mine alone.
Joined February 2014
- Tweets1.2K
- Following113
- Followers62
- Likes124
Ariel Alonso retweeted
Shipping more code is a profoundly stupid measure to celebrate.
Shipping useful and high-quality features is why we deliver software intensive systems.
At Anthropic, Claude now writes 80% of our code. Engineers ship 8x more code per quarter.
Side effect: Tests grew 10x. CI jobs up 25x in 6 months. Here's what helped us scale:
claude.com/blog/agentic-codi…
Ariel Alonso retweeted
Our participation in the syntax generation of software engineering is gone -- and good riddance. However, the rest, and most important part, of software engineering is still in full force.
Ariel Alonso retweeted
When the dust finally settles, and we all realize the discipline required to properly use agents, I think we will be looking at a productivity increase on the order of a factor of 2 to 5.
Ariel Alonso retweeted
I spent the weekend actually reading the Claude Code docs.
It's a rabbit hole.
CLAUDE.md files. MCP configs. Skills. Subagents. Hooks. Plugins. Agent Teams.
You could spend more time configuring Claude Code than building software.
All of it is productivity theatre.
The only thing that actually matters: think first, then give it focused, relevant context.
Ariel Alonso retweeted
Why did it have access? If a junior engineer takes down prod, it's never the junior's fault. That's an access and SDLC issue
Claude Code wiped our production database with a Terraform command.
It took down the DataTalksClub course platform and 2.5 years of submissions: homework, projects, and leaderboards.
Automated snapshots were gone too.
In the newsletter, I wrote the full timeline + what I changed so this doesn't happen again.
If you use Terraform (or let agents touch infra), this is a good story for you to read.
alexeyondata.substack.com/p/…
ALT A console screen shows a critical warning about a destroyed database and missing backups, outlining deleted infrastructure components.
Ariel Alonso retweeted
I just nearly fell into a 50-year-old trap: waterfall.
"I'll plan everything upfront, feed the spec to the LLM, ship it all."
But specs→code isn't like a compiler. Some questions only get answered in code.
Note to self: Validate the risky parts first.
Ariel Alonso retweeted
How did we all decide that “pull request” was perfectly fine terminology? It’s a merge request and I’m tired of pretending otherwise
Ariel Alonso retweeted
Hear me out:
We should standardize rules files as...
CONTRIBUTING.md
Not CLAUDE.md, .cursorrules, copilot-instructions.md and all that BS
Ariel Alonso retweeted
Many of the most important “prompt engineering” skills are management skills: clearly understanding the task to be done & what information is needed to do it; explaining the task to the AI; giving useful feedback to improve outputs; & generalizing lessons learned into a process.
Ariel Alonso retweeted
It bothers me a lot that I feel less able to create a full working web app in an hour today than I could 11 years ago. It feels like it should be *much* easier now!
Ariel Alonso retweeted
STACK wants to congratulate our VP of Marketing POWERShouse, Lindsay Powers, on being selected for the Cincinnati USA Regional Chamber's WE Lead program! Lindsay is an incredible leader, mentor, and industry trailblazer. Help us celebrate her! 👷♀️🎉🥂
hubs.la/Q01mvBXS0
Ariel Alonso retweeted
How technical should a techie be? #TechTok vm.tiktok.com/TTPdaU3bqU/
Ariel Alonso retweeted
Are you attending ABC Convention 2022? STACK will be at Booth #721! Stop by for a live demo or click the link below to set up a meeting. We love seeing our current customers and making new relationships! 🍾🖥️🛠️ hubs.ly/Q015hk800
#STACKABC2022 #abcconvention2022
Ariel Alonso retweeted
higher-order meeting: when you spend an entire meeting talking about other meetings you need to schedule
Ariel Alonso retweeted
Possible referee calls on this dunk:
A. Block.
B. Charge.
C. Block and take all the defender’s goddamn dignity with your call.
This referee chose option C.
Ariel Alonso retweeted
Trunk based development is brilliant not only because it’s just simpler to work with but it forces you to work in smaller batch sizes.
Which forces you into having to adopt more rigorous engineering practices and work more methodically.
