Adding the code to No-Code

Jorge Cortez
March 31, 2023
Read time

In the past couple of years I’ve seen how the no-code movement has been gaining strength and there is definitely a reason for it, no-code just makes things way quicker to build allowing for faster development times and reduces the need for a dedicated development team or extensive training, it even reduce the need of a really experienced developer to get most things done, which has been rising interest in development specially for people with little to no knowledge about software development.

While it is true that no-code apps can be really useful helping non devs get things done it also raises a lot of questions for new developers. The main question I’ve heard and seen around in chats, boards or just chatting with friends is, “does that means devs will get outdated soon?”.Well here’s my take on this, as a Full Stack Developer with 9+ years of experience working with al lot of different types of programming languages and tools I can fully say that it will not be the outcome of no-code. I my self was a bit sceptic about this apps at the beginning  and not gonna lie I used to think they’d limit the things we would be able to do (and being fair a lot of them do) but during the past year I’ve had a chance to change my mind on this.

I’ve been working on Webflow for the past year or so since that was the preferred platform to build sites in my office and I have to say it really helps making development quicker. it is easy to use and the one thing that I was sceptic about which was lack of customization was gone when I noticed I was allowed to add custom code on it and make things that were not built in happen.

Now for the bad part, and I don’t mean this is awful but I do find my self adding the same fix or custom piece of functionality over and over again in a lot of my projects. Don’t take me wrong this true for most projects regardless of the platform, but for most places we have a node module (or a nuget package if you’re one of those people) that will fix the issue with a simple approach. This is also true in  Webflow’s case but it mostly comes for greater functionalities. This is the main reason why I decided to take those fixes I’ve been reusing over and over again and put them out for people to use.

My Webflow-Utils CDN will be out for anyone to use so we can solve those simple things that are annoying to fix even when they’re just some lines of code away. over time I’ll keep adding to this as I find new fixes and ways to get things done, in the meantime though keep posted on my blog so you can find more 😉 and don’t forget there are some other amazing tools at least for Webflow that you guys can use and I my self use a lot like Finsweet  or Flowbase.

Eventually I’m hoping this project can be open for any dev to add to it so we can have a community based library to fix a lot of different issues and join forces to make everyone’s life easier! so let me know if you have any questions about my Utility packages and keep posted to my newsletters to get notified when it gets released and whenever I post again 😃!

Thanks for reading!