Boris Guéry-Josadė

Building integrations shouldn’t require writing code. In Lumino you can create a new connector in minutes — define your schema, map fields, configure auth, and make APIs talk without engineers. This video walks through exactly how to build a connector from scratch. If custom integrations are slowing your team down, give this tutorial a watch: https://hubs.li/Q042NwgH0 #iPaaS #enterpriseintegration #ERPintegration #nocode

6

💡 The role of a product manager is changing — fast. No more endless docs or hand-offs. The new generation of tools helps teams move from idea to prototype in minutes — and lets product people build, test, and iterate without waiting on devs. True innovation isn’t about control. It’s about shortening the distance between thought and action. 📖 Read the full story → https://lnkd.in/dyhf2UHG #ProductManagement #NoCode #WorkflowAI #DesignInnovation

1

Your roadmap is growing. Your eng team isn't. AI-Native Engineering Pods are how fast-moving companies close that gap — small, focused teams that use AI across design, build, test, and ship. No bloated hiring cycles. No months of onboarding. Just product, moving fast. Companies are using pods to: → Launch new products without growing headcount → Modernise legacy systems at speed → Scale output — not costs Ready to ship in 14 days? Contact us to spin up your AI-Native Engineering Pod. https://lnkd.in/gr4yEqCp

24

**Micro-frontends architecture — when and how to split your frontend** Micro-frontends sound great on paper: independent teams, independent deployments, faster scaling. But splitting a frontend too early can create more complexity than it removes. A better question is not: **“Can we do micro-frontends?”** It’s: **“Do we actually need them?”** ### When micro-frontends make sense Micro-frontends are usually worth considering when: - Multiple teams are working on the same frontend and stepping on each other’s toes - Release cycles need to be independent - Different product areas evolve at very different speeds - A large frontend has become hard to own, test, and deploy as one unit - There’s a strong domain boundary between parts of the product If your app is still manageable as a monolith, keep it that way. A well-structured monolith is often faster than a poorly designed distributed frontend. ### How to split your frontend the right way If you decide to go down the micro-frontends path, split by **business domain**, not by technical layers. Good examples: - Checkout - Search - Account - Admin portal Bad examples: - Header team - Button team - Shared components app The goal is to give each team ownership of a meaningful product slice, not just UI fragments. ### What matters most Successful micro-frontends usually require: - Clear domain boundaries - Strong design system consistency - Shared authentication and routing strategy - Thoughtful communication between apps - Observability across the whole user journey - Governance to avoid duplicating everything everywhere Without these, micro-frontends can quickly become “distributed frontend chaos.” ### A practical rule of thumb Start with a modular monolith. Invest in: - clear boundaries - shared UI standards - isolated deployments where possible - team ownership Then move to micro-frontends only when team structure and scaling needs justify the added complexity. **Architecture should solve organizational problems, not create new ones.** Have you seen micro-frontends simplify frontend delivery — or just spread monolith problems across multiple repos? #frontend #webdevelopment #softwarearchitecture #microfrontends #engineering #frontendarchitecture #techlead

Lyse Registry is now open source One year ago, we launched the Lyse Library on Figma. Since then, hundreds of companies and SaaS projects have adopted it. The most active designers kept asking for the same thing — real React components they could use in production. Today, we're releasing the Lyse Registry: 30+ React components you can use on v0 by Vercel to build full apps with the Lyse library. Compatible with shadcn. Installable in a single command. The registry is open source — contributions welcome. Lyse Registry : https://lnkd.in/eKvt5ejv Github Repo : https://lnkd.in/e-S4vvfH

41

4 commentaires

HeroUI (YC S24) enables developers to generate React applications from text prompts, requiring instant code execution and preview environments. HeroUI deployed Together Code Sandbox for their preview infrastructure — reducing cold-start times from 2 minutes to 2 seconds and accelerating their go-to-market from 5 months to 2 weeks. The managed platform handles all code execution without browser limitations. "With Together Code Sandbox, we had an MVP running in a couple of hours instead of waiting months to see results," says CEO Junior Garcia.

14

5 commentaires

🚀 Announcing the Symfony AI Initiative — spearheaded by Fabien Potencier to bring first-class AI tooling to your Symfony apps: • 🔗 Unified Platform for OpenAI, Anthropic, Azure, Google & Mistral • 🤖 Agent Component enabling multi-step AI workflows & tool invocation • 📚 Store Component for data storage, indexing & semantic search • 🛠️ AI Bundle & MCP SDK for native Symfony integration Still in active development—explore demos, review docs & join the conversation on the issue board. Your feedback and contributions will help shape the future of AI in PHP! 👉 https://lnkd.in/gkEth-bE #Symfony #PHP #AI #MachineLearning

39

The Symfony AI initiative ✨ is opening new doors. Now, the challenge is to move from experimentation to production-grade implementation. Many development teams are rushing to integrate LLMs, but often at the expense of their architecture’s long-term stability. At SensioLabs, we believe you shouldn't have to choose between innovation and a clean codebase. As early adopters of Symfony AI, we are now sharing our expertise to help organizations build smarter while staying true to the framework’s standards. As the creator of the framework, our goal is to help you: ⚒️ Build AI-integrated features that actually scale. 🛡️ Keep your architecture secure and maintainable. ⚡ Accelerate your time-to-market without piling up technical debt. Symfony was built for professional, robust applications. AI should be no exception. Read more here 🔗 https://lnkd.in/eNahFbPw Ludovic Duval Oskar Stark Salah MEHARGA Guillaume Loulier Mathieu Santostefano Hadrien Cren • Grégoire Thelliez Hugo Lafaye Marine KROLAK

185

1 commentaire

Building your first product? 🚀 Your launch depends on getting your first dev hires right. The wrong team will drain your budget, delay your launch, and leave you with tech debt that’s impossible to fix. Here’s a quick, no-fluff guide on: ✅ Who to hire first ✅ How to vet devs properly ✅ Structuring your first dev team for a successful launch Swipe through, save for later, and share with a founder who needs this. #StartupTips #HiringDevelopers #TechStartup #ProductLaunch #Founders #StartupHiring #RemoteHiring #DevTeams #SoftwareDevelopment

1

1 commentaire

Did you miss this post by Fabien Potencier ? https://lnkd.in/erfHp4KG Great and insightful view of the new Symfony #AI initiative 🚀 Two items seem particularly relevant : 🔧 MCP SDK: An implementation of the Model Context Protocol, enabling your applications to communicate with AI systems using the emerging industry standard. ⚙️ MCP Bundle: Allows your Symfony applications to act as MCP servers or clients, opening up new possibilities for AI integration and tool creation. Whether you like it or not, MCP is going to play a big part in the coming years !

8

Shifting API Quality Left: How Developers Actually Adopted Karate Register https://lnkd.in/enMa8WyV (use the following VIP code at checkout: KARATEUSERVIP) to join us in Paris on December 11, 2025, for "Karate: The Future of API Testing", listen to Mark Hughes speak on this topic.   Most teams say they’re “shifting left,” but the reality on the ground often looks very different: bloated regression packs squeezed into a single day, manual testers burning out, and UI suites so flaky that nobody really trusts the results. I’ve lived in those testing cycle first-hand. In this talk, I’ll share how we used Karate to break that pattern and turn API tests into the source of truth for how our systems behave, not just another layer of noise on top of an already creaking testing pyramid.   Drawing on real adoption stories – this session will show how contract and system integration testing in Karate became the source of truth for how our platforms are supposed to behave. You’ll see how we used Karate to harden the test pyramid: pushing more coverage down into fast API layers, cutting reliance on brittle UI flows, and reducing execution time from hours to minutes. We’ll talk about what actually worked in practice: how QA engineers led the change, how we dealt with legacy flakiness, and how we kept the feedback loop tight enough that developers actually paid attention.   By the end, you’ll have a concrete playbook you can use for your own team! You’ll leave with patterns for introducing Karate into an existing regression process, realistic ways to reduce manual regression load without lying to yourself about coverage, and tactics for stopping automation getting stuck debugging the same false negatives every sprint. If you’re already using Karate but feel your test packs, pipelines, or people are close to breaking point, this talk is about how QA can use Karate to shift API quality left – and actually make it stick.

13

1 commentaire

Startups move fast — your code should keep up without falling apart. That’s where Test Driven Development makes a difference. With TDD, you can iterate quickly and safely. As your product evolves, your tests protect what matters, catch regressions early, and document expected behavior — even when the team changes or pivots. TDD isn’t overhead — it’s insurance for speed, scale, and long-term survival. If you're building fast, test smart. #Startups #TDD #ProductDevelopment #TechDebt #MoveFastStayStable

1