Drawing on Donald Schön's 'The Reflective Practitioner', this piece argues that software development is fundamentally a conversation between developers and the problems they face. Just as an architectural mentor and student iterate through framings, tradeoffs, and discoveries while designing a building, software professionals must engage deeply with their situations to uncover details that can't be seen upfront. Agile processes are framed not as speed optimizers but as risk reducers that enable iterative learning. The post emphasizes that solutions should reflect accepted tradeoffs, and that tacit knowledge gained through experience is difficult to fully articulate.
Table of contents
Back to the futureChatterbox or black boxIf you enjoyed this post, you might also like:Sort: