I enjoy seeing these talk so much. And I feel it's sad that someone needs to defend value of design against broad community of software developers who have understood Agile as "do not plan" vs. "write functioning code" and do not feel need of understanding deeply problems they are about to solve.
In Mechanical engineering we call it the implementation of design intent. And we basically put in our drawings the best representation of our design intent. Why coders don't do a drawing of your design intent. We could also write everything down in words or codes. But that is not usable. Try to describe the shape and size of a complex part in words or code. No you need to have drawings that show pictorially what you are working on. You have to develop a graphical representation of code. Like in electronics they have drawings for circuit boards and even chips.
Don't think about it as constrains. Think about it as highlighting what you want and un-highlighting what you don't want, to create a particular and unique system with it's own character..
Here's the theremin video, he doesn't show the right thumbnail: "Carolina Eyck plays Gabriel Fauré" ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-7l9YcewEumw.html That's a small letter 'L' after the 7.
