![PawCast with GeePaw Hill artwork](https://is4-ssl.mzstatic.com/image/thumb/Podcasts123/v4/f7/6a/bc/f76abc91-b6f4-eb95-39f5-ecae7658350c/mza_2663806889298342520.jpg/100x100bb.jpg)
Model-View, The Desktop, and TDD | #71
PawCast with GeePaw Hill
English - July 10, 2020 09:00 - 11 minutes - 20.1 MB - ★★★★★ - 6 ratingsTechnology Homepage Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed
The basic idea behind all Model/View schemes, and there are several of them, is just this: draw a thick line between what your program does and how your program shows what it does. In other words, it's a compositional heuristic, guidance for how we break our problems into smaller problems. Give some objects/modules the responsibility for doing the work, and give other objects/modules the responsibility for showing the work. Tho it was originally conceived in the smalltalk world, there are many modern usages of the idea. Nearly all UI-centric frameworks take the Model/View split as their starting point.
---
You can read the full transcription of this podcast over on GeePawHill.org. Any feedback, you can always tweet @GeePawHill on Twitter, or drop a voice message via the voice messages link here on Anchor. If you are interested in becoming more involved in the Change-Harvesting community, click here to learn how to join GeePaw's Camerata.
---
Send in a voice message: https://podcasters.spotify.com/pod/show/geepawhill/message