After a year of automating, improving workflows, and testing no-code tools, I hit a wall.

But not just any wall. This was a familiar obstacle in the realm of coders—a barrier that made me feel like a muggle attempting to access Platform 9¾, where only the magically inclined (coders!) know the secret to crossing over.

It all started when I wanted to create databases and sync them— sounded exciting at first but every iteration of building a synced database… well sucked.

But alas, I realized I had been using the wrong tool all along. It was like having a thousand family photos to organize but only one binder to contain them all. How do you avoid sacrificing precious memories? And where do you even begin sorting, let alone prioritize?

It boiled down to this: I’ve been trying to build everything with an integration platform when I should have been looking at a sync platform. Now, if I was an advanced coder, this would be light work. But I’m not. To tell you the truth, I didn’t really know there was a difference, and the impact they both have, until recently.

How did I find this out?

Yes, YouTube has been my best friend for information. After watching a YouTube live video, I checked out this no-code operators course. Not too technical but more of an overall, “future of no-code.” It was a dope breakdown of the levels and impact:

1. No code operators
2. Automation specialists
3. No code builders
4. Chief automation officers

After seeing the assessment, I found out that I fall into the category of Automation Specialist. Cool. But there was one part of the overview that had me bamboozled. I didn’t know the golden rule of no-code/low-code, which is the tool for the right job. Yes, you can build anything with code, but sometimes you just gotta pick the right tool for the task at hand.

And then, the plot thickens.

I had the pleasure of chatting with one of the owners of 9x, Alex, the voice and guide behind the course. Here's what I uncovered:

Migration from Trello: His team bid farewell to Trello, migrating to platforms like Airtable and Code because Trello just couldn’t keep up. I use Trello A LOT, so this had me thinking 🤔

Custom Portal Development: Forget about shelling out big bucks for custom portal development. Alex let me know that crafting your own portal using tools like Airtable can be achieved in just 1-2 afternoons.

The Two-Way Sync Debacle: Alex cautioned against creating a two-way sync with make.com, citing firsthand experience that it can get overly complicated. This was the biggest shock for me. Let’s dive deeper:

• The threshold for people to start using no-code tools who have no clue about code is very low. Now, the threshold to get into low-code and actual coding? Super freaking high.
• It’s all fun and games until you try to make complex databases.
• Once you dig into no-code solutions, you slowly realize that having a foundational base for yourself is crucial. There’s a knowledge gap between no-code, low-code, and coding because it’s so new. Oddly enough, searching for no-code on Google Keywords shows it hasn’t really broken into North America yet; it’s more popular in South Africa and Europe. Makes sense.

This leads me into the new question about thresholds, as Alex explained:

Developer Enthusiasm and Traps: Beware the allure of reinventing the wheel. Starting developers often fall into the trap of wanting to build everything from scratch. Alex advises leveraging existing technologies rather than succumbing to the "Not Invented Here Syndrome."

I see it like this: No-code entry is easy. You can make simple stuff, easy stuff, and it feels quite good. Then as you want to build more and more stuff, the threshold into knowledge grows exponentially. I had this chat with a friend the other day, and I put it like this: the low-hanging fruit keeps the newbies engaged and excited about the process. It’s like starting to play guitar: you can strum a few bars, but don’t expect to rip off solos like Slash or Mayer right away. You just want to play "Wonderwall" for your mates and enjoy that sweet taste of accomplishment.

Core principle: Start with Existing Tools: Before you dive into building custom galaxies, check out the stars that are already shining. Building a CRM with no-code tools on your first go? Not recommended. Opt for existing solutions.

Process Adaptation: Sometimes, you've got to tweak your business processes to fit the tools available rather than muscle the tools into your predefined boxes. Alex’s shift from Trello to Airtable is a classic example. If it gets you 80-90% of the way there, you’re golden.

As Alex aptly put it, "People in no-code are developers, trying to build something new that already exists." Wise words to think about as we navigate the exciting landscape of no-code/low-code solutions.

Hope you enjoyed this totally unstructured and all-over-the-place post.

Until next week ✌️

H