Symfony

🖥 A Week of Symfony #1021 (July 20–26, 2026) ➡️ https://lnkd.in/eziYqT2i

Security meets team culture at #SymfonyCon Warsaw 2026! 🔒 Discover how to protect your endpoints against the OWASP API Top 10 with Rob Allen 🤝 Learn 10 actionable steps to build a more inclusive workplace with Stefan Koopmanschap Two must-see talks for better code and better teams! 💻🌐 🎟️ Join us: #Symfony #PHP #TechCommunity

Every developer is an engineer now People keep saying AI turns every developer into an architect.  I've been hearing it for a year, and I don't really feel it as a change. I've been the project lead of Symfony for over twenty years now.  Every line in the project might land on my plate to maintain someday.  Contributors come and go; I stay. So my job has always been about managing technical debt: sound architecture, up-to-date docs, real test coverage.  Do that badly and the project collapses under its own weight. That's not a skill I picked up for the AI era.  It's the whole game, and it has been for two decades. What changed is that everyone is now in that position.  You didn't type the code, an agent did, but you own it the moment you ship it.  And to own it, you have to understand it.  I still read every line an agent writes for me, not out of ceremony, but because I might be the one evolving that code next year.  You can't evolve what you don't understand. The agent, meanwhile, will happily keep piling on, without caring about quality the way you have to.  Look away for a while and the code degrades faster than it ever did when humans wrote it, simply because the pace is so much higher. So deep, careful reviews matter more than ever.  That's where the real work happens now: asking the questions, challenging the decisions.  That part never changed, whether it's a contributor's pull request or an agent's code. This is the difference between a developer and an engineer.  Typing code fast made you a productive developer, and the machine does that part now.  What's left is the engineering: understanding the system well enough to own it and keep it alive over years. The machine closed the gap overnight.  Some of us just had a head start.

🖥 A Week of Symfony #1020 (July 13–19, 2026) ➡️ https://lnkd.in/eHJBb8eZ

The countdown is on for #SymfonyCon Warsaw 2026! The first 4 speakers are officially live & hotel deals are ready! 🎟️ Secure your regular ticket now for an unforgettable week 👉 https://lnkd.in/e-vk8DJk

🖥 A Week of Symfony #1019 (July 6–12, 2026) ➡️ https://lnkd.in/eXFuewFP

⏰ Last call for SymfonyCon Warsaw 2026!✨ The Call for Papers closes tomorrow! If you’ve been thinking about submitting a talk or a workshop proposal, this is your sign to go for it! Why take the stage? 👉 Share your expertise: Your real-world experiences, best practices, and technical insights are incredibly valuable to the ecosystem 👉 Support the community: Actively contribute to the growth and knowledge-sharing of the global Symfony community 👉 Grow your reach: Step into the spotlight at one of the biggest PHP events of the year Whether you are a seasoned speaker or a first-timer, the community wants to hear from you! ⏳ Submit your topic before tomorrow's deadline: https://lnkd.in/e24789m2 #SymfonyCon #Symfony #PHP #OpenSource #CFP

🖥 A Week of Symfony #1018 (June 29 – July 5, 2026) ➡️ https://lnkd.in/etwU-miM

[Case Study] Managing 10M+ tons of waste for Veolia 🎉 In just 10 months, Webnet rebuilt Veolia’s Optilia back-office into a lightning-fast cloud platform! 🛠️ The Strategy: No front-end over-engineering. Just the pure power of Symfony (ux-live-component, messenger), PostgreSQL, and AWS. ⚡The Impact: -Faster operations for sales teams. -Instant adoption thanks to a modern UX. -Future-proof scalability for European regulations. 👉 Full story here: https://lnkd.in/eryr5cfT #Symfony #PHP #AWS #WebDevelopment #Veolia #Webnet

For years, Symfony got maybe one security report a quarter. Someone emailed security@symfony.com, we quietly prepared a fix, coordinated with the popular downstream projects built on Symfony, and shipped on the same day. That worked because the interesting vulnerabilities were rare and costly to find, taking a security expert. It isn't anymore. Today we get at least one report a day. Point an agent at a fresh Symfony release and it combs the entire codebase for flaws; so does the next person, running the same model on the same code. The moment one researcher reports something, you have to assume others have already found it. And the ones who email us are the friendly minority: ten report a hole, a hundred find the same one and quietly try to exploit it. So by the time a bug lands in the Symfony security inbox, we have to assume it's already a zero-day. That breaks the whole point of an embargo. The quiet window we used to buy was there to protect our users: get a patch ready before attackers knew where to look. There's nothing left to protect when the bug is public the day it's found. So I've stopped coordinating embargos and just ship the fix, even on a weekend for a critical vulnerability. All those reports are a daily grind on their own. Most are noise: the same false positives, from the same models, sent in by different people. So I'm building a database of everything we've already ruled out and letting an LLM triage against it. Only an LLM can keep up with the flood another LLM creates. The quiet window is gone for good, and the only defense left is to ship faster than the agents hunting for the next hole.