Be Obsessed with developer efficiency You know what developers like to do? Write code. Do you know what business like their developers doing? Writing code. Do you know what both businesses and developers absolutely hate? Inefficiency!
Was that too obvious? Well, you might think so at the surface, but efficiency is a deep rabbit hole and can be defined in a ton of different ways in the context of development.
I am a software developer. I write code for a living. You should know this before reading any further.
Ok, with that out of the way I’d like to have a pretty serious talk about no-code/low-code solutions and how I think they actually waste more time than what they save. They may even cause more bugs than what they prevent.
OK, But First, What is No-Code / Low-code? low-code is like building blocks Before I begin my rant, err - findings, maybe I should start with a brief definition of what the heck I’m talking about.
So I’ve been thinking about something.
If a picture is worth a thousand words, does a thousand-words description make a better picture?
At this point everyone has heard about DALLE-2. It’s an AI art generator that will take a human written description of a picture and attempt to create it. If you’ve tried it out, one thing you learn pretty quickly is that the more detailed a description you write, the more accurate the generated photos become.
It’s time for a little self-reflection.
Take a little time to think back over every single project you have ever created. OK, now right at this moment, what are you thinking about? Are you thinking about the code? Are you remembering the language, the functions, the classes? Or, are you think about what the project did? Are you thinking about the problem that it solved?
Well, if you are like most people in this world, you are thinking about the latter.
Development + Operations = DevOps. OK, so I don’t know who needs to hear this because it seems like such an obvious thing, but DevOps is not a job title!
There is no such thing as a “DevOps team” or someone who has decided to “do DevOps” as a job. If you think that there are developers and then also DevOps, all you are describing is the old way of doing things with a fancy new name.
