top of page
Cavalry logo cream
Cavalry logo cream
Cavalry logo cream

How AI actually helped me build a better calendar widget

  • Writer: Barney Braithwaite
    Barney Braithwaite
  • May 26
  • 3 min read
Colourful coding on a screen

I built a custom JavaScript availability calendar for a client last week. Google Sheets backend, live updates, mobile-responsive, the works. The kind of thing that would have been completely impossible for me to build five years ago.


Because I'm not a coder. Never have been.


The bit that actually matters

I can't write JavaScript from scratch. I understand enough to know what's possible and what problems need solving. But sitting down and coding a date-parsing function that handles UK versus US date formats? No chance.


That's where AI comes in. And it's not making me faster at something I could already do. It's enabling me to build things I couldn't build at all.


The calendar needed to read booking data from a Google Sheet and display it on their holiday rental website. Simple concept. Fiddly execution involving API calls, date handling, responsive CSS, and edge cases I wouldn't have known about (not a Scooby), yet alone thought about.


I explained what needed to happen. AI wrote the code. I tested it, spotted problems, described what wasn't working, and AI fixed them. Back and forth until everything worked properly.


Not because I'm secretly a developer who's too lazy to code. Because I genuinely don't have the technical knowledge to write that code myself. AI fills the gap between what I can design and what I can execute.


What this actually means for non-technical people

If you're a designer, strategist or small business owner who needs technical solutions but doesn't code, AI changes everything.


I can now have conversations with clients about custom functionality without immediately thinking "I'll need to hire a developer for that." I can sketch out what needs to happen, work with AI to build it, and deliver solutions that would have required outsourcing before.


That doesn't mean I'm pretending to be a developer. I still can't write production-grade applications or complex backend systems. But I can solve specific technical problems for clients who need custom widgets, interactive elements, or data integrations.


The calendar widget is a perfect example. Client had a real problem: updating availability meant uploading static images to their Weebly site every time someone booked. Manual, time-consuming, easy to forget.


They needed automation. Something that updated itself when they added rows to a spreadsheet. I couldn't have built that solution five years ago. Now I can. Not because I learned JavaScript, but because AI can translate what I need into working code.


The bit nobody mentions

You still need to know what you're trying to achieve. You need to understand the problem well enough to explain it clearly. You need to test the solution and spot when something isn't working right. You need to know enough about web design to understand what's technically possible.


AI can't figure out what your client needs. It can't have the discovery conversation that uncovers the real problem. It can't make strategic decisions about whether a feature should exist at all.


What it can do is bridge the gap between design thinking and technical execution. It lets non-developers build custom solutions instead of settling for generic templates or paying specialists for every small technical requirement.


That's genuinely revolutionary. Not because it replaces developers. Because it extends what designers and strategists can deliver on their own.


The calendar works. The client can update it in seconds. That's what matters.


Need a website with custom functionality but don't have a development team? Get in touch - I'd love to hear what you're working on.



Cavalry bugler icon

 
 
 

Comments


bottom of page