Files
cv/spec.md
T

2225 lines
31 KiB
Markdown
Raw Normal View History

2026-10-06 09:58:00 +07:00
# Personal Engineering Portfolio — Specification
> **Document:** `spec.md`
> **Version:** 1.0.0
> **Status:** Draft
> **Language:** Vietnamese / English-ready
> **Application:** Personal Engineering Portfolio
> **Frontend:** React + TypeScript + Vite
---
# 1. Product Vision
## 1.1. Vision
Xây dựng một **personal engineering portfolio** thể hiện tôi không chỉ là một Software Engineer viết code, mà là một kỹ sư có khả năng:
* Hiểu business problem.
* Thiết kế solution.
* Xây dựng hệ thống production.
* Làm việc với distributed systems.
* Làm việc với logistics technology.
* Ứng dụng AI/ML vào bài toán thực tế.
* Tối ưu hệ thống dựa trên data.
* Làm việc xuyên suốt từ technical implementation đến product impact.
Portfolio phải thể hiện được progression:
```text
Software Engineer
↓
Senior Software Engineer
↓
System / Solution Thinker
↓
Technology + Product Mindset
↓
AI + Intelligent Logistics
```
---
# 2. Personal Positioning
## 2.1. Primary Positioning
**Senior Software Engineer**
## 2.2. Engineering Focus
Các lĩnh vực chính:
* Software Engineering
* Backend Engineering
* Distributed Systems
* Logistics Technology
* System Integration
* AI / Machine Learning
* Computer Vision
* System Architecture
* Performance Optimization
* Developer Productivity
## 2.3. Personal Engineering Statement
Portfolio phải truyền tải tinh thần:
> Building reliable software systems that solve real-world operational problems.
Phiên bản có thể sử dụng cho Hero:
> Senior Software Engineer building scalable software, intelligent logistics systems, and practical AI solutions.
---
# 3. Portfolio Goals
## Primary Goals
1. Xây dựng professional identity.
2. Thể hiện engineering capability.
3. Showcase các project có impact.
4. Thể hiện khả năng system design.
5. Thể hiện kinh nghiệm áp dụng AI/ML vào business problem.
6. Tạo điểm đến cho recruiter, engineer và technical stakeholders.
7. Có thể sử dụng như landing page khi networking / job application.
## Secondary Goals
* Chia sẻ technical knowledge.
* Lưu trữ engineering projects.
* Document technical experiments.
* Xây dựng personal brand lâu dài.
---
# 4. Target Audience
## 4.1. Recruiter
Cần hiểu trong vòng 30–60 giây:
* Tôi là ai.
* Seniority.
* Core expertise.
* Kinh nghiệm.
* Các project nổi bật.
* Cách liên hệ.
## 4.2. Engineering Manager / Tech Lead
Quan tâm:
* System design.
* Technical depth.
* Problem solving.
* Architecture.
* Engineering impact.
* Ownership.
## 4.3. Software Engineer
Quan tâm:
* Technical projects.
* Architecture.
* AI/ML experiments.
* Engineering articles.
* GitHub.
## 4.4. Product / Business Stakeholder
Quan tâm:
* Problem.
* Solution.
* Business impact.
* Operational impact.
---
# 5. Core Narrative
Portfolio không nên trình bày đơn thuần:
```text
I know Java.
I know Go.
I know React.
I know Docker.
```
Mà phải trình bày:
```text
Problem
↓
Understanding
↓
Solution
↓
Engineering
↓
Measurement
↓
Impact
```
Mỗi project quan trọng phải trả lời được:
1. Vấn đề là gì?
2. Tại sao vấn đề quan trọng?
3. Tôi đã làm gì?
4. Architecture như thế nào?
5. Technical challenge là gì?
6. Tôi đã đưa ra quyết định gì?
7. Kết quả là gì?
8. Tôi học được gì?
---
# 6. Website Information Architecture
```text
/
├── Home
├── About
├── Experience
├── Projects
│ ├── IoT-DWS Integration
│ ├── AWB Detection / Computer Vision
│ ├── Facility Management Platform
│ └── Other Projects
├── Engineering
│ ├── Architecture
│ ├── AI / ML
│ └── Experiments
├── Blog
├── Resume
└── Contact
```
Navigation chính:
```text
Home
About
Experience
Projects
Engineering
Blog
Contact
```
---
# 7. Homepage
Homepage phải kể được câu chuyện nghề nghiệp trong một flow liên tục:
```text
Identity
↓
Expertise
↓
Impact
↓
Selected Projects
↓
Engineering Interests
↓
Experience
↓
Contact
```
---
# 8. Hero Section
## 8.1. Content
Hero bao gồm:
```text
[Name]
Senior Software Engineer
Building scalable software systems,
intelligent logistics solutions,
and practical AI applications.
[View Projects]
[Contact Me]
GitHub
LinkedIn
Email
```
## 8.2. Visual
Hero không nên sử dụng stock photo.
Ưu tiên:
* Minimal engineering visual.
* Abstract system diagram.
* Code / architecture inspired graphic.
* Data-flow visual.
* Subtle animated nodes / connections.
Visual phải hỗ trợ engineering identity, không biến website thành landing page marketing.
---
# 9. Engineering Philosophy
Một section ngắn sau Hero.
Title:
```text
How I Think About Engineering
```
Nội dung xoay quanh:
### Build for the real problem
Không bắt đầu bằng technology.
Bắt đầu bằng:
```text
What problem are we solving?
Who has this problem?
How do we measure success?
```
### Think in systems
Quan tâm:
* Architecture.
* Integration.
* Scalability.
* Reliability.
* Observability.
* Maintainability.
### Measure impact
Technical implementation phải gắn với:
```text
Performance
Reliability
Cost
Operational efficiency
Business impact
```
### Keep learning
Thể hiện các technical explorations:
* AI / ML.
* Computer Vision.
* LLM.
* Distributed systems.
* Performance engineering.
---
# 10. About Section
## Title
```text
About Me
```
## Nội dung
Giới thiệu ngắn về bản thân với trọng tâm:
* Senior Software Engineer.
* Software architecture.
* Logistics technology.
* System integration.
* AI/ML.
* Continuous learning.
Không viết biography quá dài.
## Suggested structure
```text
Who I am
What I work on
What I enjoy solving
What I am currently exploring
```
---
# 11. Core Expertise
Hiển thị thành 5–6 nhóm.
## Software Engineering
* Java
* Go
* TypeScript
* Distributed Systems
* REST APIs
* Microservices
## System Architecture
* System Design
* Integration Architecture
* Event-driven Architecture
* Message Queues
* API Design
## Logistics Technology
* Sortation
* Warehouse / Facility Operations
* Package Flow
* Operational Intelligence
* Facility Modeling
## AI / ML
* Computer Vision
* Object Detection
* OCR
* Model Deployment
* LLM
* AI-assisted Engineering
## Infrastructure
* Docker
* Linux
* CI/CD
* Networking
* Middleware
## Engineering Practices
* Agile / Scrum
* Technical Documentation
* System Maintenance
* Performance Optimization
* Technical Research
---
# 12. Experience
## Experience #1 — Senior Software Engineer
### Responsibilities
Không chỉ liệt kê responsibilities.
Tập trung vào:
* System ownership.
* Architecture.
* Technical implementation.
* Integration.
* Production operation.
* Technical problem solving.
---
# 13. Highlighted Achievement — IoT-DWS Integration
## Context
Tiếp nhận và nhanh chóng làm chủ một hệ thống IoT-DWS sau khi thành viên phụ trách trước đó rời project.
## Challenge
Cần hiểu nhanh architecture hiện tại và tiếp tục phát triển integration solution.
## Technical Work
Nghiên cứu và triển khai:
* HTTP integration.
* Signature Header.
* HMAC-based request/response security.
* RocketMQ integration.
* HTTP engine.
* Integration với DWS machine.
## Supported Protocols
```text
HMI
FTP
HTTP
```
## Impact
Giải pháp DWS integration được triển khai cho:
```text
16 sortations
```
## Portfolio Presentation
Project này phải được đánh dấu là:
```text
Featured Project
```
vì thể hiện:
* Ownership.
* System integration.
* Security.
* Middleware.
* Production deployment.
---
# 14. Highlighted Achievement — AWB Detection
## Problem
Tự động phát hiện shipping label / AWB từ hình ảnh được camera trên sortation machine chụp.
## Approach
Ứng dụng Computer Vision và Machine Learning.
Pipeline:
```text
Image
↓
AWB / Label Detection
↓
Bounding Box / OBB
↓
Rotation Correction
↓
Crop
↓
OCR
↓
Text Extraction
```
## Technical Areas
* OpenCV.
* Object Detection.
* YOLO.
* Oriented Bounding Box.
* ONNX.
* OCR.
* Image preprocessing.
* Model inference.
## Engineering Challenge
Một trong các challenge chính:
```text
White label
on
White package / box
```
Các phương pháp computer vision truyền thống không phải lúc nào cũng đủ robust.
Từ đó chuyển hướng sang ML-based detection.
## Result
Model được fine-tune cho bài toán AWB detection.
Kết quả được trình bày trong Tech Talk workshop.
## Portfolio Content
Project detail phải tập trung vào:
```text
Why traditional CV was insufficient
↓
Why ML was introduced
↓
Model design
↓
Inference
↓
Post-processing
↓
Production consideration
```
---
# 15. Highlighted Achievement — System Maintenance
## Context
Duy trì và hiện đại hóa hệ thống production theo yêu cầu của security / infrastructure team.
## Technical Work
* Migration sang middleware versions mới.
* OSS cleanup.
* Loại bỏ duplicate DWS images.
* System maintenance.
## Impact
Giảm OSS storage khoảng:
```text
7 GB / month
```
Dựa trên workload khoảng:
```text
70,000 images / month
~100 KB / image
```
## Portfolio Message
Không trình bày đây chỉ là:
> "Maintenance work."
Mà là:
> Continuous engineering work that improves security posture, maintainability, and infrastructure efficiency.
---
# 16. Highlighted Achievement — Scrum / Team Engineering
## Role
Ngoài technical contribution, tham gia Scrum Master responsibilities.
## Activities
* Sprint planning.
* Daily follow-up.
* Weekly follow-up.
* Agile / Scrum metrics.
* Collaboration với team members.
* Collaboration với PDs / stakeholders.
## Result
Team đạt:
```text
Scrum Level L3
```
và nhận được company-recognized reward.
## Portfolio Message
Section này chứng minh:
```text
Technical Leadership
+
Team Collaboration
+
Process Improvement
```
---
# 17. Featured Projects
Homepage chỉ hiển thị 3–4 project nổi bật.
Recommended order:
```text
1. IoT-DWS Integration
2. AWB Detection / Computer Vision
3. Facility Management / Operational Intelligence
4. AI / Engineering Experiments
```
---
# 18. Project Detail Template
Mọi featured project phải tuân theo cùng một cấu trúc.
```text
Project Overview
↓
Problem
↓
Context
↓
Goals
↓
Architecture
↓
Technical Challenges
↓
Solution
↓
Implementation
↓
Results
↓
Lessons Learned
```
---
# 19. Project — Facility Management / Operational Intelligence
## Vision
Xây dựng nền tảng chuyển đổi từ:
```text
Operations
```
sang:
```text
Operation Intelligence Platform
```
Platform thu thập operational data và hỗ trợ operations:
```text
Understand
↓
Monitor
↓
Analyze
↓
Recommend
↓
Decide
```
## Problem
Traditional operation management khó trả lời:
* Facility hiện tại có capacity bao nhiêu?
* Package flow đang như thế nào?
* Workforce đang được sử dụng ra sao?
* Bottleneck ở đâu?
* Nếu volume tăng thì cần thêm resource nào?
* Layout hiện tại có tối ưu không?
## Vision
Digitalize facility model bao gồm:
```text
Facility
├── Areas
├── Workflows
├── Activities
├── Workers
├── Equipment
└── Capacity
```
## Example Workflow
```text
Inbound
↓
Unload
↓
Move package
↓
Sorting
↓
Outbound
```
## Key Capabilities
### Facility Modeling
Operations user có thể define facility:
* Areas.
* Workers.
* Activities.
* Workflows.
UI hỗ trợ:
```text
Drag & Drop
```
để xây dựng facility model.
### Real-time Visibility
Theo dõi:
* Package flow.
* Operational activities.
* Workforce.
* Facility capacity.
### Recommendation
Platform có thể đưa ra recommendation:
```text
Volume forecast
↓
Capacity analysis
↓
Resource requirement
↓
Recommended allocation
```
---
# 20. Facility Digital Twin
Project này có thể trở thành một trong những technical showcase quan trọng nhất.
Architecture concept:
```text
Physical Facility
↓
Data Collection
↓
Facility Model
↓
Digital Twin
↓
Simulation
↓
Analytics
↓
Recommendation
↓
Operation Decision
```
Có thể trình bày các technical concepts:
* Facility graph.
* Workflow graph.
* Resource model.
* Capacity model.
* Discrete Event Simulation.
* Multi-agent simulation.
* Scenario analysis.
---
# 21. AI / ML Engineering Section
Một section riêng:
```text
AI & Machine Learning
```
Không biến portfolio thành AI portfolio.
Thay vào đó thể hiện:
> Tôi ứng dụng AI/ML khi nó giải quyết được một vấn đề thực tế.
Các chủ đề:
* Computer Vision.
* Object Detection.
* OCR.
* YOLO.
* ONNX inference.
* LLM.
* Local LLM.
* Model optimization.
* AI-assisted engineering.
---
# 22. AI Engineering Experiments
Có thể có subsection:
```text
Engineering Experiments
```
Ví dụ:
### Local LLM
Technical exploration:
```text
Qwen
MoE
llama.cpp
GPU offloading
VRAM optimization
Prefill / Decode
Expert routing
Performance tracing
```
Mục tiêu không phải khoe hardware.
Mục tiêu là thể hiện:
```text
Understand the system
↓
Measure
↓
Analyze
↓
Optimize
```
---
# 23. Engineering Blog
Blog không phải blog cá nhân chung chung.
Content focus:
```text
Software Engineering
System Architecture
AI / ML
Computer Vision
Logistics Technology
Performance Engineering
Engineering Experiments
```
## Suggested Articles
Có thể xây dựng các bài:
```text
How I Designed an IoT-DWS Integration System
From Traditional Computer Vision to YOLO-based AWB Detection
Designing a Facility Management Platform for Logistics Operations
Modeling Warehouse Operations with Discrete Event Simulation
Designing a Digital Twin for Logistics Facilities
Running Local MoE LLMs with llama.cpp
Understanding MoE Expert Routing
Building High-performance Event Simulation with Go
```
---
# 24. Engineering Project Presentation
Mỗi project phải có metadata:
```ts
interface Project {
id: string;
title: string;
summary: string;
category: ProjectCategory;
problem: string;
solution: string;
role: string;
technologies: string[];
architecture?: string;
challenges?: string[];
results?: string[];
featured: boolean;
githubUrl?: string;
demoUrl?: string;
images?: string[];
}
```
Category:
```ts
type ProjectCategory =
| "software-engineering"
| "logistics"
| "ai-ml"
| "computer-vision"
| "architecture"
| "experiment";
```
---
# 25. Design Direction
## Visual Style
Portfolio phải có cảm giác:
```text
Modern
Technical
Minimal
Professional
Confident
Engineering-focused
```
Không sử dụng visual style quá:
```text
Corporate
Generic
Template-like
Overly colorful
Overly animated
```
## Inspiration
Visual language có thể lấy cảm hứng từ:
* Developer tools.
* Technical documentation.
* Modern SaaS.
* Architecture diagrams.
* Data visualization.
---
# 26. Color System
Dark mode là visual mode chính.
## Dark
```text
Background: near-black
Surface: dark gray
Text: near-white
Muted: gray
Primary: single accent color
Border: subtle gray
```
## Light
```text
Background: white / near-white
Surface: light gray
Text: near-black
Muted: gray
Primary: same accent
Border: light gray
```
Chỉ sử dụng **một accent color chính** để tránh website quá màu sắc.
---
# 27. Typography
Ưu tiên font hiện đại, dễ đọc.
Typography hierarchy:
```text
Hero H1
64px desktop
40px mobile
H2
40px desktop
32px mobile
H3
24px
Body
16–18px
Small
14px
```
Font cần hỗ trợ tốt:
* Latin.
* Vietnamese diacritics.
---
# 28. UI Components
Reusable components:
```text
Button
IconButton
Badge
Card
Container
Section
SectionHeading
Tag
Timeline
ProjectCard
ProjectGrid
SkillGroup
ArticleCard
CodeBlock
ImageGallery
Modal
Tooltip
Navigation
MobileNavigation
Footer
```
---
# 29. Architecture Visualization
Đối với các project kỹ thuật quan trọng, cho phép hiển thị interactive architecture diagram.
Ví dụ:
```text
Camera
│
▼
Image Pipeline
│
▼
YOLO Model
│
▼
Post Processing
│
▼
OCR
│
▼
Business System
```
User có thể:
* Zoom.
* Pan.
* Click node.
* Xem technical explanation.
Nếu interactive diagram quá phức tạp, sử dụng static SVG trước.
---
# 30. Animation
Animation phải rất subtle.
Cho phép:
* Fade.
* Slide.
* Scale nhẹ.
* Hover.
* Scroll reveal.
Không sử dụng:
* Parallax quá mạnh.
* Particle background quá dày.
* Continuous animation gây distraction.
* Animation blocking content.
Support:
```css
prefers-reduced-motion
```
---
# 31. Responsive Design
## Mobile
Ưu tiên:
```text
Content
↓
Readable typography
↓
Touch interaction
```
Không cố gắng giữ desktop layout trên mobile.
## Tablet
Adaptive grid.
## Desktop
Có thể sử dụng:
```text
2-column
3-column
wide architecture diagrams
sticky navigation
```
---
# 32. Dark / Light Theme
Modes:
```text
Dark
Light
System
```
Default:
```text
System
```
Persist:
```text
localStorage
```
Không để xảy ra theme flash khi page load.
---
# 33. Technical Stack
## Required
```text
React
TypeScript
Vite
```
## Recommended
```text
React Router
Vitest
Testing Library
Playwright
oxlint
Prettier
```
## Styling
Ưu tiên:
```text
CSS Modules hoặc Tailwind CSS
```
Quyết định cuối cùng phải đảm bảo:
* Design tokens.
* Responsive.
* Dark mode.
* Maintainability.
---
# 34. Frontend Architecture
```text
src/
├── app/
│ ├── router/
│ └── providers/
│
├── components/
│ ├── ui/
│ ├── layout/
│ └── portfolio/
│
├── pages/
│ ├── Home/
│ ├── About/
│ ├── Experience/
│ ├── Projects/
│ ├── ProjectDetail/
│ ├── Blog/
│ └── Contact/
│
├── data/
│ ├── profile.ts
│ ├── experience.ts
│ ├── projects.ts
│ ├── skills.ts
│ └── articles.ts
│
├── hooks/
├── lib/
├── types/
├── styles/
├── assets/
│
├── App.tsx
└── main.tsx
```
---
# 35. Content Architecture
Content phải tách khỏi presentation.
Ví dụ:
```text
profile.ts
experience.ts
projects.ts
skills.ts
articles.ts
```
Không hard-code portfolio data trong JSX.
Mục tiêu:
```text
Content
↓
Data
↓
Components
↓
Pages
```
---
# 36. State Management
Không sử dụng global state management nếu không cần thiết.
Local state cho:
* Mobile navigation.
* Theme.
* Modal.
* Filters.
* Contact form.
Không sử dụng Redux chỉ cho mục đích portfolio.
---
# 37. Routing
Routes:
```text
/
/about
/experience
/projects
/projects/:projectId
/engineering
/blog
/blog/:slug
/contact
```
404:
```text
/404
```
---
# 38. SEO
Mỗi route phải có:
```text
title
description
canonical
Open Graph
```
Project detail có SEO metadata riêng.
Blog article có:
```text
article:title
article:published_time
article:author
```
Generate:
```text
sitemap.xml
robots.txt
```
---
# 39. Resume
Website phải có CTA:
```text
Download Resume
```
Resume có thể là PDF.
Vị trí:
* Hero.
* About.
* Navigation hoặc Contact.
Không để Resume trở thành CTA lớn hơn Projects.
---
# 40. Contact
Thông tin chính:
```text
Email
GitHub
LinkedIn
```
Contact form là optional.
Nếu chưa có backend:
```text
mailto:
```
có thể được sử dụng ở Phase 1.
Nếu triển khai backend:
```text
POST /contact
```
phải có:
* Validation.
* Rate limiting.
* Spam protection.
---
# 41. Accessibility
Target:
```text
WCAG 2.2 AA
```
Requirements:
* Semantic HTML.
* Keyboard navigation.
* Visible focus.
* Proper heading hierarchy.
* Alt text.
* Accessible links.
* Accessible buttons.
* Form labels.
* Contrast.
* Reduced motion.
---
# 42. Performance
Target:
```text
LCP < 2.5s
INP < 200ms
CLS < 0.1
```
Requirements:
* Image optimization.
* Lazy loading.
* Code splitting.
* Minimal dependencies.
* Avoid unnecessary JavaScript.
* Optimize fonts.
* Avoid oversized hero assets.
---
# 43. Security
* Không commit secrets.
* Không expose API secrets.
* Validate external content.
* Sanitize Markdown/HTML.
* Dependency audit.
* Không sử dụng `dangerouslySetInnerHTML` nếu không cần.
* Contact endpoint phải có rate limiting nếu được triển khai.
---
# 44. Analytics
Analytics chỉ dùng để hiểu usage.
Events:
```text
page_view
project_view
project_github_click
project_demo_click
resume_download
contact_click
social_click
article_view
```
Không track:
* Sensitive information.
* Keystrokes.
* Unnecessary personal data.
---
# 46. Code Quality
Required:
```text
TypeScript strict mode
ESLint
Prettier
```
Rules:
* Avoid `any`.
* Explicit public component props.
* Small components.
* No duplicated business logic.
* No dead code.
* No debug logging.
* Consistent naming.
---
# 47. Git Convention
Branches:
```text
main
develop
feature/*
fix/*
refactor/*
```
Commits:
```text
feat:
fix:
refactor:
docs:
test:
chore:
```
Examples:
```text
feat: add project detail page
feat: add dark mode
fix: mobile navigation overflow
refactor: extract project card
docs: update portfolio specification
```
---
# 49. Deployment
Portfolio phải có khả năng deploy static.
Ưu tiên:
```text
Vercel
```
Alternative:
```text
Cloudflare Pages
Netlify
GitHub Pages
```
Requirements:
* HTTPS.
* Custom domain.
* Automatic deployment.
* Preview deployment cho Pull Request.
---
# 50. Browser Support
Hỗ trợ:
```text
Chrome
Edge
Firefox
Safari
```
Không cần hỗ trợ legacy browsers nếu không có requirement đặc biệt.
---
# 51. Internationalization
Primary language:
```text
Vietnamese
```
Architecture phải sẵn sàng cho:
```text
English
```
Trong tương lai có thể chuyển portfolio sang English-first nếu phục vụ international opportunities.
---
# 52. Content Rules
## Không viết
```text
I am passionate about technology.
I am hardworking.
I am a fast learner.
I am a team player.
```
nếu không có evidence.
## Ưu tiên
```text
Built X
Designed Y
Reduced Z
Deployed to N facilities
Implemented X
Solved Y
Improved Z
```
Portfolio phải ưu tiên **evidence over adjectives**.
---
# 53. Impact Metrics
Khi có thể, project phải có metric.
Ví dụ:
```text
16 sortations deployed
~7 GB/month OSS reduction
70,000 images/month processed
X% performance improvement
X ms latency
X requests/sec
```
Không bịa metric.
Nếu không có số liệu chính xác, sử dụng qualitative impact.
---
# 54. Project Storytelling Standard
Mỗi featured project phải có:
```text
01 — Context
02 — Problem
03 — Constraints
04 — Solution
05 — Architecture
06 — Implementation
07 — Challenges
08 — Result
09 — Lessons Learned
```
---
# 55. Personal Growth Section
Có thể có section:
```text
What I'm Exploring
```
Thể hiện những lĩnh vực đang phát triển:
* AI in logistics.
* Intelligent operations.
* Digital twins.
* Simulation.
* Multi-agent systems.
* LLM.
* Computer Vision.
* High-performance systems.
Mục tiêu là thể hiện:
```text
Current expertise
+
Future direction
```
---
# 56. Long-term Career Narrative
Portfolio cần phản ánh career direction:
```text
Software Engineering
↓
System Engineering
↓
Logistics Technology
↓
Operational Intelligence
↓
AI-powered Logistics
```
Đây là narrative quan trọng hơn việc liệt kê thật nhiều technology.
---
# 57. Future Vision
Portfolio có thể dần phát triển thành:
```text
Personal Website
↓
Engineering Portfolio
↓
Engineering Knowledge Base
↓
Technical Blog
↓
Personal Engineering Lab
```
Trong tương lai có thể bổ sung:
* Interactive architecture diagrams.
* Simulation demos.
* AI experiments.
* Engineering benchmarks.
* Technical playground.
* System design visualizations.
---
# 58. Non-functional Requirements
## Maintainability
Code phải modular và dễ mở rộng.
## Scalability
Architecture cho phép thêm:
* Project.
* Article.
* Experience.
* Skill.
* Language.
mà không cần thay đổi component architecture.
## Performance
Website phải nhanh ngay cả khi số lượng project/article tăng.
## Accessibility
WCAG 2.2 AA target.
## SEO
Mỗi public page có metadata riêng.
## Reliability
Không được crash khi:
* Missing image.
* Missing optional URL.
* Invalid project slug.
* Missing article.
* External resource unavailable.
---
# 59. Acceptance Criteria
## Homepage
* [ ] Hero hiển thị đúng.
* [ ] Positioning rõ ràng.
* [ ] CTA Projects hoạt động.
* [ ] CTA Contact hoạt động.
* [ ] Social links hoạt động.
* [ ] Responsive.
## About
* [ ] Professional profile rõ ràng.
* [ ] Engineering philosophy rõ ràng.
* [ ] Current interests hiển thị.
## Experience
* [ ] Experience timeline.
* [ ] Achievements.
* [ ] Technical contributions.
* [ ] Impact metrics.
## Projects
* [ ] Featured projects.
* [ ] Project detail.
* [ ] Technology stack.
* [ ] Architecture.
* [ ] Challenges.
* [ ] Results.
## Engineering
* [ ] AI/ML.
* [ ] Architecture.
* [ ] Experiments.
## Blog
* [ ] Article list.
* [ ] Article detail.
* [ ] Code blocks.
* [ ] Syntax highlighting.
## Resume
* [ ] Resume download.
## Contact
* [ ] Email.
* [ ] GitHub.
* [ ] LinkedIn.
* [ ] Optional contact form.
## Theme
* [ ] Dark.
* [ ] Light.
* [ ] System.
* [ ] Persist preference.
## Accessibility
* [ ] Keyboard.
* [ ] Focus.
* [ ] Screen reader.
* [ ] Contrast.
* [ ] Reduced motion.
## SEO
* [ ] Metadata.
* [ ] Open Graph.
* [ ] Sitemap.
* [ ] Robots.
## Performance
* [ ] LCP target.
* [ ] INP target.
* [ ] CLS target.
* [ ] Optimized images.
---
# 60. Definition of Done
Feature được xem là hoàn thành khi:
* [ ] Requirement implemented.
* [ ] TypeScript không có error.
* [ ] oxlint pass.
* [ ] Tests pass.
* [ ] Build pass.
* [ ] Responsive.
* [ ] Accessibility checked.
* [ ] SEO checked.
* [ ] Performance checked.
* [ ] Không có console error.
* [ ] Không có unnecessary dependency.
* [ ] Code reviewed.
* [ ] Documentation updated nếu cần.
---
# 61. Development Phases
## Phase 1 — Foundation
* [ ] Vite.
* [ ] React.
* [ ] TypeScript.
* [ ] oxlint.
* [ ] Prettier.
* [ ] Routing.
* [ ] Design system.
* [ ] Theme.
## Phase 2 — Core Portfolio
* [ ] Hero.
* [ ] About.
* [ ] Expertise.
* [ ] Experience.
* [ ] Projects.
* [ ] Contact.
* [ ] Footer.
## Phase 3 — Engineering Showcase
* [ ] Project detail.
* [ ] Architecture diagrams.
* [ ] AI/ML section.
* [ ] Engineering experiments.
* [ ] Resume.
## Phase 4 — Knowledge
* [ ] Blog.
* [ ] Markdown / MDX.
* [ ] Code highlighting.
* [ ] Article SEO.
## Phase 5 — Production
* [ ] Testing.
* [ ] Accessibility audit.
* [ ] Performance audit.
* [ ] SEO audit.
* [ ] CI/CD.
* [ ] Deployment.
* [ ] Custom domain.
---
# 62. Priority
## P0 — Must Have
```text
Homepage
About
Experience
Projects
Contact
Responsive
Dark/Light
SEO
Accessibility
Performance
```
## P1 — Important
```text
Project Detail
Resume
Engineering Section
Architecture diagrams
Blog
```
## P2 — Future
```text
Interactive diagrams
Search
Analytics
CMS
Multi-language
Technical playground
Simulation demos
AI assistant
```
---
# 63. Success Criteria
Portfolio thành công khi người truy cập có thể hiểu trong khoảng 1–2 phút:
```text
Who is this engineer?
↓
What does he specialize in?
↓
What has he built?
↓
What impact did he create?
↓
What kind of engineering problems does he care about?
↓
How can I contact him?
```
Đặc biệt, người xem phải nhận ra được 3 đặc điểm:
```text
1. Strong Software Engineering
2. Real-world Logistics / System Experience
3. Ability to apply AI/ML to practical problems
```
---
# 64. Final Product Principle
Portfolio không phải là một collection của:
```text
Skills
Certificates
Job titles
Technology logos
```
Mà là một collection của:
```text
Engineering Problems
+
Technical Decisions
+
Systems Built
+
Measured Impact
+
Lessons Learned
```
Mục tiêu cuối cùng:
> **Show, don't just tell.**
Website phải khiến người xem có cảm giác:
> “Đây là một Senior Software Engineer có khả năng ownership một bài toán từ business problem → system design → implementation → production → measurable impact.”
---
# 65. Technical Stack Summary
```text
Frontend
├── React
├── TypeScript
└── Vite
Architecture
├── Component-based UI
├── Data-driven content
└── Route-based pages
Testing
├── Vitest
├── Testing Library
└── Playwright
Quality
├── TypeScript strict
├── oxlint
└── Prettier
Deployment
└── Vercel / equivalent static hosting
```
---
# 66. Portfolio Identity Summary
```text
PERSONAL PORTFOLIO
│
┌────────────────┼────────────────┐
│ │ │
SOFTWARE ENGINEERING LOGISTICS AI / ML
│ │ │
Architecture Operations Computer Vision
Distributed Facilities Object Detection
Systems Integration OCR
Backend Digital Twin LLM
│ │ │
└────────────────┼────────────────┘
│
ENGINEERING IMPACT
│
BUILD → MEASURE
│
LEARN
```
---
# 67. Final Statement
Portfolio phải thể hiện một engineering journey:
```text
Build reliable systems
↓
Understand operations
↓
Solve real-world problems
↓
Apply intelligent technologies
↓
Measure impact
↓
Keep learning
```
Đây là định hướng xuyên suốt của toàn bộ website.