Mastering Software Engineering
Juval emphasizes the importance of understanding volatility in software design and the need for a rigorous engineering discipline. He argues that true mastery comes from extensive practice and training, akin to other professions like medicine or aviation. Quick fixes or "magic bullets" are myths; instead, a deep commitment to learning and refining skills is essential for success in software development.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
Episode 407: Juval Lowy on Righting Software
Related Questions
How do I know if I'm overengineering and doing too much upfront design in software architecture for the episode 2 tools to get you 90% operational // Michael Del Balso - Willem Pienaar - David Aronchick // MLOps Meetup #50 and the clip Lessons from Failed Projects?
How do I know if I'm overengineering and doing too much upfront design in software architecture for the episode "2 tools to get you 90% operational // Michael Del Balso - Willem Pienaar - David Aronchick // MLOps Meetup #50" and the clip "Lessons from Failed Projects"?
How do I know if I'm overengineering and doing too much upfront design in software architecture in the context of the episode From Idea to Production ML // Lex Beattie - Michael Munn - Mike Moran // MLOps Meetup #61 and the clip Maximizing Complexity, based on the insights from the episode The Pragmatic Programmer - The Evils of Duplication and the clip Fragile Codebases?