I disagree heartily and would like to explain: I think it helps to view no-code as the latest iteration of a pattern that started back with COBOL and has inclu

I disagree heartily and would like to explain: I think it helps to view no-code as the latest iteration of a pattern that started back with COBOL and has included things like Excel, Wordpress, Squarespace, or Shopify wherein some common subset software tasks become massively deskilled (e.g. being able to set up an online store was once a massively profitable skillset and is not anymore). While understanding the problem to be solved is, of course, hard, implementing a solution is much easier if you can be freed from the most common concerns of translating your business solution to code. > You'll have to throw it in the bin if it turns out to be a success though! I think, again, excel shows this is unlikely to be true. There are billion dollar businesses running on a giant mess of excel spreadsheets (I've seen it). They're good enough and I expect a few of the current no-code contenders will go the same route. None of this is to say the end of software is here (and I don't think serious -people in the no-code space expect that), just that a new class of software may be going through a process we've seen other types of programs go through.