~/collaborate
Your product, on real work. Then I write up what held.
I'm Fernando, @ferlogs_ on X: AI software engineer at ioBuilders, founder of Futer, and AI agents in production since early 2026. I partner with companies building AI, developer tools, software and hardware. I use the product on the work I already do, then publish what happened, with the numbers.
- nameFernando · @ferlogs_
- roleAI software engineer @ ioBuilders
- buildsfounder of Futer · co-founder of Luckybites
- runsAI agents in production, read-only
- basedBarcelona, Spain
- xx.com/ferlogs_
- webferlogs.com
- followers656 on X · 7 Oct 2026
- statusopen to partnerships
~/numbers
A small account, growing fast, and every number is public.
Pulled from the public X profile on 7 Oct 2026. Each one can be checked on the profile or on the post it links to. Nothing here is rounded up.
656
followers on X, as of 7 Oct 2026
2,676
views on the best post so far, from 21 Sep 2026
52
replies on that same post: people who wrote back, not only scrolled past
683
posts and replies on the account, since the first post on 31 August
~/followers on X
The account was opened in January and sat empty. The first post went out on 31 August.
- 1
- 538
- 564
- 656
~/published
What I have published, with the numbers next to it.
The personal posts travel furthest. The technical ones reach fewer people, and the right ones: engineers and founders building with AI.
I'm 29. Engineer and founder from Argentina, based in Barcelona. Looking for connecting with people in AI, startups, VC, tech and sports. Let’s find each other.
2,676 views52 replies49 likesintroduction, first takeI’m 29. Solo founder from Spain. Looking to connect with founders & indie hackers.
1,449 views37 replies33 likesfirst post · agents, read-onlyFirst post after eight months of owning this account. I'm Fernando, product engineer in Barcelona. I put AI agents into my team's daily operations: twelve of them, all read-only. None can change production. Also building apps in the gaps. What are you building?
259 views1 reply3 likesAI meetup · BarcelonaI went to an AI meetup in Barcelona expecting to talk about models and agents. Instead, I spent most of the night talking to founders, exits, business ideas and people building outside tech. Funny enough, the most interesting AI conversation was about what happens when you need a technical person to make sure what you built actually holds up. Thx @egraciani!
139 views0 replies6 likesThe long form
Technical articleThe agents on my team cannot change anythingTwelve read-only skills in the daily operations of a regulated backend team, the standards corpus underneath them, and the one rule that made it possible.Open sourceagent-opsRead-only Claude Code skills and a shared standards corpus, for backend teams that run things in production. The scaffolding of the pattern in the article, so another team can lift the shape.And what I build, which is where the testing happens
Futer
Founder · LiveAmateur football gets organised in group chats. Futer replaces that: find a match near you, join with one tap, and the teams come out balanced by rating.
thefuter.com · the full story →
Luckybites
Co-founder · LiveRestaurant promos across Barcelona. Diners claim a deal at a partner venue and collect points for reviewing it afterwards.
luckybites.io · the full story →~/coverage
What I write about, and the shapes it takes.
Topics
AI
Models and assistants, judged by what they do to a real codebase.
AI agents
In the daily operations of a regulated platform since early 2026: permissions, failure modes, and what a lead asks first.
Developer tools
What Futer, Luckybites and this site are built with, and what I dropped along the way.
Productivity
A day job and two live products. The workflow that makes that fit is half the material.
Hardware
The desk that runs all of the above, used for weeks before it gets a verdict.
Building products
From first commit to live, in public: Futer's crews, Luckybites' restaurant side, and the bugs in between.
Formats
Product testing
A test on real work, with the question agreed up front. It ends in a verdict and a list of what I would fix.
X thread · ferlogs.com
Real-world workflows
How a tool fits a working week: the setup, the friction, the parts that stuck.
X thread · ferlogs.comexample →
X posts and threads
Short, in my voice, most days. A thread when the story needs steps.
x.com/ferlogs_example ↗
Technical articles
The long version, with code and diagrams, kept on this site with RSS.
ferlogs.com/writingexample →
Tutorials
Step by step from a clean start, with a repository to follow along.
ferlogs.com · GitHub
Case studies
The whole partnership in five steps, with the numbers of what went out. It stays on this site.
ferlogs.com/collaborate
~/process
Product, real use, content, distribution, feedback.
Five steps, in this order, every time. A case study on this site follows the same five, so you can see what you would get before you write.
- 01
Product
You send access, a build or a device. We agree on the question worth answering, never on the answer.
you get a scoped test, in writing
- 02
Real use
I use it on real work for as long as the question needs: a feature in Futer, a migration, a week of my own workflow. Notes and screenshots as I go.
you get a test on work that exists
- 03
Content
A post, a thread, an article, a tutorial or a case study, written by me from those notes. You check the facts; the verdict stays mine.
you get content in my voice, disclosed
- 04
Distribution
X first, where I post most days. The long version stays on ferlogs.com with RSS, and code goes to GitHub when there is code.
you get the posts, linked and dated
- 05
Feedback
What I would tell a friend on your team: what broke, what confused me, what I would fix first. In private, whatever the post says.
you get a builder's notes on your product
Case studies
None published yet. The first partnership ends up here, written in these five steps, with the numbers of what went out.
What I already use, and where it runs →~/rules
Paid for attention, never for the verdict.
Money buys my time and a fair test. It does not buy a positive post, and the people who follow me can tell the difference.
If a product does not hold up, you hear it first, in private, with the details. Whether anything goes out after that is a conversation; praise I do not mean is not an option.
- opinionmine · not the brand's, not my employer's
- reviewyou check facts before it goes out
- disclosureevery paid or gifted post is labelled
- bad newsyou hear it first, in private
- employerioBuilders systems stay out of it
- verdictnot for sale
~/inquiry
Partnership inquiries. Tell me what you are building.
The form writes the email for you. Nothing is stored and nothing is sent anywhere but your own mail app.