I build software with AI in a practical way. No hype.
Morbegno, Lombardia
Joined June 2009
- Tweets791
- Following191
- Followers95
- Likes1.3K
This article reminds me of the good old days when software was easy to understand.
sheets.works/data-viz/holdin…
Martedì 3 novembre alle 19:00 torna il PUG Sondrio, questa volta a Morbegno.
Mattia De Leo di TeamSystem ci racconta perché "L'AI in produzione è un gioco di squadra": piattaforma e Forward Deployed Engineer.
luma.com/smjtw39f
The new Xbox Nano controller is so cool. Finally, someone who’s thinking about the little pro gamers!
xbox.com/it-IT/accessories/c…
My side project scored 92 on Lighthouse SEO. Its HTML body was one empty
.
Lighthouse runs JavaScript, so it never saw the problem. Crawlers that don't run it, including most AI crawlers, found a shop with nothing in it.
With AI, anyone can build a website or an app. Getting people to find it and care is still hard. After 10+ years as a software architect, building is the easy part for me. Marketing is my weak spot, and We Won't Buy, a fake shop for real shopping urges, is my training ground.
On the B2B platforms I built, users arrive through logins, not search. So I shipped it like an internal app: a pure client-side SPA. Lesson one: SEO.
Funny detail: the 8 missing points weren't even about the empty div. There was no robots.txt, so /robots.txt fell through to the SPA and returned HTML. The score caught the small problem and missed the big one.
The fix: prerender the first view at build time, with no SSR framework and no new dependency. Then the marketing checklist: robots.txt, sitemap, JSON-LD, a new title, an FAQ in 5 languages. Grok Bot audited and opened the PRs; I reviewed every diff.
SEO 100 in a local run. Not a ranking, just a first step. A green score isn't the same as being visible: curl your homepage and read what comes back.
Write-up: weekendcodeadventures.xyz/po…
I've been pair programming with a colleague and some AI agents for almost a month now.
We discuss design, trade-offs, and next steps while the agent handles the coding. We review and steer its work together.
The surprising benefit? More space for human collaboration.
Emily Bache offers an interesting perspective on this:
youtube.com/watch?v=ydAin2IW…
Daily rant: IDEs and tools still struggle with established concepts like packages. Why don’t more tools visually distinguish npm packages from ordinary folders? And why can’t I group changes by package instead of just by folder, for example?
It feels like these tools are disconnected from how developers actually work.
I’m starting to question monorepos. I’ve been using them a lot, with deeply nested project structures and repos on every layer. Do they still make sense? Wouldn’t separate repositories make the boundaries clearer?
I bought a couple of old iPads for 10€, and I transformed them into dashboards.
New life for old devices.
Surprise of the week: my blog's accessibility score wasn't about code. It was the colour. White on coral #f76c6c fails contrast. Switched to #cf454b, and Lighthouse now gives it 100.
weekendcodeadventures.xyz
What if, instead of asking AI to explain something in plain text, we asked it to generate an interactive HTML page?
A friend introduced me to this idea, and I've been experimenting with it while working with coding agents.
The idea is simple: not everything needs to be explained with walls of text. Sometimes, a small interactive interface makes things much easier to understand.
I put together three examples:
- Code Review
- Incident Timeline
- Component Hierarchy
These are just initial examples, and I'm still experimenting with and improving them. The possibilities go far beyond these three use cases.
No frameworks. No dependencies. No build steps. Just self-contained HTML files we can regenerate every time.
The interesting part is that we can stop treating text as the default interface for explaining things.
github.com/francescobarbera/…
If you're unsure what the LLM is saying, ask it to produce an HTML file with a clear explanation in a structured format.
Much more useful than plain text.