4 ms·
The author, like many people, is conflating two issues that result in complexity in software engineering. (Among many others.) First, is the fact that we need
by gfodor 16y ago
The author, like many people, is conflating two issues that result in complexity in software engineering. (Among many others.)
First, is the fact that we need to tell the computer what to do. This is, I think, what the author thinks of "programming" as. He's right, it's hard, and it's gotten easier as we've improved our tools and languages that enable us to tell the machine what we want it to do.
However, second, is the problem of taking a description of a problem, from another human, and translating it into a piece of software. The source of this information, in the worst case, is a verbal description. At the extreme, it's a written specification (which, as we all know, ultimately ends up in the trash.)
It's this knowledge capture problem that I think has a wide open opportunity. There needs to be a better way for the 3rd party humans to describe their problems in a way programmers can build on top of. It doesn't have to be precise, it doesn't have to be perfect, it just has to be better than the status quo of verbal descriptions and .doc files of specs.
- bennysaurus 16y agoThe author doesn't touch on it much, but part of the added complexity is each person thinks differently too. “Create a window with a table view, and then when someone clicks a button, add an entry to the table view” If you asked a room of 30 people to draw you a picture of exactly what that sentence means, you will get 30 different results. Building on your comment, I'm not sure the actual act of programming would be hard if you had to take only 1 person's viewpoint into account and work off that.
- kevinburke 16y agoIf we figured out the best practice for common GUI cases (ex. in tables, shade every other row light gray), you could hide the complexity from the average program writer and make better decisions for them.
- extension 16y agoA GUI toolkit is already a set of best practices. Designing one is a difficult matter of balancing convenience with flexibility. Make it too basic and you complicate special cases and impede innovation. Make it too detailed and you force noisy code and wheel reinvention.
- maigret 16y agoRight. I think that's why good toolkits have good default behaviors that you can also easily overwrite through well documented APIs. I think a good abstraction should let you also access the underlying layer for special cases.
- extension 16y agoAn API designed for overriding still suffers from the same compromise. Any particular use case will want to override a specific set of functionality and nothing more. More fine grained overridability means more overhead complexity. Simplicity means you have to override functionality in large units, likely reimplementing most of it.
- ippisl 16y agoI know there's application simulation tools , that let business users build a running simulation of an application, and let them improve and test it. from it they can generate more accurate specs for the development teams. The claimed benefits are quite high: 50% reduction in app specification time , and 75% reduction in development changes.
- hasenj 16y agoIt's often a mistake to think that a human can describe his requirements. People don't really know what they want. No one could have gone to Steve Jobs and said, hey, I want a phone that can read mail, play music, download apps, and has a touch screen. No one thinks in these terms. At best, people would say: I want a device that I can carry around with me that can act as a small computer. There's a wide and huge gap between "creating great products" and "gathering user requirements".
- gfodor 16y agoAn improved means of communication would not presume to solve the problem of humans being unable to precisely describe requirements. The point is right now the status quo is that people are unable to describe the requirements to a satisfactory degree of precision, for those that they do have the ability to describe. Note that this means of communication can apply not just to third parties but to those within the organization (designers, product people) who need a means to describe their own, more specific vision in terms that can be then used by programmers to turn into working software.