How do humans build so quickly?

Please understand that I find it amazing when individuals do this and that I like reading the posts. As an engineer, I just want to know how people manage to make things so quickly.

A LOT of what’s being created is half-baked, to be honest. There’s some great stuff out there, but there are ten times more bad solutions.

I won’t name any specific websites, but I’ve tried:

  • SaaS platforms that let me impersonate other organizations when posting.
  • SaaS platforms that had accessible paths because they weren’t properly secured behind authentication or permission walls.
  • SaaS platforms with landing pages that looked like they were made by a five-year-old.
  • SaaS platforms with ideas that are just poor or have almost no audience potential.
    And that’s just the beginning.

There are also a ton of AI wrappers available, which are essentially three pages long and may just be a template with different text, colors, and images: landing, login, and chat pages

People with front-end experience, templates/boilerplates, BAAS, LLM, and a lack of empathy find success with these shortcuts.
I suspect some people mass produce under several identities. Like, there’s certainly at least one person that spams it relentlessly under three different names every day. While most people spend months or years working on one. A trend emphasizing quantity has emerged, with 12 per year or one per week…

Completely concur! Furthermore and I won’t lie to you our SaaS is really an additional AI wrapper. The MVP was assembled by my spouse in a few short hours. On the landing page, we explicitly inform users that this is really an OpenAI/GPT wrapper. People don’t mind paying $x.xx/mo to essentially just use our GPT prompt repeatedly, with a few variables added in that make it unique, though, because it produces results.

Many “founders” overstate things or use it as a marketing gimmick, be beware. Say something like “learn how I built my Saas in just 4 hours and 27 minutes” and then take you through an onboarding process that might involve a training or a worldwide marketing awareness program. Yes, there are a ton of templates and shortcuts to get you started, but I believe good, reliable software takes effort. Just my two cents

By what do you mean? I spent an entire afternoon building an ERP while intoxicated and lounging by my pool. Five hours later, I had 8,000 paying clients and an 80K monthly revenue. Microsoft had already reached out to me, expressing interest in purchasing the ERP for $500 million. Would you like to receive my complimentary eBook?

Here is a lot of needless hatred. Some individuals just find it hard to accept that some people work more, are more committed to a project, and will sacrifice everything for it. The momentum results from this.
Having the appropriate resources also helps, but that’s a topic for another conversation.

Out of sheer curiosity, I can’t stop building projects. If I start to wonder if something can be created, improved, or rewritten, I’ll blink, and suddenly three days have passed with me having a barely functional prototype. A few more blinks later, and it’s either mostly complete or completely overwhelming! That final 10% often feels like another 90%, and while working on that, I tend to get sidetracked and end up creating several more projects in the same way.

I’m not sure if this is common for others, but right now, I’m debating with someone in another post who claims I can’t build a full-stack application with custom AI integration in just a few days. Even though I’m juggling four other projects, I’m tempted to quickly create a GitHub for that project just to prove a point.

So, fueled by curiosity, a bit of spite, and the need to meet my commitments to stakeholders, I usually build projects pretty quickly

They are simply superior to us; we can never catch up to them because they are quicker and smarter. It’s best to just go on your own journey without giving it any thought.

We are fortunate to have a technical founder that works for his firm and develops SaaS. He comprehends the goal of our product and is sufficiently passionate about it to put in long hours after work to fulfill our deadlines. Also, there are a ton of new tools and resources available to aid in pre-planning; as a result, our technical founder only needs to code because everything, including the user interface, has been carefully thought out beforehand.