I've been asking myself an interesting question lately.
Am I building a system for developing software, or could it eventually become a system for developing almost anything?
A few months ago, I started building MAGDC (MAG Development Center).
The idea was to solve problems I kept running into while developing software with AI: forgotten decisions, unexpected changes, broken functionality, and agents doing more than I actually asked.
MAGDC doesn't write the code itself. It helps me organize requirements, decisions, architecture, tasks, and verification while AI tools such as Cursor handle implementation.
My main testing ground has been XenForo add-on development.
But I wanted to see whether the same approach would work somewhere else.
My first experiment beyond XenForo
I'm currently finishing MAG Business CRM, built with Google Sheets and Google Apps Script for managing 3D printing orders.
It handles things like customers, materials, pricing, production orders, payments, and financial calculations.
What makes this interesting to me isn't simply that AI helped build a CRM.
It's how we developed it.
I defined the business requirements, made the important decisions, and used MAGDC to organize the work into manageable steps. Cursor implemented the changes and ran technical checks.
And we learned something important along the way.
Passing tests doesn't necessarily mean the product is good to use.
For example, an order management screen passed technical checks, but when I tried using it, the selected order's details appeared below a long list. With just twenty orders, that was already inconvenient.
So we changed the interface based on actual usage.
Other seemingly small requests, such as giving orders readable numbers or preserving financial history, turned out to require much more careful architectural decisions.
The CRM has substantial implemented and tested functionality, although its final end-to-end validation and practical acceptance are still ahead.
It's not proof that MAGDC works everywhere. But it is useful experience outside its original XenForo environment.
What's next?
I've also worked on a Windows utility connecting ChatGPT and Cursor.
Now I'm considering something very different: developing a civilian racing drone.
I want to explore whether MAGDC could help organize not just programming, but also CAD models, engineering requirements, prototypes, documentation, and physical testing.
The MAGDC repository already has a planned embedded/FPV domain, but that doesn't mean the engineering workflow has been proven.
And that's exactly what I want to discover.
Maybe MAGDC's approach will transfer well.
Maybe I'll find that some of its rules only make sense for software.
Either result would teach me something.
I'm increasingly interested in building a system where one person can coordinate complex projects with AI assistance — while keeping the important decisions under human control.
Can an AI development workflow designed for software eventually help create physical products too?
I don't know yet. But I intend to test it.
Top comments (0)