Alexandre Gerlic

🚀 Scaling an engineering team without traditional managers ⚙️ How we've done it at @alanengineering ⬇️ medium.com/alan/scaling-e…

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

📣 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/a8b3fe4c-…

@cursor_ai We wrote about how we built this momentum, the systems behind it, and what's next: alan.com/en/blog/discov…

@cursor_ai Everyone Can Build is now real: * Faster iteration. Broader ownership. * Teams unblocked. * Code became our shared interface. #everyonecanbuild

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

"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-…

@lovable 💬 Instead of waiting for “vibe-coding” tools to scale… What if we made existing engineering tools and workflows more accessible?

@lovable 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

💡 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.

💡 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!

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.

🚀 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 👇