Introducing BC Prompt Kit: How I Started My AI Journey
How I Started My AI Journey
Like many developers, I was skeptical about AI coding tools.
“Why do I need AI?”
I didn’t trust the output.
I felt slower when I tried them.
I worried I would spend more time fixing AI results than writing code myself.
That changed a few months ago when I decided to play around with it.
I began to study prompts.
I looked at MCP servers.
I started experimenting with small tasks.
Create this, add that, rename this, renumber that.
Those small tasks turned out to work very well.
The small steps helped me.
They built my confidence.
Slowly but surely.
I started playing around a bit more.
Asking AI to explain code.
Asking AI to generate documentation.
Asking AI to check logic.
Over time, my habits changed. Now I use AI almost daily.
To generate code.
To test ideas.
To validate patterns.
To review code.
It’s not magical.
It’s not perfect.
It still takes time and effort.
But I realised something.
AI isn’t magical or perfect, but it genuinely helps with the tedious parts of development.
It allows me to focus on solving more challenging problems.
Introducing BC Prompt Kit
I spent weeks figuring out how to use AI.
To save you some time, I created the BC Prompt Kit.
A simple collection of prompts that everyone can use to start their AI journey with Business Central and AL development.
I’m not an expert, but I’m sharing what I learned so you can start your AI journey without the frustration I experienced.
If it helps you get started with AI, then it’s worth sharing.
What’s in the Kit?
Just a collection of prompts that have worked for me, organised into four categories:
- Base Development
The everyday stuff: creating tables, pages, codeunits, APIs. These are the prompts I use most often when building features. - Analyse Features
For when you inherit someone else’s code and need to figure out what it does. (We’ve all been there.) - Documentation
Because writing documentation is nobody’s favorite task, but AI actually makes it bearable. - Refactoring
Cleaning up messy code, removing duplication, fixing things you’ve been meaning to fix. AI is surprisingly good at this.
Want to Try It?
Head over to BC Prompt Kit.
If you’re new to AI, I included a Getting Started Guide that covers the basics.
Start with one prompt.
Use it on a small task.
Check the output.
Adjust the prompt to fit your workflow.
Repeat.
You’ll get faster after a few days.
Worst case? It doesn’t work for you and you’ve lost a few hours.
Best case? You find a new way to work that actually helps.
Things I’ve Learned
- AI isn’t perfect, but it’s helpful when you learn how to use it.
- Good prompts and MCP servers make all the difference.
- You still need to review everything. AI assists, you decide.
- You own the code, even if AI generates it. Take full responsibility before releasing to production
- Starting is the hardest part. Once you get going, it clicks.
- Being skeptical is fine, but give it a real try before dismissing it.
Final Thought
I went from thinking AI was overhyped to using it daily.
Not because I’m sold on the hype, but because it makes parts of my job easier.
If you’re skeptical like I was, I get it.
But maybe it’s time to give it a shot?
