Discover
Learn Agile Practices
Learn Agile Practices
Author: Dan the Dev
Subscribed: 8Played: 174Subscribe
Share
© Learn Agile Practices@2026
Description
Unlock Your Potential with Learn Agile Practices
Harness the power of Agile Software Development with technical practices, and accelerate your journey to becoming a senior software engineer.
Enter a learning ecosystem & Achieve Technical Excellence
Join a community dedicated to mastering agile development methods and software development methodologies. Empower yourself to become a better software engineer with our personalized coaching and hands-on support.
https://www.learnagilepractices.com/
Harness the power of Agile Software Development with technical practices, and accelerate your journey to becoming a senior software engineer.
Enter a learning ecosystem & Achieve Technical Excellence
Join a community dedicated to mastering agile development methods and software development methodologies. Empower yourself to become a better software engineer with our personalized coaching and hands-on support.
https://www.learnagilepractices.com/
84 Episodes
Reverse
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







