IssueRaiser

Full stack dev: topics to teach

This is the early planning of a new course "uncool full stack development" or something similar. Basically, I want to show people how to use simple broad-purpose tools, rather than SAAS and complex stuff like docker. So we'll be looking at cron, bash, perl, simple VPS servers, etc. Why? Because: it's cheaper (use a single cheap server to do loads of stuff, rather than signing up for heaps of SAAS that do one little thing); you learn the foundations of everything else, which is knowledge that never goes out of date; rather than learning lots of domain specific languages, config files, and APIs, for every different service, you learn a small number of powerful foundations you can re-use everywhere; when you're working with SAAS or higher-level frameworks, you can debug your problems because you know what's happening underneath; lots of interviews ask about lower-level foundations, so it'll help you get recruited; for building a startup or hobby project, it's far cheaper, easier, and more scalable when you're in control of what you're doing and you understand how it all works. ## Contents (links to sections) - [CLI tools](https://github.com/jph00/notes/issues/3#issuecomment-695805101) - [Concepts](https://github.com/jph00/notes/issues/3#issuecomment-695805120) - [Protocols/foundations](https://github.com/jph00/notes/issues/3#issuecomment-695805134) - [Programming tools](https://github.com/jph00/notes/issues/3#issuecomment-695805149) - [Basic services](https://github.com/jph00

Posted by jph00 on Sep 20, 2020, 3:33 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments

github (SaaS)

Full stack dev: topics to teach

jph00Sep 20, 2020, 3:33 PM

This is the early planning of a new course "uncool full stack development" or something similar. Basically, I want to show people how to use simple broad-purpose tools, rather than SAAS and complex stuff like docker. So we'll be looking at cron, bash, perl, simple VPS servers, etc. Why? Because: it's cheaper (use a single cheap server to do loads of stuff, rather than signing up for heaps of SAAS that do one little thing); you learn the foundations of everything else, which is knowledge that never goes out of date; rather than learning lots of domain specific languages, config files, and APIs, for every different service, you learn a small number of powerful foundations you can re-use everywhere; when you're working with SAAS or higher-level frameworks, you can debug your problems because you know what's happening underneath; lots of interviews ask about lower-level foundations, so it'll help you get recruited; for building a startup or hobby project, it's far cheaper, easier, and more scalable when you're in control of what you're doing and you understand how it all works. ## Contents (links to sections) - [CLI tools](https://github.com/jph00/notes/issues/3#issuecomment-695805101) - [Concepts](https://github.com/jph00/notes/issues/3#issuecomment-695805120) - [Protocols/foundations](https://github.com/jph00/notes/issues/3#issuecomment-695805134) - [Programming tools](https://github.com/jph00/notes/issues/3#issuecomment-695805149) - [Basic services](https://github.com/jph00

Comments (0)

No comments yet. Start the discussion.

Comment on this issue