4
1 Comment

Why I always resort back from no-code to code

TLDR; Tow major reasons FREEDOM and OPTIMISATION

So basically whenever I start something using no-code technologies, I find myself resorting back to code. for two major reasons.

1- FREEDOM: when I start something using no-code and it gains some traction I typically find myself coming up with more features/integrations/etc. I always hit a wall at some point using no-code tools due to their limitations. When I am using code I have to freedom to use any stack, integrate freely with anything and install any tools on my servers. Basically I can create whatever I want the way I want it ..

2-OPTIMISATION: If you have been coding for some time chances are you have many of the building blocks already written for other products that you have built. I typically find it faster to pull these parts together form different products and adapt it to whatever I'm doing than using no-code tools. This allows me to Save Time and Money in addition to being able to optimise for (performance and specific use case).

This isn't to say than no-code tools are bad or not worth by any means . They allow you to start/test things quickly sometimes at no cost, however for me there is always point of diminishing returns that happens with using these tools and I find myself faster and more productive using code in the long run.

on November 15, 2022
  1. 3

    I agree with your points. No-code is great for small teams or an MVP. It usually starts being a functional and performance problem when the project grows.