Six Lectures and a Companion Site for Non-Developers
Internal Dev Literacy Course
- Period
- Jul 2026 – Aug 2026
- Role
- Planned, built & taught
- Satisfaction
- 5/5 전원
- Recommend
- 9.7/10
Background
- Many colleagues were non-developers like me, and words like 'deploy' and 'API' were still hard for them. You can ask AI anything now — but without the basic flow, you don't know what to ask. During my LIKELION internship I planned, built, and taught the course on my own. (Jul – Aug 2026)
Execution
Curriculum & Teaching — Solo
- Designed a 6-session lunchtime curriculum and taught it weekly for 6 weeks — software structure, dev vocabulary, Git & GitHub, collaboration communication, AI & vibe coding, AI trends.
- Unified every concept under one restaurant metaphor — dining hall = frontend, kitchen = backend, fridge = DB, order slip = API — so each session added to the same picture.
Built the Companion Site
- Built the site with React · TypeScript · Vite — 14 SVG concept diagrams, live in-browser demos (login round-trip, Git collaboration simulator), and a 51-term glossary.
- Cut every exercise that needed installs or accounts — assuming people listen over lunch, only what works from a single link stayed.
Results
- Attendee survey (n=6): 5/5 satisfaction across the board, 9.7/10 average recommendation, 4.7/5 on 'I understand more of developer conversations now.'
- Feedback said it was 'too short,' with requests for follow-ups on infrastructure, databases, and dev collaboration.
What I learned
- The biggest decision was not teaching code. Narrowing the goal from 'becoming a developer' to 'talking with developers' made clear what fit in six sessions and what didn't — teaching, too, was scope cutting.