^Tagsoftware writing

In my previous article, I noted that what programmers do is translate ambiguous specifications into very exact specifications, taking into account all of the specific subtleties that the implementation requires. However, I recognize that those not familiar with custom software may not recognize the problem. This article describes in additional detail the kinds of considerations that cause no-code solutions to be problematic. The essence of the problem is this: there are an infinite number of possible ways your business could possibly work, but only one way that it actually works. The work of the programmer is to make sure the software matches the specific way that your business works. Let’s take something simple like calculating shipping. It might be easy Read More ›

For at least the past twenty-five years of software development, people have been claiming that, using this tool or that tool, we will be able to build software with “no code,” and that our tools will build code for us.  The claims have varied with whatever the current technology is. In the 1990s, the idea was that we could have a system which allowed building software entirely with drag-and-drop interfaces. Tools such as Visual Basic, Delphi, PowerBuilder, and even Microsoft Access made people think that this was an achievable dream. It turned out not to be deliverable on its promises. We’ll get more into the “why” later on. Today we have a new set of tools and a new set Read More ›