After three decades of coding, I’ve never seen anything transform how we build and think about software as fast as vibe coding does right now.
I’ve been writing code since I can remember. From Basic programs and C compilers to video rental systems in Clipper and database logic, until I eventually became a Salesforce Developer.
That’s more than 30 years having fun debugging and solving problems. I’m lucky to work with something I love, and I still enjoy learning every single day. In tech, for better or worse, there’s no end to learning.
I’ve lived through the internet revolution that reshaped everything. Now we’re facing another shift, one that’s redefining how society works and how we interact with technology. It’s likely to be even more disruptive, yet fascinating to witness.
There are valid ethical, environmental, and economic concerns, and the job market implications are real. These deserve to stay front and center in the discussion.
Still, I can’t ignore the positive side: the creative, practical, and transformative opportunities opening up before us.
Some changes are beyond our reach or influence, but others we can already use to build, automate, improve, and move faster.
Over the last few months, I’ve been exploring how AI tools like Vibe Coding and MCP servers can help with real Salesforce work. Here’s just a few examples of what that looks like in practice.
Fixing Bugs and Updating Metadata
A big part of my daily work is keeping Trailhead orgs and packages in top shape. Things evolve quickly, and we have to make sure everything is always ready for our Trailblazers. From Flows, to Agentforce Agents, to Apex and LWCs, to branding.
By using Agentforce with natural language prompts, I can accelerate development. I describe the issue, explain what I’m trying to achieve, give context, and ask for help.
It’s extremely important to note that AI still makes mistakes, of course. That’s where experience comes in. To enforce our standards, review the results, and ensure scalability and consistency. It feels like doing a code review with a fast, tireless teammate who probably had way too much coffee ☕️.
And you still want to take time to do it right, document it, and keep it clean so others can pick it up later.
Hands-on Challenge Feasibility
When my team works with Trailhead content owners, one of our main jobs is to figure out if something is “HOCable.” In other words, can we create a hands-on challenge that matches the learning objectives?
With new Salesforce features, that’s often tricky because we start before public documentation even exists. So we investigate, test, and reverse-engineer metadata to make sure we’re validating the right things and the things right.
Now imagine running that process with multiple agents working together. One agent could interpret writer instructions to parse challenge requirements. Another could extract metadata from an org, another could write code, a third could review it, and so on. All with shared findings, specific order of dependencies, and tasks orchestration.
That’s one of the tooling improvements I’ve created to help us with that, and what vibe coding allows. And it’s already saving my team a ton of time. These are real examples of what’s already happening today.
So, who is this for?
Vibe coding works for both developers and non-technical folks. For small tasks, it’s straightforward and safe enough.
For complex work, human judgment still matters. A lot. This expertise is what will keep your systems and your business sustainable.
Another important point: relying too much on AI can weaken your own skills. It is easy to let the machine take over, but that comes at a cost. You need to stay sharp, keep questioning and learning, and understand the reason behind every line of code. That is how you remain the trusted human in the loop, the one who catches mistakes, makes sound decisions, and ensures the work reflects real engineering thinking, not blind automation.
AI will keep evolving fast. Ignoring it means missing out on ways to boost your productivity and creativity as a developer. That’s strange to say, because I’ve always taken pride in writing the code myself, with precision and quality. But the landscape is changing. This is undeniable.
The key is balance. Stay critical, stay ethical, but stay curious. This technology is for those who understand that progress doesn’t erase craftsmanship. It amplifies it.