Practical path · LEGION.TW
You are allowed to build software nobody else needs.
This is the path for someone who has never written code and is tired of copying the same appointment into three places. You install VS Code and Codex, build a real native Windows app early, then learn by using it: GitHub, a brief that describes your actual week, a second person sharing the records, and what to do the day it breaks.
Written by Buddy Lien.
The articles
Read them in order. Each one assumes the decisions made in the last.
- 01You Can Have Software Nobody Else NeedsYou do not need a market, a business plan, or users to justify building a tool. The calling work behind the Visit Book example, and why the job is more interesting than the app.6 min read
- 02What You Need Before You StartInstall VS Code, pick the Codex desktop app or the CLI, and have Codex build Visit Book as a real native Windows app with Tauri — opened from a shortcut, saving records on your own computer.9 min read
- 03GitHub for People Who Have Never Written CodeUnderstand Git and GitHub, find the changes Codex saved, and distinguish the project's source history from a backup of your business records.5 min read
- 04Describe the Life You Want the Software to FitA careful account of one phone call is worth more than a page of borrowed technical language. How to describe your real working day so Visit Book fits it instead of resembling every other dashboard.6 min read
- 05The Little Bit of Systems Engineering You Actually NeedOne saved appointment feeding the business page, the calendar, and Friday's visit list. Enough systems reasoning to ask why an app still makes you type the same change twice.6 min read
- 06Don't Let AI Shrink Your Ambition“Let's start with a simple MVP” can be discipline or a conveniently small interpretation of your request. The article Buddy rewrote after Frank pointed out that a beginner's first app could be a real native one.6 min read
- 07Add Something Real: A Second PersonExtend Visit Book to a colleague calling from another Windows computer in another home: the same business details, the latest conversations, and nobody phoning the same place twice.7 min read
- 08When It Breaks, You Still Own ItThe AI says it fixed the problem and the problem is still there. How to report failure precisely, recover a working version of Visit Book, and stay the owner of it.7 min read
Who this is for
People with a stubborn, unglamorous problem and no programming background. No market, no business plan, and no permission required.
About the example
The articles use a fictional appointment tool called Visit Book — calls, callbacks, changed visits, and then a second caller in another home. You build your own version; Visit Book is not hosted here.
Read the course →