Syllabi

Why the titles are not subject names but some weird goals kind of thing?

I always had issues relating what I am studying to how I am going to use it. A foolish attempt to resolve this is to mention the why of the syllabus instead of the syllabus name(subject). Also it’s easier to tell the why then to assign a subject because the resources I have under them are somewhat unstructured.

Whenever I have a new information resource, I categorize it at entry. It can go under any one of these:

I try my best to not repeat links across these pages. I have not setup any automated link checker for either duplication/backlinks/linkrots etc.

This is my syllabi created in October'22.

πŸ’Ό HB01: How businesses works #

Understand basic economics #

Additional cherry for businesses #

Understand how to start #

πŸ₯• HB02: Become more confident with problem solving #

Revisit the basics #

Deal with long term fears #

πŸ†˜ HB03: Get back at basic math #

Get introduced #

Resurface basic comp sci math #

Permutations and numbers #

Linear Algebra #

Binary math #

🌎 HB04: Get a grip over Web Development #

Get your HTTP basics right #

React and Typescript way to mastery #

Get a hold of web engineering #

Time for Webassembly #

Other experiments with web that are worth #

Get your web security right #

πŸ‚ HB05: Computer graphics #

Basics of CG #

Ray tracing #

WebGPU #

Easings #

ThreeJS #

πŸ” HB06: Basic security knowledge upgrade #

Server, sessions and web #

OAuth and OIDC and Tokens #

For personal knowledge #

Cryptography #

🐲 HB07: Become functional #

Be at ease with Python #

Be at ease with shell scripting and my local system #

Be building with Golang #

Other things #

🚒 HB08: Server Admin and network troubleshooter #

Deploying systems #

Maintaining Services #

Containers #

Kubernetes #

Oops! Observability #

Oh CI/CD #

Network must be up! #

What’s up DNS? #

πŸ” HB09: Remove database fear #

DB general knowledge #

SQL Basics #

Context on DBs #

Joins #

SQLite #

Postgres #

Too long Redis #

Infra Operations & Security #

πŸ– HB10: Become pragmatic #

Gain old wisdom #

Advice by other people #

Testing shit #

Learn more about API design #

General API #

Web API design #

Caching #

🌺 HB11: Languages and how they are made #

Experiment with Rust #

Experiment with Elixr #

Remove fear of compilers #

No really, PLT fr #

No time for Functional programming #

DIY projects #

πŸ¦† HB12: Comfortable w Distributed Systems #

General Dist Sys #

Designing better systems #

πŸ… HB13: Really wanna Systems #

A word of warning for self here, I am interested in this stuff but it seems like there are not too many directly applicable jobs or projects I can work on, so study these accordingly.

But this info in-directly will always be helpful for me in other areas.

Basics #

Virtualization #

Finally File-systems and Storage #

Performance #

BPF & eBPF #

Strace #

Arch #

πŸ•Έ HB14: Scraping and Archival #

Become spiderman #

Become spiderman at scale #

Archiving for the greater good #

Maintaining archives #

γŠ™ HB15: Working with data #

Probability and Statistics #

Do the work with Data science #

Data processing #

Deploying stuff #

LLMs in production #

HB17: Analyze, Visualize and Plot! #

Learn to plot #

Simulations #

Example case studies #

Random examples to reverse engineer from.

HB18: Get creative w programming #

“It often feels like ‘hacking’ to get result.”

Get started w it #

Learn by doing #

HB19: Hello Beep Boop HCI #

Get familiar #

How we do the internet thing #

HB20: Understand P2P #

General P2P #

Torrent #

Alternative internet #

Protocols&Encoding #

wtf NAT #

Time for WebRTC #

HB21: Geo and Maps #

Basics #

Get mapping #

Play #

GPS #

QGIS #

HB22: Local First Stuff #

Basics #

Sync Server/Engine #

Game network engines #

CRDTs #

HB24: Network Programming #

Network Programming wen #

RPC #

🏜 HB16: Some Art & Craft is nice #

HB:23: Electronics & Hardware #

Electronics basics #

Micro-controller #

Radio & Wireless #

Robotics #

Prototyping #