Work across systems, software, and aerospace.

• Recommends a refuelling strategy ahead of time from trend and live data, instead of operators working it out from scratch under time pressure
• Surfaces the recommendation alongside current conditions so operators can act on it or override it

Power Platform, with an AI-assisted forecasting model behind the recommendation. Currently a working pilot.

• Automated pipeline raises supply and demand requests without manual tracking
• Shifts the operator's job from managing logistics by hand to monitoring pipeline status

Power Platform, with a custom automated request pipeline behind it. Currently a working pilot.

• A defect walks Waiting for assessment → Pending CEN Endorsement → Pending for Approval → Approved → Repair in progress → Ready for collection → Collected, with ADDL (Acceptable Defect Deferred Log), ADDL Expired and Rejected as branch states, and every transition gated by role
• Moving a scheduled Preventive Maintenance date is not a free edit but an LOS — Latitude of Servicing — request that clears approval bands before the dashboard reflects it
• A defect formally deferred as an ADDL keeps the asset serviceable only until its expiry date, after which the asset flips itself to ADDL Expired
• Eleven built-in roles plus custom roles, resolved by a security-definer function server-side rather than trusted from the client
• Five Postgres realtime channels push changes to the dashboard, coalesced through a 150ms per-table debounce so a burst write does not thrash the UI

The functions were proved in Power Apps first, then rebuilt as a full-stack application once per-user licensing stopped being viable for a user base that reached beyond the RSAF.

• A trip walks pending_approval → approved → ongoing → completed, with rejected as a branch, and approvers can clear many at once rather than one at a time
• Four roles — admin, facilitator, approver, driver — with more than one assignable to a person, enforced at three layers: route guards, 136 row-level-security policies over 31 tables, and per-request auth inside every edge function
• Digital pre-use inspections, configurable per vehicle type and per model, whose outcome drives whether the vehicle reads as serviceable
• Fuel accounted end to end — bulk tanks to refueller payload holdings to POL top-ups to a summary report — with forklifts tracked by hour-meter and vehicles by odometer
• Ground support equipment booked in and out of the same register as the vehicles, and every action written to an audit trail with actor, entity and timestamp

The functions were proved in Power Apps first, then rebuilt as a full-stack application once per-user licensing stopped being viable for a user base that reached beyond the RSAF.

• Fill-in-the-blank, checklist-table and multiple-choice questions, graded case-insensitively against the authored answer
• Submit stays hidden until every question on a quiz is correct, with mastery enforced by the domain model rather than a UI check
• A cadence and rotation engine that derives Outstanding, Overdue, Upcoming and Completed status for every crew
• A readiness dashboard and status board, scoped by squadron or platform, showing who is current across all eight airframes

Delivered spec-first with OpenSpec change proposals, with the storage layer kept swappable behind the same call sites so Microsoft Dataverse can slot in without touching the app.

Reads a photographed goods receipt or invoice, in whatever format the issuing company used, extracts the fields the finance form and the downstream RPA flow need, and stores every record in one auditable repository.

• Whitelist-gated sign-in with a one-time email login code, so there are no passwords to manage
• Camera capture of the fuel receipt or invoice, with manual entry as the fallback when no OCR key is configured
• Separate aviation and vehicle fuel forms, each with its own searchable, exportable history
• A full audit log of every submit, edit, delete and role change, plus an admin panel for platforms, the email whitelist and users

• Role-based access control across four permission tiers
• Approval workflows with end-to-end visibility
• Real-time availability and conflict detection
• Recurring bookings for repeating schedules
• Audit logging on reservation records
• Soft-delete patterns and departmental isolation for multi-tenant use

Designed and implemented end-to-end with specs-driven development (frontend, API integration and data model) in two days, and demonstrated it to stakeholders in a dedicated session. Gemini 3.1, Claude Opus 4.6 and GitHub Copilot assisted the build; none of them runs in the shipped product.

Learned how to make use of FormSG and Plumber (Open Government Products) to safely store sensitive data and user contact details on the Internet considering policy constraints.

• Every weekday splits into an AM and a PM wave, with slot times and labels editable per day by an admin and copyable across days
• Each mission wants a QFI and a Psych assessor; an unfilled half is tracked as a broken pair rather than left silent
• Covering requests carry a reason and an optional suggested replacement, and move to History once decided
• Per-assessor duty counts drive a ranked workload chart, so over-tasking is visible before it is a problem; an admin can lock a published week against further changes

Using Lovable to create a quick prototype on the spot to gain user feedback, deploying to PowerApps safely. GitHub Copilot and Google AI Studio assisted the build; neither runs in the shipped app.

Rapid prototyping using simple no-code tools to create a functional system and deploy within a day.

• Geofencing for check in/out at designated locations
• Logistics accountability and tracking
• Noticeboards for centralised announcements
• Hand-over features facilitating smooth transitions

Significantly improved the efficiency and accuracy of attendance tracking for duty personnel.

Every Code Apps project in this portfolio was built after this approval. Before it, Code Apps could not be deployed in the environment at all.

The syllabus covered prompt-driven development, rapid prototyping and Power Apps deployment.

Staff from Nanyang Polytechnic attended alongside RSAF personnel. Internally the masterclass was recognised in PPCoE updates, and attendance held across the cohort.

Designed a systematic workflow that reduced development time from months to days for Digital Champions and RAiD developers.

A citizen developer finishes an internal app and then has to convince people to use it. That second job needs screenshots, a page and a post: skills the build didn't require, and time the builder doesn't have.

• Clones the target repo read-only into a temporary directory and never writes back to it
• Runs a threat scan before anything executes; the app is only booted, with mock data, after it passes
• Captures the app's actual screens, and falls back to static reconstructions when Node or a headless browser isn't available, rather than failing
• Emits a marketing spec, a zero-dependency HTML landing page, 16:9 and 9:16 SVG infographics, a Remotion video composition, and LinkedIn copy

Writing a skill someone else installs is a different discipline from writing one for yourself: it has to refuse to damage a stranger's repository, and it has to degrade instead of crash when their machine is missing a tool.

Left alone, a coding assistant is agreeable and eager: it starts editing on the first message and adds things nobody asked for. For someone who can read the output but not yet audit it line by line, that is the failure mode that costs the most time.

• Holds an approval gate: no change to code, files, data model, dependencies or structure until a complete implementation plan has been shown and accepted
• Requires two or three distinct approaches on anything substantial, conventional and unconventional, before one is chosen
• Bans unrequested features, pages, integrations and redesigns mid-implementation
• Instructs the assistant to stop the moment an assumption turns out to be false, and to be direct rather than agreeable

The useful part of a system prompt is the refusals, not the encouragement.

Learned about cybersecurity scanning architecture, policy constraints, and how to collaborate with departments to clear tools for citizen developers.

RSAF engineers learning to look after the people on their own team: practice at a conversation that is hard to rehearse without a real subordinate in front of you.

The agent plays the teammate: a shy one, with something on their mind they are afraid to raise with their boss. The engineer role-plays the conversation and finds out what their questions actually surface. It runs on open-source models inside Copilot, for training use.

Navigated license constraints creatively to replicate GPT-4.1 concepts, managing context engineering to prevent hallucinations.

Me, for my own coursework. I was drawing assignment flowcharts by hand from written descriptions, and wanted to describe one and get it back as a graph. The interesting part turned out to be teaching the model to hold its output to the exact code format the Flowgiston Python library would accept.

Explored prompt engineering and integrating Python libraries together in a single notebook for workflow tools.

Certificate of Participation from AI Singapore.

Exposure to ML algorithms, various cloud technologies in Huawei's ecosystem, and MLOps. Introduced to the AI development field.

Introduced to various cybersecurity practices transitioning from an engineering background.

Learned riveting, soldering, and composite materials. Instilled resilience, self-discipline, and the ability to handle stress.