James Chang · Work

Portfolio · 2025 – 2026

Six systems I built myself

I do not write code, but I use AI as my engineering team — requirements, data, rules, release — one system at a time. From building an Access system myself in 2015 to AI-built web tools in 2025, each entry states why it exists, how it was built, and what changed afterwards.

01

Access management system

2015–2022 · built in-house

Why
The company did have an IT department, but an earlier IT misstep — plus cost and confidentiality concerns — made me unwilling to hand over the critical checkpoints. So I carved them out: not outsourced, not given to internal IT, built in Excel and Access. It worked well; the cost was a bulkier, less tidy process.
How
Built tables, forms, queries and reports in Access, putting inventory, manufacturing orders and R&D data into one database, with permissions, backups and versions maintained by me.
Result
Critical data stayed in my hands, and daily lookups and monthly reports no longer meant stitching sheets. The limits were explicit too — single machine, difficult collaboration, manual sync.
Role
Requirements, data model, forms and reports; self-taught throughout
  • Inventory
  • Manufacturing
  • Database design
interface illustration

02

Access learning site

2022–2025 · internal use

Why
ChatGPT from 2022 accelerated my learning, but the concepts I had once learned and then confused needed somewhere to be reviewed.
How
Collected common syntax, the object model, examples and the mistakes I had made into an internal site, added to as I learned.
Result
Scattered notes became searchable material — and the base for moving workflows online later.
Role
Content curation and site building; AI-assisted coding
  • Internal material
  • Knowledge curation
  • Access VBA
interface illustration

03

ERP modernisation

2025–2026 · personal project · in progress

Why
A long-running Access inventory system opened on one machine only; data kept growing and backup or handover was painful.
How
First inventoried every table and field, defined field mapping and import rules, then rebuilt it as a web system on SQLite and Django — released in stages with old data kept for comparison.
Result
Queryable, backup-able data and concurrent use. I defined the specification and acceptance checklist; AI implemented it and I fixed errors round after round.
Role
Requirements, data rules, acceptance; no coding
  • Data migration
  • Field mapping
  • Acceptance spec
interface illustration

04

Web barcode scanning

2025 · personal project

Why
Stock takes relied on pen and paper plus one shared USB scanner; change the person or the device and work stalled.
How
Scanning through the browser camera, on desktop, tablet or phone; scanned codes go straight into the list.
Result
Anyone can count stock with their own phone, with nothing to install.
Role
Process design, interface trade-offs; AI-assisted coding
  • Shop-floor process
  • Scanning
  • Cross-device
Interface illustration

05

Bluetooth label printing

2025 · personal project

Why
Every new label printer meant reinstalling drivers and vendor software; urgent printing stalled.
How
The browser connects to the Bluetooth printer directly, with layout editing, preview and printing; common formats are saved as templates.
Result
No software to install; a new printer works straight away and onboarding got shorter.
Role
Layout rules, real-world process; AI-assisted coding
  • Bluetooth
  • Label layout
  • Retail operations
Interface illustration

06

Learning platform

2025 · personal project

Why
Course material, notes and downloads were scattered across folders and unfindable when needed.
How
Built a download, index and search workflow that turns scattered files into a queryable knowledge base.
Result
A tool I use daily; anything is a few seconds away, and it underpins my own continuous learning.
Role
Data structure and process design; AI-assisted coding
  • Knowledge management
  • Data curation
Interface illustration