Episode from the podcast Full-Stack Developer
Episode
Released Sunday, October 25th 2026 15 min
Show notes
Code is plain text In the previous activities, you learned that a program is a set of instructions written for a computer. You also learned that your work is stored in files and folders, identified by names, extensions and paths. Now you need the rig...
15 min
The Product Backlog: the single list of work You have just seen the three Scrum accountabilities: Product Owner, Scrum Master and Developers. You now need to know what the Product Owner actually manages day to day: the Product Backlog. According to t...
15 min
Why debugging needs a method A bug is a gap between what you expect a program to do and what it actually does. You already know how to read an error message without panicking. You also know how to break a problem into small, unambiguous steps. Debugg...
15 min
Scrum and the Scrum Team In the previous lesson you saw the agile principle: deliver often, learn, adjust. Scrum is the most widely used framework for putting that principle into practice. It is described in a short official document, the Scrum Guide...
15 min
Why agility exists In the previous activities, you built a complete project plan. It covered the scope, a Gantt chart with dependencies and a critical path, a budget with contingencies, and a risk register. This approach is called predictive, or plan...
15 min
Why an error message is your ally When red text suddenly fills your terminal, your first instinct may be to think you broke something or that you are not made for this. That reaction is normal, and every developer has felt it. In reality, an error me...
This podcast, its content and its artwork are not owned by, affiliated with, or endorsed by Castquire.
Up next