Author | Lightnews

Jeremy Vyska | #MSDYN365BC MVP

@bc.jeremy.vyska.info

950 followers 120 following 190 posts

🇸🇪/🇺🇸 in Gothenburg Sweden. #MSDYN365BC MVP. He/him. Autistic/ADHD. Dad-joker. Problem solver. Lgbtqia+ Supporter. This is my business world profile and I'll mostly be engaging in work topics here.

Posts Media Videos Starter Packs

Pinned

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 22

🚀 After building BC extensions and seeing the same development challenges repeatedly, I'm excited to share our approach to comprehensive BC development intelligence.

🧵

1 2 7

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · 6d

Pretty low feedback so far, will likely push it through today and then when it's live, people will probably have all sorts of opinions 😉

Reposted by Jeremy Vyska | #MSDYN365BC MVP

Natalie Karolak - 𝑩𝑪 𝑫𝒐𝒄𝒔 𝑳𝒊𝒃𝒓𝒂𝒓𝒊𝒂𝒏 @nataliekarolak.bsky.social · 20d

Docs, AL Language changelog, BCLE videos, and what not ... so much to learn about what's new in BC 27 for developers!

But don't worry - I've combined it all-in-one in my new blog:

𝗗𝗼𝗰𝘀: 𝗪𝗵𝗮𝘁’𝘀 𝗻𝗲𝘄 𝗶𝗻 𝗕𝗖 𝟮𝟳 𝗳𝗼𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀
nataliekarolak.wordpress.com/2025/10/02/d...

Docs: What’s new in BC 27 for developers

Summary of all technical changes in Business Central 2025 release wave 2 (BC 27 / runtime 16.0) mentioned in the docs and beyond.

nataliekarolak.wordpress.com

2 9 15

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · 26d

With the tech changing every week, one thing stays the same.

I hate waiting on progress bars.

@bctechdays.com

A BC TechDays 2024 mug of tea stands next to a hand drawn progress bar slooooowly filling from BC TechDays 2025 to 2026

1 8

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 22

I'm most excited about the opportunity for all of us to test this together and refine it based on real BC development scenarios. There's a lot we can learn from community feedback.

What BC development challenges would benefit from this kind of systematic guidance? I'd love to hear your thoughts.

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 22

• Layer system for company/team customization
• One-click VS Code integration through MCP

🎯 Ready to help test it? Find out more here:
nubimancy.com/2025/09/22/...

🧵

1 1

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 22

✨ What we've included so far:
• 100+ BC knowledge topics from ALGuidelines and community best practices
• 14 AI specialists for different BC development areas (architecture, performance, security, etc.)
• Structured methodologies for common workflows (optimization, testing, integration)
🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 22

After 30 days of AI-accelerated development, we've built BC Code Intelligence - a system that brings BC domain expertise directly into VS Code. This works well for our development patterns, though there's definitely room for community testing and improvement.

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 22

🚀 After building BC extensions and seeing the same development challenges repeatedly, I'm excited to share our approach to comprehensive BC development intelligence.

🧵

1 2 7

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 10

Yep. Link to group in description. 5 min overview vid for "New to Discord"
youtu.be/oUfTr55pOls?...

"BC Professionals" - Discord Basics for the Microsoft Dynamics 365 Business Central Community

YouTube video by Spare Brained Ideas

youtu.be

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 9

I'm curious about your experiences: Have you seen patterns where generic AI guidance actually made things worse? What's worked best in your domain?

I've even added instructions about how you could play with it to test different models - tell me what you find!

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 9

I've open-sourced the complete testing framework because I'd rather see more people succeed with AI knowledge engineering than keep this approach to myself.

Full methodology and results: nubimancy.com/2025/09/09/...

🧵

1 2

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 9

The results surprised me. Generic programming knowledge actually _hurt_ performance - we're talking a 4% regression. But when I got the knowledge engineering right? One module went from 64 seconds to 81 milliseconds. That's 746x faster.

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 9

Like many of you working with AI tools, I keep hearing about "feeding knowledge to AI," but I hadn't seen systematic testing of whether it works - and more importantly, which approaches work better than others. So I built a controlled experiment with five different knowledge engineering tiers.

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Sep 9

I just finished an intense week of testing something I've been curious about: whether different approaches to "knowledge engineering" actually improve GitHub Copilot's effectiveness with Business Central development.

🧵

1 3

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

This wraps up my 3-part AI transformation series - from skepticism to organizational enthusiasm.

The approach is replicable, but infrastructure and governance matter more than the AI itself.

Full post: nubimancy.com/2025/08/26/...

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

If you're working on AI adoption in your org, curious about your experience:

Have you hit the "individual success but team adoption struggles" wall?

What's worked for making AI accessible to everyone, not just the early adopters?

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

The formula that emerged:

Without all three elements = individual productivity improvements at best

With all three elements = teams actively requesting AI integration on every project

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

The most surprising part? Once we had all three elements working together, team transformation happened in about one week.

Despite technical hiccups (VS Code versions, MCP setup), they went from "can we make this work?" to "can we roll this everywhere?"

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

Business Governance solved the "AI enthusiasm vs business reality" problem.

AI agents would jump into implementation even when requirements had obvious gaps needing stakeholder input. Quality Gates force pause points for business validation.

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

Knowledge Architecture was the game-changer though. We created ".aidocs" folders - documentation designed specifically for AI consumption, not humans.

AI agents need context about WHY decisions are made, not just WHAT to implement.

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

Technical Infrastructure meant zero-friction access. If team members need to become AI experts or configure complex environments, adoption stalls at early adopters.

We built a "Bootstrap" system - one VS Code task activates AI guidance in any repository.

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

The breakthrough came when I stopped thinking about AI adoption and started thinking about AI infrastructure.

Three specific elements made the difference:

Technical Infrastructure + Knowledge Architecture + Business Governance

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

Here's what I discovered: Individual AI mastery and organizational AI transformation are completely different challenges.

You can be great at using AI personally and still completely fail at scaling those benefits to your team.

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

This is Part 3 of my AI transformation series - and the gap between individual AI success and team transformation? Way more complex than I expected.

🧵

Jeremy Vyska | #MSDYN365BC MVP @bc.jeremy.vyska.info · Aug 26

Three months ago I was sitting in conferences wondering "why does everyone think AI is transforming business when it's basically fancy autocomplete for me?"

Today my team actively wants our AI infrastructure rolled out to every project.

🧵

1 1