6
9 Comments

What do you struggle with the most?

If we were chatting what would you say you struggle with the most when it comes to no-code?

Is it generating an idea? Best practices? Picking a tool? Understanding no-code limitations?

I'd like to know where you struggle the most. Or if you did struggle at some point but are past it now, what was the struggle and how did you overcome it?

  1. 2

    Learning the freaking thing. It's like a totally new language for me with new concepts etc. I wish more no-code creators would focus on USABILITY i.e. making things EASY to use vs. introducing a bunch of features.

    1. 1

      Yeah, that makes sense having to learn the tool in addition to how to build out your idea

  2. 1

    For me, I'd say it'd be when to use it. As a developer, I have a stack that I'm already use to and the skills to build stuff, and I'm afraid the no-code tools are going to be underpowered for what I'd want to do.

    However, for the times it has been an appropriate tool, it's been much faster to get something done. So now, I'm trying to transition to leaving commoditized programming to no-codes, and focus my programming on core competencies people haven't commoditized yet.

    I think most traditional programmers will poo-poo it by calling it 'not programming', but I keep in mind that assembly programmers use to call FORTRAN "not programming" because it was too high level.

    1. 1

      ah, I see. It's great that you have both skills, though! My background is in software engineering, but honestly, I use the structure that I learned far more than the syntax. I wish I could have just studied JS to powerup anything no-code related. :)

      1. 1

        Syntax is usually not a concern for me either. It only rears its head as something to pay attention to when I learned other programming paradigms, like logic programming.

  3. 1

    Hey Lacey, it has to be idea validation: I write about it here upvoted.io

    1. 1

      Interesting! I'll take a look!

  4. 1

    For me it would be keeping track how the whole application works.

    There are so many different moving parts that it's hard to keep track on how the data flows between all the services.

    I have a notes application in which I write down which services authorize with one another and how / what data they exchange. Otherwise I wouldn't have any idea how the whole application works. I'm also concerned that when I remove one account / integration that the whole thing falls apart.

    1. 1

      Definitely - that makes sense and kinda hits on @zerotousers 's pain point, as well. As much as I love no-code tools, they are nuanced in how they work, even if they operate off of the same principles.

Trending on Indie Hackers
After 10M+ Views, 13k+ Upvotes: The Reddit Strategy That Worked for Me! 42 comments Getting first 908 Paid Signups by Spending $353 ONLY. 24 comments I talked to 8 SaaS founders, these are the most common SaaS tools they use 20 comments What are your cold outreach conversion rates? Top 3 Metrics And Benchmarks To Track 19 comments Hero Section Copywriting Framework that Converts 3x 12 comments Join our AI video tool demo, get a cool video back! 12 comments