Nocode, lowcode and the importance of internal standards

In nocode and lowcode standards are everything. And I don’t mean standards through standardisation organisations such as W3C or ECMA. No, I mean standards as in finding the generalised solution to the problem at hand, and solving it such that an internal standard organically grows out from your code. In many ways this is “the secret sauce” in Magic. When we generate a CRUD web API backend using our tools, what we are actually doing, is to create a standardised solution, where all endpoints have a very specific structure. Below is parts of our assumptions in these regards.

  • All Update endpoints are using the PUT verb
  • All Create endpoints are using the POST verb
  • All CRUD endpoints associated with the same database table have the same URL
  • All Create endpoints returns the primary key(s) for the newly created record, as long as these are automatically generated by the database
  • Etc, etc, etc

The above results in an “internal standard or convention”, which the computer can rely upon, allowing it to create predictions in regards to what an endpoint does, how it behaves, what input it requires, and what output it returns. For the record, there are literally hundreds of additional conventions applied by Magic in addition to the above. Regardless, the result becomes a uniform solution, built around a set of pre-defined conventions and standards, allowing the computer to 100% accurately “predict” what the code does.

When the machine can create accurate assumptions about your code, everything else comes natural

Without these types of conventions, your life would be impossible. For instance, every time you enter a car, you know where to find the ignition key hole, you can trust that all manual gear shifts are roughly the same, and that the gas pedal is to the right. If each car manufacturer had different positions for its gas pedal, driving cars would be literally impossible for humans. In such a regard there is nothing new to what we are doing, we’ve just taken it to a new level.

The conclusion here is that regardless of whether or not you want to use our services, you can still benefit from internalised standardisations and conventions. Simply because, as you standardise something, you’re one step away from automating it. And once you automate it, you become more productive. As you become more productive, you become more valuable. Until you reach the point where you can create 100,000 lines of code, in literally one second!

In the above video I am demonstrating how to create 100,000 lines of code in 1 second!

If you want us to help you with standardising your internal models, feel free to contact us below to start the conversation.

By servergardens

Create .Net Core CRUD APIs wrapping your SQL database in seconds

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s