AI

ACE AI SW Startup Training

Development (Completing Features with AI)

Day 7 Development (Completing Features with AI) Videos + AI chatbot learning

Development (Completing Features with AI) Learning Helper

A service doesn't work just because the screens exist. When a user presses a button, data must be saved, read and updated. In this session especially, you use Codex Client Workspace to map events to static markup (Task 01), check and fix broken user paths like lost filters using session storage (Task 02), and check features to block rapid repeated clicks and date boundary errors (Task 03), putting together a fully working service.

For: students who finished the screen skeleton design
Bring: laptop, VS Code, web browser
Format: 2h theory / 3h lab / 1h sharing
πŸ“– Go to Session 7 guide

πŸš€ Day 7 Lab MVP Tasks Roadmap

Go to full Task board β†’
TASK 1
Integration

Task 1. Connect Features

Stop the sign-up form's default submit, save to local storage and switch screens.

Enter Task 1 lab
TASK 2
Scenario

Task 2. Check User Scenarios

Set a temporary session backup guard so filters don't reset when returning to the search list.

Enter Task 2 lab
TASK 3
Validation

Task 3. Find Feature Errors

Block duplicate data from rapid clicks and invalid input like booking a time in the past.

Enter Task 3 lab
MISSION 1
Review

Mission 1. Check Service Completeness with AI

Get an overall quality diagnosis covering missing loading feedback (Spinner) and storage exception handling.

Enter Mission 1 lab
MISSION 2
E2E Scenario

Mission 2. Use It from Start to Finish

Apply flow feedback from a beginner persona and prove an E2E scenario that can be completed.

Enter Mission 2 lab

Day 7 Lecture Videos

Recommended YouTube lectures
A list of recommended YouTube lectures on the key Day 7 topics (MVC, layered architecture, Express.js, CRUD APIs, DB integration). (All are free lecture videos that allow embedding and playback.)
πŸ“š All lectures (5)
  • β–Ά
    1. WEB3 - Express - 1. Course intro (Opentutorials)
    5:12
  • β–Ά
    2. WEB3 - Express - 5.1. Detail page 1 - Route Parameter (Opentutorials)
    6:45
  • β–Ά
    3. WEB3 - Express - 6. Creating pages (Opentutorials)
    8:30
  • β–Ά
    4. WEB3 - Express - 7. Updating pages (Opentutorials)
    7:15
  • β–Ά
    5. WEB3 - Express - 8. Deleting pages (Opentutorials)
    6:20

Key Summary Notes

Day 7 Summary

Today's key goals

On Day 7 you learn how APIs called from the front end are handled on the server, and build real CRUD APIs with Express.js using MVC and a 4-layer structure.

  • Express.js project setup: server environment and routing for RESTful APIs
  • Layered architecture design: separate Route -> Controller -> Service -> Repository
  • Database CRUD: write data CRUD logic with an ORM or raw SQL
  • RESTful API endpoints: finish REST APIs that follow URI design guidelines
  • Exception handling and middleware: set up business errors and a global error handler
Learning tip: ask the AI chatbot on the right questions like "How do I split roles between Controller and Service in a layered architecture?" or "How do I set up global error handler middleware in Express.js?"