wardleymaps.com is for sale. Make an offer
Start mapping

From the read-only archive of the Wardley Mapping community forum (2018–2023). Category: Questions, Answers & Random posts. Posts are by their authors. Links to sites that moved or closed point to link notes.

Since the topic of conversational programming seems to attract a lot of attention, and have a significant impact on things that are very close to my heart (programming), I have decided to map it.

This is a map representing the landscape in the past (say, pre-2005). I would say the landscape was as follows:

5c8b74ddb2a932006083a49a

As you can see on the map above, there is plenty of custom-built components, which form together a wobbly tower. It does not mean that building such a solution was impossible, but that it would be ridiculously expensive (as it is usually the case if you don’t use standard and predictable components), and it would bear a significant risk of not addressing real customer needs (as conversational programming would be something completely new). I think that IBM Watson fits such a description.

Time has passed, and things have changed a bit. We, as the industry, have learned quite a lot:
5c8b7d7ab2a932006083a4cc
The same map without diff, just things as they seem to be today (for the sake of readability):
5c8b7d7ab2a932006083a4cc%20(3)

Conclusions:

Great stuff. I like your analysis, the threshold to implementations has lowered and in some places something close to this has happened.

I’ve been fascinated with natural language parsing since I worked on a chomsky type 0 parser in the 1970s. All I’ll say about that is Lexicons aren’t enough; It has to be phrase based.

Ever since the fifth generation computing fiasco people have talked about conversational programmers workbenches. They have to do some things we humans can’t though because otherwise we could just employ more programmers apprentices.

More recently convdev has become a thing. Although like “Agile” the term has become subverted.

In one project someone plugged chatbots into sharepoint. Quite a lot of the grunt work for devops was parsed out of comments.

Somewhere I have a diagram for an AI supported development environment, and it indicated to me that conversational connected speech is still the bottleneck. Most modern dev IDEs now have snippet handling and do automatic refactoring. What has been happening in chip layout for years is starting to happen in software layout.

I’m not sure that edge (or even corner) cases are a problem. In test world there are generators that create all permutations of variables and the results always find unexpected cases. I’m sure generating many (millions) of variations and annealing solutions that meet requirements can (and probably are) done now.

Once again mapping proves invaluable and a great bit of work, thanks.