Why the Fuss About Conversational Programming?

We’re still waiting for those conversational programming environments to fully form but we’re getting close. The technology is there (i.e. large language models), the concept is there (i.e. conversational programming) and the attitude is there (i.e engineers getting swamped by complexity). All the factors needed are in place, it’s only a question of how quickly this evolves and which actor launches first at the right level of abstraction — Microsoft or AWS? (View Highlight)

whomever does drive this to more of a utility will gain the advantage of the meta data for applications built on top. (View Highlight)

The speed of one company with engineers building systems through conversational programming (i.e. a discussion with the system) versus the speed of a company whose engineers are messing around with containers and orchestration systems (such as kubernetes clusters) versus the speed of a company whose engineers are still wiring servers in racks. (View Highlight)

You’ll need less engineers. Nope. See Jevon’s paradox. You’ll need to retrain to a new world but you’ll end up doing more stuff. (View Highlight)

As a rule of thumb, if you’re not currently a hyperscaler then your platform engineering team should be spending most of its effort in getting rid of things from your organisation and building instrumentation for this. (View Highlight)