Why No Code Makes for Bad Software
by Jean-Raphaël Poulin Arguin, Founder / CEO
Why No Code makes for bad software
One of the first things you learn as you graduate from an intermediate developer to a senior one is how important data structures are.
It really all starts from the data.
Bad data choices lead to longer development times, more bugs and poor user experience.
One way you can tell a data architecture isn't good is by how hard it is to build features around it.
Programming is data transformation.
Having limited control over your data structure makes building software harder.
NoSQL databases were seen as this brand-new innovation that would kill relational databases and help developers ship faster.
NoSQL was more flexible that's why everyone thought it would make things move faster. (also very scalable)
The truth is that everyone went back to relational databases a few years later.
Lack of rigid structure around data leads to spaghetti code.
If data is not structured correctly, every new task gets more complex.
Yes, a No Code kid can build a SaaS in a weekend.
No, that SaaS will not scale.
Adding a feature is gonna get progressively harder every time.
Duct tape here, crazy glue there cannot fix bad foundations.
Yes, you can learn to code in a year
No, you cannot expect to build intelligent things in the first year.
Experience is the only true way to learn how to properly structure your software's data.
You'll make mistakes and you'll learn from them.
Interested in learning more about how technology can transform your business? Reach out to our team below!