Wouter De Schuyter

🚨 Frontend/Full-Stack Devs: Can you spot the red flag in this package.json? As a freelance developer, I constantly deal with scammers trying to infiltrate my system or steal money. That's why I always test new projects in an isolated Docker container (Ubuntu 22.04) - protecting my personal files is non-negotiable. The Setup: Yesterday, I received what seemed like a legitimate LinkedIn inquiry. After some back-and-forth, they invited me to check out their GitHub repo - a blockchain-powered chess platform. Honestly? The concept was pretty cool, everything looked professionally done, and I was quite excited. So I fired up my Docker sandbox, pulled the code, and opened it up in VSCode. First stop: package.json (as it should always be). The Red Flag: Almost everything looked very standard, being a simple Vite (React.js) app, except for one dependency: "common-js-support." Never heard of it. Google search? Nothing. NPM registry? Doesn't exist. But here's where it gets interesting - running npm info common-js-support revealed the package DID exist, with some suspicious details: Maintainer: <redacted> Dependencies included: fs@0.0.1-security The Attack Vector: That fs package version is a known malicious dependency that allows remote code execution on your machine. NPM flagged it as malicious and permanently removed it from the registry. When I politely explained the security issue and asked them to replace the problematic package, they simply deleted our entire conversation. The Takeaway: Always audit dependencies before installation, especially from unknown sources. These attacks are getting more sophisticated, and that Docker sandbox saves me from a potential disaster almost daily. Stay vigilant out there! 🛡️ What's your go-to security practice when reviewing new codebases? I am very keen to know and learn from others out there facing the same problems! 🫡

1.864

185 Yorum

🏖️ Handum Beach Resort Booking System Week 10 at ASV Business Solution — the week the system started feeling like a real product. ✨ This was probably the most feature-dense week yet. Here's what shipped: 🐛 Fixed a guest booking bug where status update emails (approved, declined, completed) were only being sent to registered users. I added a getRecipient() helper to resolve the correct email target — userId first, guestId as fallback — and updated all three email methods to use it. 🗑️ Implemented the delete villa feature properly — confirmation dialog, GraphQL REMOVE_VILLA mutation, local list update, and a bug fix where the resolver argument was typed as Int instead of String (MongoDB ObjectIds are strings). ⭐ Built the Reviews & Testimonials feature end-to-end. The backend now auto-resolves userId and guestId from the bookingId so the frontend doesn't need to pass user identity at all. Reviews now live in the database and populate the home page Testimonials section with real data. 🤖 Overhauled the AI chatbot architecture. Replaced a brittle intent-classification router (5 intents, separate handlers) with a single unified flow: gather all resort context upfront (villas, bookings, FAQs), inject into the system prompt, and let the model reason freely. Added 25-message session memory and Markdown rendering in the chat UI so responses feel polished and natural. ☁️ Migrated all villa image uploads and payment proof uploads from local disk storage to AWS S3 — with a shared S3Client, multerS3 storage config, and full URL storage in the database. The getImageUrl() helper methods scattered across components were deleted entirely. 🧭 Built a scroll-adaptive site header, a full FAQ CRUD system with a NestJS module from scratch, and an accordion FAQ section on the home page with a contact panel. The system is beginning to feel complete. 9 weeks in and I'm building features I'm genuinely proud of. 🙌 #OJT #Internship #NestJS #Angular #AWS #S3 #AIchatbot #GraphQL #FullStack #Philippines

1

💡 Good code is invisible; bad code is a system crash. At JeniusTek, we don’t just build pretty interfaces — we focus on what’s under the hood. Clean architecture and maintainable systems mean your software won’t need a total rebuild in 18 months. Maintainability is a feature. Quality at the start saves a fortune at the end. #CleanArchitecture #SoftwareQuality #MaintainableCode #TechSolutions #FutureReady #JeniusTek

5

Competition among Frontend consultants/freelancers remains high.   Frontend Developers currently have the highest average number of applications per assignment on Brainville. Applications per assignment are also up +16% in 2026 compared to 2025 so far.   Does this reflect what you’re seeing in the market right now?   #FrontendDeveloper #Frontendutvecklare #FrontendUdvikler #Nordics #brainvillestatistics

33

2 Yorum

Toni reminds us in his post below that the Dutch PHP Conference has its 20th edition this year. I remember that first edition in 2007 fondly. I was a complete newbie in organizing conferences and had only my experience as a speaker and attendee to know ‘what is right’. When trains were delayed and a lot of visitors arrived late, we said ‘should we postpone the schedule and wait?’ but Cal Evans, our host that day said “Nope! Whatever happens, the schedule is leading. No delay”. And he was right of course, it would have derailed the agenda for all the attendees that were in time. When the projector didn’t work because of a broken cable, we learned the importance of high quality keynote speakers: Kevlin Henney turned out to be a great stand up comedian and kept the audience engaged for 10 minutes while the venue repaired the setup. With every edition after we have refined the schedule and the organization, applying the schedule discipline that Cal taught us and carefully selecting our keynote speakers. What also never changed is that we always kept that ‘what would speakers want’ and ‘what would attendees want’ at the core of how we make decisions! Not only for the Dutch PHP Conference but also for the Appdevcon, Webdevcon and Dutch AI Conference that came after.

24

1 Yorum

New server initiatives. Everybody getting ready for Solid Symposium in Londen next week #sosy2026. Will we see you there? A new JavaScript Solid Server (JSS) is now ready for beta testing: https://jss.live/ JSS is a JavaScript/JSON-LD-first Solid server and is aligning with the upcoming Linked Web Storage (LWS) specification. It provides a lightweight, independent implementation that can run on servers and phones. Less packages, less memory and high performance. #solid #linkedwebstorage

5

1 Yorum

𝗣𝗹𝗼𝘁 𝗧𝘄𝗶𝘀𝘁: 𝗧𝗵𝗲 𝗟𝗮𝘆𝗼𝗳𝗳𝘀 𝗔𝗿𝗲𝗻'𝘁 𝗥𝗮𝗻𝗱𝗼𝗺. 𝗧𝗵𝗲𝘆'𝗿𝗲 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰. 🎯 Companies aren't just cutting costs. They're cutting the developers who refuse to evolve. 𝗪𝗵𝗮𝘁 𝗜'𝗺 𝘀𝗲𝗲𝗶𝗻𝗴 𝗶𝗻 𝟮𝟬𝟮𝟱: 𝗧𝗲𝗮𝗺 𝗔: 3 AI-native developers shipping a complete e-commerce platform in 6 weeks 𝗧𝗲𝗮𝗺 𝗕: 8 "experienced" developers still debating architecture patterns after 3 months 𝗚𝘂𝗲𝘀𝘀 𝘄𝗵𝗶𝗰𝗵 𝘁𝗲𝗮𝗺 𝗴𝗼𝘁 𝗯𝘂𝗱𝗴𝗲𝘁 𝗮𝗽𝗽𝗿𝗼𝘃𝗮𝗹 𝗳𝗼𝗿 𝗻𝗲𝘅𝘁 𝗾𝘂𝗮𝗿𝘁𝗲𝗿? 𝗧𝗵𝗲 𝗻𝗲𝘄 𝗵𝗶𝗿𝗶𝗻𝗴 𝗰𝗿𝗶𝘁𝗲𝗿𝗶𝗮: ❌ "10 years of experience" ✅ "Can you ship working features fast?" ❌ "Expert in legacy systems" ✅ "Comfortable with AI-assisted development?" ❌ "Strong debugging skills" ✅ "Knows how to leverage AI for problem-solving?" 𝗪𝗵𝗮𝘁 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝗮𝗿𝗲 𝗾𝘂𝗶𝗲𝘁𝗹𝘆 𝗺𝗲𝗮𝘀𝘂𝗿𝗶𝗻𝗴: 📊 Lines of code per day (AI-assisted vs manual) ⏱️ Time to feature completion (with vs without AI) 🐛 Bug reduction rates (AI-reviewed vs human-only code) 💰 Cost per delivered feature (AI-augmented teams vs traditional teams) 𝗧𝗵𝗲 𝗯𝗿𝘂𝘁𝗮𝗹 𝗺𝗮𝘁𝗵:  • 1 AI-native developer = 3 traditional developers in output  • 50% less debugging time with AI code review  • 70% faster feature delivery with AI assistance 𝗥𝗲𝗮𝗹 𝗰𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻 𝗜 𝗼𝘃𝗲𝗿𝗵𝗲𝗮𝗿𝗱: CTO: "Why do we need 12 senior developers when 4 junior developers with AI tools ship the same amount?" Engineering Manager: "Because... experience?" CTO: "Experience shipping slow code isn't an asset anymore." 𝗧𝗵𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝗮𝗱𝗮𝗽𝘁𝗶𝗻𝗴:  • Training existing teams on AI tools  • Hiring for AI-collaboration skills  • Measuring productivity, not tenure 𝗧𝗵𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝘀𝘁𝗿𝘂𝗴𝗴𝗹𝗶𝗻𝗴:  • Protecting "senior" roles based on years, not output  • Treating AI as a threat instead of a tool  • Wondering why their competitors are moving faster 𝗙𝗼𝗿 𝘀𝗲𝗻𝗶𝗼𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 𝘁𝗵𝗶𝘀: Your experience IS valuable. But only if you multiply it with AI. 𝗙𝗼𝗿 𝗷𝘂𝗻𝗶𝗼𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀: This is your moment. Learn AI tools now and leapfrog the dinosaurs. 𝗧𝗵𝗲 𝗵𝗮𝗿𝗱 𝘁𝗿𝘂𝘁𝗵: In 2025, "senior developer" means "senior at using AI to solve problems." Not "senior at solving problems without AI." 𝗧𝗵𝗲 𝗰𝗵𝗼𝗶𝗰𝗲 𝗶𝘀 𝘆𝗼𝘂𝗿𝘀: Evolve or become extinct. What's your plan? #TechLayoffs #AIEvolution #FutureOfWork #DeveloperCareers #TechTrends2025 #AIProductivity #SoftwareDevelopment #TechIndustry #CareerStrategy #DigitalTransformation #TechJobs #AIAdoption #WorkforceEvolution #TechLeadership #IndustryShift #DeveloperLife #TechReality #AIForDevelopers #ModernWorkplace #TechCareers

2

Salamzzz PHP Fellows, You must try PHP Native! Check out the post by Arif Hussain 😇 below. I’ve tried it myself and it works great. The setup is very simple — just follow a few steps and you’ll be amazed by the results! Highly recommended for PHP developers. 🚀

4

1 Yorum

In the preparation of my talk at Vue Amsterdam about local-first software, I started to write a blog post that explains sync engines for Vue developers and also shows what options we have.

2

Let's end this year with a bang! 🚀 Sylius v2.2. it's out! 🎉 The new Sylius 2.2. release brings important updates, with a strong focus on the tech stack: 📌 Symfony 7.4 & PHP 8.5 support - keeping your projects up to date and future-proof 📌 Shipping - estimated delivery time functionality 📌 Tax - zone priority ordering when multiple tax zones match 📌 CLI - list admin users with details, delete admin accounts, and extended installer setup A solid minor release with meaningful improvements for both developers and business teams 💪 🔗 Full release notes: https://lnkd.in/dVZ5Jtt3

53

ATP came back two years after the first project. In 2023 we built their compliance assessment platform — a build with custom logic, Stripe, course enrollment integrations, a state-specific PDF library. The kind of project most small businesses only do once. In late 2025 they asked us to replace their PHP marketing site too. They didn't run an RFP. Didn't take vendor calls. Didn't shop the project. They sent a proposal request to the team that already knew their stack, their auth, their Azure subscription, their content team's workflow. 23 pages. 17 static, 6 with admin interfaces. 99 hours. $8,910 — well below what an agency quote would have been, and competitive with a WordPress build. The reason it worked at that price isn't because we're fast. It's because the boring infrastructure already existed. Same App Service. Same SQL Server. Same auth system. Same deployment pipeline. The "DevOps work" — the part that eats most marketing-site budgets — happened years earlier. The first project a small business ships with a custom dev team is always the most expensive. The second project starts from a different baseline. The third one barely needs a SOW. Most small businesses never get to find that out. They run a fresh RFP every time, pay the discovery tax every time, onboard a new vendor every time. The economics of small-business software get a lot better once you stop doing that.

2

1 Yorum

🚀𝐁𝐈𝐆 𝐍𝐄𝐖𝐒 🔊 𝐓𝐡𝐞 𝐒𝐭𝐚𝐟𝐟𝐢𝐧𝐠 𝐓𝐢𝐦𝐞𝐥𝐢𝐧𝐞 𝐢𝐬 𝐞𝐯𝐨𝐥𝐯𝐢𝐧𝐠. 🔥🔥 We’re bringing major improvements to the experience of planning work in Confluence. Smoother, faster, and built for modern teams. 🛠️ Curious about the 𝐜𝐡𝐚𝐧𝐠𝐞𝐬? Check the sneak peek here: 👉 https://lnkd.in/eSkTvkq6 Ready to see it in action? Check it out on the Transition Technologies PSC's Atlassian Marketplace: 🔗 https://lnkd.in/eJt_icUN ⚡🔊 #TeamTTPSC #TTPSCAdvocacy #Atlassian #AtlassianForge #Confluence #StaffingTimeline

16

I've been thinking about this for years, and Joost de Valk's recent piece about refactoring WordPress and Jean Galea's response to it, finally pushed me to write it down. WordPress needs a modern PHP foundation. Not a reckless rewrite, but a structured migration path. I'm proposing the BackPress name be revived as an opt-in legacy compatibility layer: old plugins and themes keep working, new projects get a clean architecture from day one. Full post: https://lnkd.in/dTMmEup4

3

3 Yorum

Still running Java 8 or 11? You’re in good company. Many teams can’t rewrite or upgrade on schedule – and that’s fine. Tomorrow at Devoxx Belgium, Pasha Finkelshteyn (BellSoft) and Baruch Sadogursky (TuxCare) will talk about how to do better in legacy Java. From cleaner code and better testing to faster performance and stronger security, they’ll show how to keep engineering standards high even when you’re not moving to the latest LTS. 📅 Thu, Oct 9 • 13:50 • Room 7

5

1 Yorum

Joost de Valk says WordPress is falling behind the modern web with its centralized plugin repo and dated infrastructure. The founding member of FAIR frames the project as a resilient, standards-driven alternative, but says WordPress Playground and the Abilities API show modernization in the WordPress project is still possible → https://lnkd.in/g-9scZVT (h/t: @therepositorywp)

3

2 Yorum

Last night, our colleague Michel Schudel took the stage at to deliver a talk on the art of building maintainable Spring Boot applications, guided by the principles of Clean Architecture. In his session, Michel showed how to structure your code so that your domain logic stays clean, testable, and protected from framework and infrastructure concerns. No over-engineering. No theoretical fluff. Just practical examples you can apply immediately in your own projects. Because let’s be honest: building something that works is easy. Building something that’s still maintainable two years from now? That’s craftsmanship. Michel is a software developer at Craftsmen and also a member of the CFP Committee Board of Voxxed Days Amsterdam, where he helps shape high-quality technical content for the community. Big thanks to Utrecht JUG for having us and for organizing another great evening of knowledge sharing and community building. 👏 #SpringBoot #CleanArchitecture #SoftwareEngineering #Java #UtrechtJUG #TechCommunity Willem van de Griendt Téo Bais Michel van Dongen Sopra Steria

29

1 Yorum

I built a production SaaS product using AI. Heavily. Not autocomplete. I mean: architecture decisions, debugging sessions, entire modules — together with AI. And I'm not going to pretend otherwise. Here's what I noticed: the developers who are loudest about "real engineers don't use AI" are usually the ones who haven't shipped anything recently. I work in logistics tech. I see a real problem every day. I had domain knowledge nobody else had. AI gave me the execution speed to match it. The product works. The routes optimize. Real dispatchers are testing it. How it was built doesn't change whether it solves a real problem. We got a new tool. The developers who learn to use it well will build things that weren't possible before. That's not a shortcut. That's just 2026. Have you shipped something with AI help? Or are you still pretending you haven't? #ai #buildinpublic #saas #softwaredevelopment #artificialintelligence

As part of the Lynxmind team I see this challenge every day. Companies feel the pressure to innovate but often lack the map to get there. It is easy to buy a tool but much harder to build a strategy that scales. That is exactly where we step in. We don't just implement technology. We build the roadmap plus ensure it aligns with your real business goals. Proud of the work we are doing to turn AI hype into measurable results. 👇

4