Vibe coding, agentic software development and rapid internal tooling. Equip operational and non-traditional engineering staff within Malaysian SMEs to design, build, secure, version-control and deploy custom multi-user internal web tools in under 48 hours using AI-native coding assistants, managed cloud databases, GitHub and automated deployment pipelines.
Outcome. A working, deployed internal tool with its source in a private GitHub repository.
2 days · physical · SBL-Khas · 14 training hours
Small steps, real builds. Everything in this school runs on your own laptop, so the laptop has to be ready before the first module starts. Twenty minutes this week saves you the first half hour of the session, which is otherwise spent watching your neighbour build while your installer downloads.
20 min · deliverable: text notesBefore you touch a tool, get the idea straight. The AI is not a magic box: treat it as a fast junior developer who needs a written brief, and you will know what to do when it goes wrong. This chapter gives you the method and the folder the rest of the evening runs on.
90 min · no deliverableTurn a vague idea into three specific files without writing them from scratch. The coach interviews; you answer, confirm, and edit. Ownership comes from the read-back and the one deliberate change.
90 min · deliverable: text notesThis is where the room lights up: first visible screen, first working feature. It is also where the discipline matters most: one card, one test, continue or fix. The trainer demos one full card cycle, then gets out of the way.
120 min · deliverable: text notesTwo habits: check the work against the spec before calling it done, and put it somewhere that is not a laptop. Git is taught as insurance and audit trail, not as a developer ritual. .gitignore comes before the first commit because M5 will introduce secrets.
60 min · deliverable: git repo urlMove the app off localStorage onto a real database without learning SQL. The coach generates the schema from a plain-English data model; you run it. Secrets are introduced here quietly (which key is public, which is not) so M7 has something to test.
120 min · deliverable: text notesLogin is the easy part. The point of the module is that the database enforces access, not the UI, and you prove it by signing in as a second person and failing to see the first person's data. That failure is the deliverable.
90 min · deliverable: text notesMake security concrete by doing the bad thing on purpose and catching it. The leak drill is the memorable part; PDPA is the part companies will ask about. The Review Mirror's extended checks make this measurable.
90 min · deliverable: text notesShip it, prove it, present it. Deployment is mechanical once env vars are understood; the presentation is where you realise what you built. Demo night is also the school's marketing for the next 101 and the HRD assessment moment.
90 min · deliverable: deployed app urlLock a seat on a session below to open the chapters. Each chapter opens once the checkpoint before it is cleared.