Learn Agile Practices

When vibe coding went mainstream, my first reaction wasn't panic. It was curiosity. Then came a sharper question. The speed never bothered me. What bothered me was that not understanding the generated code had become part of the workflow, something you were supposed to accept.In this episode I talk through how I reasoned about it, based on years of XP and DevOps. TDD, refactoring and continuous delivery aren't rituals to skip: they're the brakes that make speed safe. Vibe coding takes out the understanding loop that comes before the tests. Public incidents showed what happens when understanding is treated as optional at the moments it matters most. This isn't an ideological stance against AI. I'm against using AI without discipline, and I wanted AI to help me carry the cost of discipline instead of skipping it.Follow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe

🇮🇹 Che tipo di ingegnere voglio essere? Un anno fa ChatGPT era solo un taccuino per me — un posto dove ragionare ad alta voce, fare brainstorming, tenere un diario. Poi gli strumenti sono migliorati, l'hype è cresciuto, e ho sentito la spinta verso scorciatoie che non erano professionali. La domanda sbagliata era "dovrei usarlo o no?" Quella giusta ha cambiato tutto: che tipo di ingegnere voglio essere con questi strumenti? Questo episodio parla di quel cambio di prospettiva — e del perché la risposta non è un nuovo set di valori, ma amplificare le pratiche che già funzionano. Il "come" arriva nel prossimo episodio. 🇬🇧 What Kind of Engineer Do I Want to Be? A year ago, ChatGPT was just a notebook for me — a place to think out loud, brainstorm, journal. Then the tools got better, the hype got louder, and I felt the pull toward shortcuts that weren't professional. The wrong question was "should I use this?" The right one changed everything: what kind of engineer do I want to be with these tools? This episode is about that shift — and why the answer isn't a new set of values, but amplifying the practices that already work. The "how" comes next.Follow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe

EpisodeIterative Incremental opens with a restart, not a comeback. After closing the Practical Handbook for Product Developers, I'm changing the object of study — not the practices. Same XP, Agile, Lean and DevOps foundations you know; new lens, focused on coding agents and what holds up under evidence rather than hype. No fixed runtime anymore: this episode takes exactly the space the thinking needs, which is the whole point of the new format. Follow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe

🎙️ “L’AI non solo scrive, ma pensa (al posto tuo?)” Ogni settimana siamo sommersi da più contenuti di quanti ne possiamo leggere. E ora l’AI non si limita più a generarli — li sceglie, riassume e spiega per noi. In questo episodio esploriamo come l’intelligenza artificiale stia trasformando il modo in cui impariamo: dal passaggio da blog e corsi a feed generati dall’AI, fino ai nuovi modi di studiare, dialogare e insegnare con gli LLM. Scopriremo:come il micro-learning e il “learning by chat” stanno cambiando la nostra attenzione e la profondità di comprensione;dove si nasconde il trade-off tra velocità e riflessione;perché ogni lettore oggi è anche autore — ma non sempre un buon insegnante;e un mini-caso reale: un developer che impara solo tramite chat AI… cosa guadagna e cosa perde.Chiudiamo con una sfida: 📈 per 48 ore, traccia come impari — con e senza AI — e scopri dove nasce davvero la comprensione. 🎧 25 minuti di pratica, curiosità e consapevolezza su come l’AI sta riscrivendo l’apprendimento.Seguimi su Linkedin: https://www.linkedin.com/in/daniele-scillia/Follow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe

L’AI scrive codice più veloce, ma… era davvero questo il problema? In questo episodio analizziamo i veri colli di bottiglia nello sviluppo software: comunicazione, delivery, debito tecnico e decisioni lente. Capiremo dove l’AI può davvero accelerare (testing, review, refactoring) e dove invece rischia di peggiorare la qualità. Chiudiamo con una sfida pratica: in 48 ore, mappa il collo di bottiglia più grande del tuo team — e portalo in retro o stand-up.Follow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe

🚨 CI/CD ≠ Pipeline automatizzataE no… non sono solo nomi altisonanti per la stessa cosa. La maggior parte dei team sbaglia su questo punto.E questo porta a rilasci più lenti, build rotte e sviluppatori confusi. Ma una volta che ho capito davvero le differenze…Come si costruiscono l’una sull’altra…E come un concetto semplice—il Trunk-Based Development—sblocca tutto... 🚀 È stato lì che velocità e affidabilità di delivery sono esplose. Oggi, nel nuovo episodio del mio podcast Weekly Pomodoro, ne parlo nel dettaglio:→ Cosa significano davvero CI/CD→ E come implementarli in modo efficace Se anche tu hai mai annuito in riunione facendo finta di capire la differenza tra i tre... 👀O vuoi finalmente sbloccare la tua pipeline di delivery... Devi assolutamente ascoltare l’episodio di oggi!Follow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe

🧠 It looks like LLMs are making devs 10x more productive.But something else might be... Over the past few months, I’ve been watching a pattern emerge.Devs rave about LLMs massively boosting their output. PMs boast about faster features. Founders post screenshots. VCs… well, they think they found the next gold mine. But when I zoomed in, something felt off.The devs getting the most value from AI agents aren’t doing anything “new.” They’re doing this instead:✅ Writing tight, testable code✅ Working in small, iterative steps ✅ Focusing on feedback and flow✅ Getting clarity before coding✅ Refactoring relentlesslySound familiar? It should. That’s the original Extreme Programming (XP) playbook. And it’s looking more relevant now than ever—just wrapped in AI.🚀 So what’s really driving productivity here?→ Is it the machine, or the mindset?→ The assistant, or the agile habits? IFollow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe

🚀 Are AI-assisted IDEs the future of development? 🤔In today's world, tools like Cursor are pushing the boundaries of what AI can do for developers. But... are they truly the game changers we’ve been waiting for?💡 After experimenting with Cursor in my daily development workflow, I’ve found some amazing advantages, but also some challenges.Here’s a sneak peek into my findings.--------------------------------------------------------------------------------------------------------------------Discover Learn Agile Practices: https://learnagilepractices.com/Subscribe to the newsletter: https://learnagilepractices.com/subscribeJoin the free Telegram channel: https://t.me/+2QAtoLNIgVU0NmU0Need help in developing your career in Software? Discover my coaching and mentorship program: https://learnagilepractices.com/coachingFollow me: https://danthedev.carrd.co/Follow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe

Working remotely doesn’t mean you’re working asynchronously. Too often, these two ideas get bundled together.👉 But remote ≠ async.One is a decision about space, the other about time. In today’s episode of my podcast Weekly Pomodoro, I unpack the biggest misconceptions about async work — and why being "async-first" doesn’t mean banning real-time communication.🚨 Going fully async may sound modern, but in practice it can slow you down, isolate your team, and break trust.✅ Still, in the right contexts, async work is incredibly powerful.--------------------------------------------------------------------------------------------------------------------Discover Learn Agile Practices: https://learnagilepractices.com/Subscribe to the newsletter: https://learnagilepractices.com/subscribeJoin the free Telegram channel: https://t.me/+2QAtoLNIgVU0NmU0Need help in developing your career in Software? Discover my coaching and mentorship program: https://learnagilepractices.com/coachingFollow me: https://danthedev.carrd.co/Follow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe

🗑️ Quanti sprechi ci sono nel tuo team di sviluppo... che nessuno vede?➡️ Bug in produzione. ➡️ Feature che nessuno usa.➡️ Soluzioni troppo complesse.➡️ Pull request che restano ferme per giorni.👉 Tutto questo ha un nome: spreco nascosto.E logora silenziosamente la produttività, il morale e la qualità del tuo team e del suo lavoro. Nel nuovo episodio del mio podcast Weekly Pomodoro ti porto in un viaggio tra i principali sprechi nel software, ispirato ai principi lean e agile.Scoprirai:✅ Quali sono le 4 fonti principali di spreco nel lavoro tecnico✅ Perché alcune sembrano “normali” ma sono veleno per il team✅ Come iniziare a eliminarle, una alla volta --------------------------------------------------------------------------------------------------------------------Discover Learn Agile Practices: https://learnagilepractices.com/Subscribe to the newsletter: https://learnagilepractices.com/subscribeJoin the free Telegram channel: https://t.me/+2QAtoLNIgVU0NmU0Need help in developing your career in Software? Discover my coaching and mentorship program: https://learnagilepractices.com/coachingFollow me: https://danthedev.carrd.co/Follow & subscribe Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:https://www.linkedin.com/in/daniele-scillia/One framework or practice per week, straight to your inbox — subscribe to the newsletter:https://learnagilepractices.substack.com/subscribe