Making Software Design As Simple As Creating A PowerPoint Presentation
from the good-or-bad? dept
A few months ago we wrote about Charles Simonyi's efforts to build tools that would make creating applications as easy as making a PowerPoint presentation. While we wondered whether or not that was really possible, others were more afraid of the inevitable "idiot-ification" of programs if that happened. People like Edward Tufte insist that the dumbing down of our thinking by PowerPoint has dangerous consequences - so just imagine how he (and others) will react to the dumbing down of programming. Already, people revolt against ideas like Visual Basic. News.com, though, is running an interview with Simonyi where he describes in more detail the ideas behind Intentional Software. It doesn't sound quite as drastic as the original descriptions (though, still quite revolutionary, if it can be pulled off). They're not trying to build the tools to make it easier for non-programmers to program themselves. Instead, they're building a system so that programmers can build an environment for non-programmers to build subject-specific programs, which is actually quite different. As he explains, before, programmers would talk to subject matter experts about what they were trying to do, and then try to build a program that represents that. The goal of Intentional Software is still for the programmers to talk with the subject matter experts - but then to build a system for the subject matter experts to build their program. It still sounds like a very difficult task, and one that I'm sure will still draw plenty of complaints.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Reader Comments
Subscribe: RSS
View by: Time | Thread
Are we solving the right problems?
The concern I have isn't that we have easy enough tools for programming - it's that we don't have simple, intuitive ones for process/workflow modeling, which would help people avoid using programming tools to automate bad designs & processes.
I've seen too many situations where simple programming tools facilitate either or both of these bad-automation drivers:
- "Power Users" who understand a business problem, but don't know enough about programming to properly automate a solution, or even assess if tools like VB or Access are appropriate platforms for what's needed.
- "SWAT Developers", who know the tools well, and measure their success by how fast they can use them to implement a RAD-style solution on behalf of a client. These folks often have the same platform-assessment blindspot (i.e. just because you CAN build it in a given tool doesn't mean you should).
If you had good, easy-to-use tools to help model the problem/process itself, we'd have a lot better upfront analysis and successful solutions following them.
(Yes, there are some tools like this, but they're either too complex, or only suited to modeling processes that can be automated in Excel/MS-Office)
[ link to this | view in thread ]
Brilliant
[ link to this | view in thread ]