←
Wouter de Jong (@wouterj@phpc.social)2,599 posts
Wouter de Jong (@wouterj@phpc.social) avatar

Wouter de Jong (@wouterj@phpc.social)

@wouterjnl

Docs & Core team member at @symfony; Software Engineer/DevOPs @my_wheels; Building Architecture graduate @TUeindhoven;

◷ Joined September 2011▧ 35 Photos and videos
Wouter de Jong (@wouterj@phpc.social) avatar
Wouter de Jong (@wouterj@phpc.social)@wouterjnl·Mar 2

In 2013, @fabpot started a challenge of creating a Symfony app with only 1 file and 200 lines of code. Today, I showcase how far we get with modern Symfony in my latest blogpost: wouterj.nl/2026/02/200-lines…

Wouter de Jong (@wouterj@phpc.social) avatar
Wouter de Jong (@wouterj@phpc.social)@wouterjnl·Feb 2

New blog post on how we manage env variables to configure our applications in Kubernetes, to allow changing them without a redeploy: wouterj.nl/2026/02/manage-en…

Evan You avatar
⟳ Wouter de Jong (@wouterj@phpc.social) retweeted
Evan You@evanyou·23 Nov 2024

Agreed. The value of PR descriptions is often in things that are NOT directly inferable from the changes: - What original problem led to this PR? - Are there related issues / prior discussions? - What alternatives have been tried? Does this supersede previous attempts? - Why are certain seemingly unreasonable choices made? What are the tradeoffs? AI that generates summary based on the changes of an isolated PR is not really helpful in a meaningful way. Good PR descriptions need not only a holistic understanding of the entire codebase, but even the contribution history of the project. That’s of course harder to do, but I think it’s a possible direction to make it actually useful.

Thank you GitHub, but that’s not how we build software. AI should help us focus more on reasoning, design, communication. Filter spam and unnecessary noise, not helping creating them.

Wouter de Jong (@wouterj@phpc.social) avatar
Wouter de Jong (@wouterj@phpc.social)@wouterjnl·8 Aug 2024

New post on my blog: 📝 Store Code Discussions in Git using Git Notes wouterj.nl/2024/08/git-notes We distribute code using Git, but the discussions in pull requests are just as important! I'll show how Symfony also distributes the discussions using Git.

Wouter de Jong (@wouterj@phpc.social) avatar
Wouter de Jong (@wouterj@phpc.social)@wouterjnl·11 Apr 2024

Thanks you #PHP community for showing up as one and supporting a fellow member in his fight to steal more years to live! We reached the goal of $250,000 on Ryan Weaver's fundraiser in 4 days. Let's continue supporting Ryan and his family 💙 gofund.me/82392317

Wouter de Jong (@wouterj@phpc.social) avatar
Wouter de Jong (@wouterj@phpc.social)@wouterjnl·8 Apr 2024

Heartbreaking news. I can confidently say Ryan has supported every single person in the Symfony community through his passionate work on the docs, SymfonyCasts, GitHub, etc. Now it's time to give support back on a much more important topic and share the warmth of our community❤️

So.... I have incurable brain cancer and I'm asking for your love & support 💖

2:11
Wouter de Jong (@wouterj@phpc.social) avatar
Wouter de Jong (@wouterj@phpc.social)@wouterjnl·7 Feb 2024

The average age of PHP code lines in @symfony 75% of the lines are edited within the past 4 years. That's pretty amazing for a codebase that it's 15 years old! Also interesting to see some components that were more or less feature complete from the start (Mime, RateLimiter,...)

Post attachment
Ryan Weaver avatar
⟳ Wouter de Jong (@wouterj@phpc.social) retweeted
Ryan Weaver@weaverryan·21 Oct 2023

Remember: it’s pretty easy to bump your deps to 6.4 and run your tests / try your app. It should still work exactly like before. If it’s not, let us know!

Test it, test it and test it again!