Public log of a self-taught journey from junior Go developer to a systems-level backend engineer, targeting open-source-first remote companies like GitLab, Canonical, and Grafana Labs.
Become a Go Backend Engineer with deep systems understanding — not just someone who writes code, but someone who understands why it works: memory, concurrency, networking, architecture.
Timeline: 2-year roadmap, structured in 12-week cycles ("12 Week Year" method).
Target companies: GitLab · Canonical · Grafana Labs · HashiCorp · Cockroach Labs
Focus: Go Core internals · CS50x · TryHackMe Pre Security
Go Core ████░░░░░░░░░░░░░░░░ 20% CS50x ██░░░░░░░░░░░░░░░░░░ 10% TryHackMe ░░░░░░░░░░░░░░░░░░░░ 0% (Update manually each week — percentages are illustrative)
| Folder | Description |
|---|---|
cs50/ |
Notes from Harvard's CS50x — computer science fundamentals |
go-core/ |
Deep-dive Go internals — types, memory, concurrency, interfaces |
infosec/ |
TryHackMe Pre Security path — networking & Linux fundamentals |
- Week 0 — Scratch
- Week 1 — C
- Week 2 — Arrays
- Week 3 — Algorithms
- Week 4 — Memory
- Week 5 — Data Structures
- Data types & memory sizes
- Slices, arrays, maps internals
- Pointers & escape analysis
- Interfaces (nil interface trap)
- Goroutines & scheduler (GMP)
- Channels
- Sync package
- Context
- Error handling
- Database drivers (pgx, pq, gorm)
- Pre Security path
- Linux Fundamentals 1–3
This repo is both a personal accountability tool and a transparent record of consistent, structured learning — the kind of signal that matters to companies who value open-source contribution and self-direction over credentials alone.
GitHub: @MahmudovMZ