{"id":9031,"date":"2025-05-28T12:00:00","date_gmt":"2025-05-28T11:00:00","guid":{"rendered":"https:\/\/www.markwilson.co.uk\/blog\/?p=9031"},"modified":"2025-05-28T20:09:50","modified_gmt":"2025-05-28T19:09:50","slug":"does-vibe-coding-have-a-place-in-the-world-of-professional-development","status":"publish","type":"post","link":"https:\/\/www.markwilson.co.uk\/blog\/2025\/05\/does-vibe-coding-have-a-place-in-the-world-of-professional-development.htm","title":{"rendered":"Does vibe coding have a place in the world of professional development?"},"content":{"rendered":"\n

I\u2019ve been experimenting with generative AI lately \u2013 both in my day job and on personal projects \u2013 and I thought it was time to jot down some reflections. Not a deep think piece, just a few observations about how tools like Copilot and ChatGPT are starting to shape the way I work.<\/p>\n\n\n\n

In my professional life, I\u2019ve used AI to draft meeting agendas, prepare documents, sketch out presentation outlines, and summarise lengthy reports. It\u2019s a co-pilot in the truest sense \u2013 it doesn\u2019t replace me, but it often gives me a head start. That said, the results are hit and miss, and I never post anything AI-generated without editing. Sometimes the AI gives me inspiration. Other times, it gives me American spelling and questionable grammar.<\/p>\n\n\n\n

But outside work is where things got interesting.<\/p>\n\n\n\n

I accidentally vibe coded<\/h2>\n\n\n\n

It turns out there\u2019s a name for what I\u2019ve been doing in my spare time: vibe coding<\/em>.<\/p>\n\n\n\n

First up, I wanted to connect a microcontroller to an OLED display and to control the display with a web form and a REST API. I didn\u2019t know exactly how to do it, but I had a vague idea. I asked ChatGPT. It gave me code, wiring instructions, and step-by-step guidance to flash the firmware. It didn\u2019t work out of the box \u2013 but with a few nudges to fix a compilation error and rework the wiring, I got it going.<\/p>\n\n\n\n

Then, I wanted to create a single-page website to showcase a custom GPT I\u2019d built. Again, ChatGPT gave me the starter template. I published it to Azure Static Web Apps, with GitHub for source control and a CI\/CD pipeline. All of it AI-assisted.<\/p>\n\n\n\n

Both projects were up and running quickly \u2013 but finishing them took a lot more effort. You can get 80% of the way with vibes, but the last 20% still needs graft, knowledge, or at the very least, stubborn persistence. And the 80% is the quick part – the 20% takes the time.<\/p>\n\n\n\n

What is vibe coding?<\/h2>\n\n\n\n

In short: it\u2019s when you code without fully knowing what you\u2019re doing. You rely on generative AI tools to generate snippets, help debug errors, or explain unfamiliar concepts. You follow the vibe, not the manual.<\/p>\n\n\n\n

And while that might sound irresponsible, it\u2019s increasingly common \u2013 especially as generative AI becomes more capable. If you’re solving a one-off problem or building a quick prototype, it can be a great approach.<\/p>\n\n\n\n

I should add some context: I do have a Computer Studies degree, and I can<\/em> code. But aside from batch scripts and a bit of PowerShell, I haven\u2019t written anything professionally since my 1992\/93 internship \u2013 and that was in COBOL.<\/p>\n\n\n\n

So, yes, I have some idea of what\u2019s going on. But I\u2019m still firmly in vibe territory when it comes to ESP32 firmware or HTML\/CSS layout.<\/p>\n\n\n\n

The good, the bad, and the undocumented<\/h2>\n\n\n\n

Vibe coding has clear advantages:<\/p>\n\n\n\n