There is a well known software design paradigm that is called “Convention over configuration“. At its core, it aims to make software development easier by reducing the amount of decisions that a developer has to make when writing software. It accomplishes this by providing the developer with a set of rules or conventions to follow. That in turn reduces the amount of configuration and scaffolding needed to get to the software built. The most common example that gets thrown around is that of a class to database relation. If your class is called “Posts” your database table name would be called “posts” too. No mappings or configuration required. By following defined rules and conventions, developers can almost always build their software in a standardised way. That means writing less code and focusing on what they’re really good at, solving complex problems. Some of the biggest and best software frameworks and libraries are built upon this design paradigm, and for good reason. What if however, we approached the paradigm from a different angle. What if we applied it to how we design our WordPress plugins from a users perspective rather than software design perspective? What does this mean
Share This