#13 - What is DevOps?
Introduction
Do you have some bad habits in your life? I am sure you do, well you can either ignore this bad habit or figure out ways to change your life for the better.
If we move beyond ourselves and towards a low-code/no-code development team. Bad habits become costly in resources, manpower or even scepticism in adopting low-code/no-code tools for their organisation.
Bad Habit 1: Doing Everything in Only One Copy
The key feature of No-Code/Low-Code is that change is made quickly and without repercussions. If a mistake was made, you can quickly undo the changes made to the software. This makes sense for a non-tech trained low-code/no-code developer to keep just a single copy while making changes directly on it.
You run the risk that this copy is not working with the expected experience or you had deleted something accidentally. This could also mean that you are unable to fix any problems that may arise due to multiple developers/users making changes to your software.
There is a reason software developers use version control software like Git or Subversion. Along with multiple copies/environments of the software. For traceability of changes and a resilient system that can recover from failure.
Bad Habit 2: You Don’t Need a Developer
Depending on the creator of the Low-Code/No-Code platforms. The majority of these platforms are easy to learn and build without the need to understand software development.
The usual case in reality for no-code platforms is that when you move towards further customisation of the software using the advanced features of these platforms. You might be required to learn knowledge or skillsets that a developer should possess in HyperText Markup Language (HTML) or Cascading Style Sheets (CSS)
The apparent issue is when you start to use Low-Code platforms that assume you possess skillsets or knowledge to leverage upon these platforms to do more with less. They could also be like Webflow to provide you with videos to cover the gaps that you might find along the way.
Bad Habit 3: No Documentation Found!
One of my cardinal sins that a software project must have is technical documentation. This can be quite a bone-chilling & frustrating experience for a developer. When a developer is tasked with creating, integrating or maintaining a piece of legacy software.
We do this because, with documentation, we can provide context and understanding for the piece of software. Therefore one of the best practices for developers is to keep up-to-date with relevant documentation so that anyone can use or make changes to it.
We must always assume that someone will be taking over what we had done to start anew or to continue on this piece of software.
Conclusion
In summary, these are bad habits you would get when you are using no-code/low-code tools. Therefore I would suggest that you look at addressing these bad habits.
Before these bad habits become a problem that will cost you greatly in terms of time and resources that you have to pay down the road in the future. I would also strongly suggest you get an experienced developer to become the advisor or part of the low-code/no-code team.