AI, Wappler, and the Importance of Knowing What You’re Doing 🧠

Hi everyone,

I wanted to share some thoughts about AI, not just in programming but in many different areas. There's often a misconception that AI is some separate entity, almost like a person or an employee on its own. In reality, AI doesn't have its own mind or consciousness like us; it's just made up of sophisticated algorithms, basically a bunch of complex instructions.

Now more than ever, people who've invested time and sometimes money into understanding how code works, how structures function, how databases operate, and how frontend-backend connections should be structured correctly are seeing real benefits. On the other hand, those who skip these foundational concepts often end up frustrated because they believe they can bypass essential knowledge. But this isn't just true for programming. I've seen the same issue in writing, where people don't know how to craft good prompts, resulting in poor quality content. It's also common in design some designers don't spend enough time learning about core principles like UI and UX, leading to ineffective results. The issue isn't the tool itself. Similarly, with Wappler, sometimes we ask things through AI and the outcomes aren't as expected. It’s not Wappler’s fault; rather, we often lack the necessary foundational knowledge to effectively handle this new technology, which requires a solid understanding of the problems we're asking AI to solve.

AI is an amazing tool that can seriously speed up our work. Sometimes, with just a brief description or a bit of context, it can deliver results that might otherwise require lots of explanation or way more time. But it's super important to understand that AI isn't magic, it doesn't automatically know exactly what we want or need.

For example, if you say something like "I want an app just like Facebook" or "I need a sales system like McDonald's," that's just not enough. These systems are huge and complicated, and AI can't just replicate them without detailed instructions and a solid understanding of what you're trying to do. Even when we give it lots of information, there’s usually still something missing to get a perfect result.

I really think we need to learn how to use AI properly. Just like a carpenter learns how to handle a hammer, we need to educate ourselves on using AI smartly and effectively. Understanding AI's limits helps us use it better and prevents frustration when it doesn't perform exactly as expected.

Unfortunately, I've seen AI used incorrectly, leading to disappointment and skepticism. This kind of misuse can hurt not just the user but also their team, their company, and their clients. It's key to remember that AI alone doesn't solve everything. We, as developers and professionals, need to provide solutions by understanding the software, our customers, and how they work every day.

For simple tasks, like recreating something basic such as the Snake game, AI might quickly give you what you need. But for custom solutions tailored specifically for clients, we need a clear understanding of their context, problems, and goals. Only then can we effectively use AI to enhance our work.

This is just my personal take on it, but I think now’s a great time to pause, reflect, and really understand how to get the most out of AI to do our work more efficiently, deliver better results in less time, and most importantly, solve our clients’ needs more quickly and effectively.

11 Likes

Very well put :+1:

1 Like

Such a good read, very true.

1 Like

Just finished a PKI (Public Key Infrastructure) digital document signing architecture with Claude Summit 4's assistance.

These are the main features created:

  • Database: employee_certificates table exists with certificate storage
  • Login API (/app/api/auth/login.json): Has certificate provisioning integrated after line with updateLastLogin
  • Signing API (/app/api/signatures/sign_document.json): Complete PKI signing workflow
  • Certificate API (/app/api/certificates/ensure_certificate.json): Automatic certificate provisioning
  • Frontend (/views/employee_sign_task.ejs): Professional signing interface with Web Crypto API hashing
  • Routes (/app/config/routes.json): Added /employee-portal/sign-task route

Current Status: About to test the end-to-end workflow. The login system uses Wappler security provider authentication and automatically provisions PKI certificates. The signing workflow validates certificates, creates cryptographic signatures, and updates task status.

As @Max_Saravia has said, what instruction does one issue to Claude to get the result?

4 Likes

Really interesting work, @ben . I’ve actually been exploring digital signature workflows myself for certain use cases, especially around document approval and compliance flows, so this is super valuable. Thanks a lot for sharing the architecture you put together, it’s very insightful and well-structured. I noticed you’re leveraging the Web Crypto API and Wappler’s security provider for seamless certificate provisioning, which is a great approach. Just out of curiosity, how many prompts did it take you to get Claude to produce something this complete? Did you need to refine the flow much or was it mostly straight through?

Hi Max, this is new territory for me, learning about the differences between electronic and digital signatures and the legal aspects of each.

The short answer: I have no idea of how many prompts, maybe well north of 30, mainly because I was on a learning spree.

After a couple of days of research to acquaint myself with terminologies and outcomes, I sat down with Copilot (the Microsoft one) and started asking questions. These questions included discussing alternatives, like including SSH for extra security and using third party solutions such as Boldsign and Docusign.

I did not want to use third parties because I want my app to be independent and not to have the extra financial burden.

This is what Copilot finally suggested:

A PKI (Public Key Infrastructure) digital document signature is used > because it provides strong security, authenticity, and integrity for electronic > documents. Here’s why it’s beneficial:

Key Benefits of PKI Digital Signatures

  1. Verified Signer Identity – Ensures that the signature belongs to the > correct person using cryptographic authentication.
  2. Tamper-Proof Security – If the document is altered after signing, the >signature becomes invalid, ensuring integrity.
  3. Legal & Regulatory Compliance – PKI-based signatures meet global > standards for electronic signatures, making them legally binding.
  4. Audit Trail & Timestamping – Provides a detailed log of when and where the document was signed, ensuring traceability.
  5. Encryption for Confidentiality – Protects sensitive documents from unauthorized access.

PKI works by using a private key to sign the document and a public key to verify the signature. This ensures that the document remains unchanged and that the signer’s identity is authenticated.

Once in Wappler, I guided Claude through the process, all in the Ask mode, until we reached a roadmap that I agreed with. The roadmap was divided into 4 steps so that there would not be a total meltdown when executing the instructions. The final instructions were given in the Agent mode.

I did come across a few hurdles where Claude did not have the faintest about the Wappler workflow. One instance, the login API was totally ruined by AI resulting in me having to do a complete remake of the API. I then showed Claude the correct steps. Claude learned and did not repeat the mistake.

All in all, a great experience and a great learning session for both Claude and me.

3 Likes

Nice post @Max_Saravia and @ben !

I liken AI to taking on a new employee.

Give them a simple task like sweep the kitchen floor and they will probably get it right.

Ask them to run the entire administration of your business, and you know you’ll need to give them a whole lot of background and constraints before they do what you are looking for. You’ll then will want to regularly meet with them to give direction.

Sometimes you know a contractor could potentially do a great job at something, but by the time you’ve explained it, waited for it, reviewed it multiple times, got frustrated, and then had to pay for it, you just decide it’s easier to do it yourself.

And yet… you can end up with a colleague or employee where after a while you just learn from each other and work in perfect harmony, beautifully in sync, guiding your business to bigger and better places.

IMHO, it’s all just the same with AI!

4 Likes

Hi Ben, sorry for the late reply. I was taking a few days off with the family up in the mountains and just got back to civilization, :snowboarder:.

First of all, incredible work. I think what you built is really impressive, but what struck me most is something you mentioned near the end: the idea of AI as a complement, almost like a tutor. That’s something I’ve been thinking about a lot lately too. Not long ago this was pure sci-fi, and now it’s actually happening. We’re able to learn more, and better, thanks to these tools.

The idea that AI doesn’t replace us as developers, but actually helps us become better ones, really resonates with me. It gives us the chance to learn faster and in a more structured way, compared to spending hours digging through forums or GitHub repos trying to figure out how to do something or whether someone has already done it.

And yeah, I can totally relate to what you said about Claude messing up the login API. That kind of thing happens to me all the time. I often end up dropping the AI halfway through and doing the rest manually myself. But the learning process from those moments is actually super valuable.

I also really appreciated what you said about not wanting to use third-party services. That’s exactly what I try to do with all my apps too. Not just to keep costs competitive, but also to have more control and independence for myself, for the software, and for the client. That mindset has become core to how I build things.

Thanks a ton again for sharing your whole workflow and all this valuable info. It’s inspiring and super helpful. Looking forward to seeing where you take it next!

1 Like