It depends how you define "code". If "code" is a system of rules to convert information from one form, to another, then software will always need code. This ar

It depends how you define "code". If "code" is a system of rules to convert information from one form, to another, then software will always need code. This article talks about the "agile", but creating software has never been about code. It's always been about delivering value. Code or no code, creating software and delivering value is no trivial task. I believe we will always need to define the conditions and boundaries that computers need to work within. What we need to get better at is defining and communicating what those conditions and boundaries need to be. I think one great example of that is Behaviour-Driven Test (BDD) and gherkin. Gherkin is code written in a business readable, domain specific language. Programming computers may change and complex computer code will become abstracted away further, but no matter how you look at it, programming computers will never totally disappear.