If someone has strong knowledge of a particular business field but no programming experience, could they learn enough in under a year to build dependable software for that field? The initial version would be a Windows CRUD application with a WinUI 3 frontend, a C# backend, an API for importing data from at least one external website, and SQLite for individual users. It would need substantial business logic, including client records, work papers, reproducible snapshots, reopening saved work, and exporting data to another endpoint. A later version might use PostgreSQL and support teams. The first goal would be personal use and reducing manual work, with the possibility of eventually turning it into a business. There is little or no budget for hiring collaborators, so I'm wondering how realistic the one-year timeline is, especially with AI tools available for guidance.
5 Answers
Six to twelve months can be enough to become comfortable with one language and build a small application if you put in serious, regular effort. It is unlikely to be enough to become an experienced engineer who can independently design, secure, deploy, and maintain complex business software. A sensible goal would be a limited personal-use tool with frequent backups and manual checks, not a dependable commercial system from day one.
The difficult part usually isn’t making the screens or getting a prototype running. It’s making sure the business rules are correct and handling edge cases. Once real users and sensitive data are involved, you also need security, permissions, backups, quality assurance, compliance, and a plan for updates. AI can help write and explain code, but it won’t take responsibility for whether the system is correct or legally safe.
Having domain expertise is a major advantage because you understand what the software should do. It doesn’t replace software engineering experience, though. Professional applications are normally built through collaboration between developers, testers, operations people, security specialists, and sometimes legal or compliance experts. With no budget, aim for a useful prototype first and expect the timeline to expand as you discover the hidden requirements.
The collaboration issue is the main concern since I can’t currently afford a team. I may need to treat the first year as learning and prototyping instead of promising a finished product.
You could probably learn the programming mechanics in a year, especially if you study and practice consistently. A basic CRUD application is achievable, but complex business rules, database design, API integration, authentication, testing, deployment, and long-term maintenance are separate skills. Building something that works for personal use is much more realistic than building a product that businesses can safely rely on.
For a private first version, narrow the scope aggressively. Pick one workflow, use SQLite, avoid multi-user features, and build a small vertical slice from data entry through processing and export. That could be a reasonable one-year learning project. Trying to cover the entire field from start to finish, support teams, connect to several websites, and make it production-ready is far beyond what most beginners can reliably complete alone in that timeframe.
That makes sense. I was mainly thinking about starting with a private tool for my own workflow, rather than launching a commercial platform immediately.