More than syntax, teaching interns the real developer workflow
21 days of sessions on how developers actually work day to day. Git, deployments, DNS, auth, APIs, and the public record a developer leaves behind.
Over 21 days, I ran a set of classes for a small group of interns on Google Meet. It wasn't line-by-line syntax teaching. It was how developers actually work day to day: the tools, the workflow, and how to show real projects.
What we covered
LinkedIn for profiles and recruiter visibility. Git and GitHub for version control, pull requests, commits, and merge conflicts. The GitHub Student Pack for domains, design tools, and hosting credits. Vercel for deploying frontend and full-stack projects with custom domains. Namecheap for buying domains and DNS. Overleaf and LaTeX for resumes that pass ATS filters. Supabase for auth and a simple database. React with Vite for the frontend. The OpenAI API for adding AI features. Markdown for READMEs and docs.
What they could do by the end
They could explain what full-stack development means, how a site goes from a push to a live Vercel deploy, how to call an API securely with environment variables, and why a GitHub and LinkedIn presence matters alongside the code.
The part that mattered most was not any single tool. It was that they stopped treating deployment, domains, and auth as someone else's job.