@avec_alan, previously: @Intercom
Paris, France
Joined January 2010
- Tweets1.7K
- Following584
- Followers351
- Likes381
Pinned Tweet
🚀 Scaling an engineering team without traditional managers
⚙️ How we've done it at @alanengineering ⬇️
medium.com/alan/scaling-engi…
Alexandre Gerlic retweeted
We wrote about Hopper, the agent we built at Alan.
It started as a coding agent for builders. Today 80% of Alaners use it, and 25% of our merged PRs come from it.
More technical posts to follow in the coming weeks/months!
medium.com/alan/hopper-we-bu…
Alexandre Gerlic retweeted
Ever wondered how Alan reimburses health claims so fast? Spoiler: we automated 70% of document processing.
We just dropped the first article of our doc processing series — stay tuned for more on how we're scaling this across other countries and use cases. buff.ly/2Lu7aWD
Alexandre Gerlic retweeted
📣 We’re doing something a bit different at @alan: an on-site Engineering Recruitment Day
📍 Paris (Alan HQ)
🗓️ Tue, March 17
⏳ Apply by Wed, March 11
👉 jobs.ashbyhq.com/alan/a8b3fe…
ALT Eng Hiring Day at Alan - 2026/03/17
A button color took weeks to ship. Not because it was hard—but because the designer who spotted it couldn't fix it themselves.
So we asked: what if everyone could build?
#everyonecanbuild
Everyone Can Build is now real:
* Faster iteration. Broader ownership.
* Teams unblocked.
* Code became our shared interface.
#everyonecanbuild
We wrote about how we built this momentum, the systems behind it, and what's next: alan.com/en/blog/discover-al…
Alexandre Gerlic retweeted
"Claude did it almost on its own while I was boiling water for my tea"
That's how our engineers now fix flaky tests at Alan.
Read more about our journey from manual debugging to AI-powered investigation in our latest article 👇
medium.com/alan/from-gut-fee…
💡 Should you use @lovable?
Over the past few months, I’ve had the privilege of watching yamas.tech/ come to life built with Lovable.
It’s not “just a landing page.”
It’s a full-fledged product: frontend with complex states + AI multi-agent backend.
So, when should you use it?
✅ Rapid experiments: landing pages, waitlists, MVPs
✅ Small teams: can handle an app with a few engineers
❌ Large teams or large codebases: not ready yet
🚀 Just tested @kirodotdev (kiro.dev/), Amazon’s new AI IDE.
Not just another “copilot” — it rethinks the IDE as a spec + workflow engine. Here’s what stood out 👇
What can be improved
⚠️ Spec-to-Code maturity: The spec creation feels strong; the code generated still needs refinement.
⚠️ Pricing clarity: splitting “vibes” vs. “specs” requests makes forecasting harder.
⚠️ Settings surprises: autocompletion was disabled by default.
💡 Overall impression: @kirodotdev is onto something. They’ve rethought the IDE not just as a coding tool, but as a specification and workflow engine. Even if it’s not fully mature yet, the ideas are bold and might influence how other IDEs evolve. Worth exploring!