Antonio Fernandes

New audio plugin tutorial series! 🎵 We've built an awesome sampler plugin using JUCE and C++, and we're going to show you exactly how to build one too. In this series, you'll learn: ✅ Audio engine architecture for sample playback ✅ Professional plugin UI design in JUCE ✅ Sample loading and memory management ✅ MIDI note mapping and voice allocation ✅ What makes a plugin production-ready (not just tutorial-ready) This is for intermediate developers who are ready to build real products that could ship to customers. This series has been made with the help of the awesome Matthijs Hollemans! Episode 1 is live now - we explore the finished sampler and break down the project setup. This tutorial is perfect for anyone who wants to move beyond basic tutorials and start building professional audio tools. Watch here: https://lnkd.in/gKctdHmH Join us at The Audio Programmer for more! #AudioProgramming #JUCE #PluginDevelopment #MusicTech

94

2 Comments

Three hours into a coding session with Claude, everything's working, features are shipping fast. Then you realize you've built three different authentication systems and can't remember which one you're actually using. This is drift. And it's exactly why pure vibe coding breaks at scale. I've watched this happen with clients building real products. The speed feels great until day three, when you're debugging something you coded yesterday but can't remember why. Suddenly you're spending hours untangling code instead of shipping. The article making rounds right now on anti-drift workflows breaks down four solid approaches: PRD.md for clarity upfront, GitHub Spec-Kit for structured specs and plans, Planning with Files to persist context across sessions, and the Ralph Wiggum Loop for fully autonomous builds. What strikes me is this: none of these are about slowing down. They're about catching problems at the spec stage instead of in production. Users report 80-90% fewer bugs with Spec-Kit specifically because you stop and review after each stage. The real question though? How many teams are actually doing this versus just accepting drift as the cost of moving fast. Because there's a difference between vibe coding for a weekend project and vibe coding a feature that touches five different files in a production codebase. https://lnkd.in/echnCVsA Vibe Coding App

1

If we change a Streaming Resource request, will Angular unsubscribe? 🤔 Check out Milos Krstic, an experienced architect, expanding his extensive Angular knowledge. In this exclusive clip from Tech Stack Nation, Milos asks this question to Alex from the Angular team and learns about #abortSignal. 🔥 As a member of our expert Architects Study Group, Milos is surrounded by friendly architects sharing knowledge to elevate one another’s skills. 👨‍💻👩‍💻 Want to be like Milos - a confident architect who asks excellent questions and thrives on a challenge? #BecomeTheExpert at Tech Stack Nation! 💪😎🌟 #ArchitectsStudyGroup #TechCommunity #AdvancedTech #LevelUp

4

💡 AI doesn’t just change how code is written – it changes expectations and outcomes. In the final section of Jellyfish’s AI Adoption Guide, we explore how expectations for engineering leaders are evolving as AI becomes embedded across the SDLC. Because the organizations pulling ahead are treating AI as a transformation, not a tooling upgrade. Inside, you’ll explore: - Why AI adoption is quickly becoming a leadership mandate, not an option - How to balance ambitious goals with realistic expectations - What cultural investments are required to sustain long-term gains - How data can be used to align executives and engineering teams The teams that win in the AI era won’t just have better tools – they’ll have leaders who know how to guide change. Download today: https://lnkd.in/dut_6WpQ

20

80% of software agencies deliver exactly what CTOs fear: • No real leadership • Zero accountability for outcomes • Technical debt instead of solutions I've had clients come to us after spending $250K with other agencies. Result: A pile of code that needs complete refactoring. The space is broken. At Nolte, I'm so confident in our delivery that I've invested in 90% of our clients over the past 3-4 years. That's not normal in this industry. But it should be. The difference: → We optimize for ROI, not billable hours → We own outcomes, not just deliverables → We bring strategic thinking, not just code Most agencies are vendors. We're partners. When you truly believe in what you're building, you put your money where your mouth is.

19

Is your dev team accessibility-ready? We break down 7 essential skills every engineer should have to build inclusive, WCAG-compliant websites and apps in 2025. From semantic HTML to screen reader testing and mobile responsiveness, these are the fundamentals that separate good teams from great ones. Read the full article: https://lnkd.in/gnAnc4Ss #Accessibility #WCAG #InclusiveDesign #WebDevelopment #A11y #DevSkills #Section508 https://lnkd.in/gnAnc4Ss

1

If you’re running a multi-tenant SaaS on “one big cluster” and every incident feels risky, this one might help. We walk through how to move toward a cell-based architecture so you can limit blast radius, isolate noisy tenants, and scale with a bit more peace of mind. Key take-aways: What a “cell” is and how it differs from simple sharding How to route tenants to cells using a control plane and edge gateway Patterns for data isolation, global reporting, and schema changes A practical migration path from shared-everything to cell-based design 👉 Check it out: https://lnkd.in/ddpk_XaH Would like to hear how you’re handling blast radius and noisy neighbors in your own SaaS systems. #SystemDesign #SaaS #Architecture #Scalability #Reliability

1

Engineers prefer specialised tooling for tests, docs, and code reviews -> https://lnkd.in/drC-sgcn That preference creates a tension. Role specific tools help, but separate tools can break alignment. A “done” task means something different to an engineer than it does to a researcher, but both still need to land on the same common ground. So AI cannot only work on the last prompt. It must operate over shared state: intent, insights, and feedback signals, with role specific behaviour anchored to a unified truth underneath. This is why we are building Qi, a flow engine for human AI cooperation, to move upstream and anchor AI reasoning in authenticated shared state, provenance and trust signals, with humans able to challenge and refine outputs. -> Swipe to slide 5 for the specialisation versus alignment tension. Slide 6 lists the structural fix.

5

1 Comment