Notes / Tag
#learning
Abstraction and naming
Abstraction hides details so you can think about one thing at a time; names are how you point at what's hidden. What a good abstraction looks like, how names carry meaning, the conventions in Python, JavaScript, Go and PHP, and what happens when an abstraction leaks.
Algorithms and Big-O without the heavy math
Why some code gets slow as data grows and some doesn't. What an algorithm is, how Big-O describes growth, the handful of classes you'll actually meet, and real timings that show the difference.
APIs and integration
Calling other systems, and being called by them. What an API is, JSON, why every request needs a timeout, retrying the right way, rate limits, pagination, idempotency keys so a retry doesn't charge twice, and verifying webhooks. Run against a small mock API, in Python and PHP.
Basic data structures
Lists, maps, sets, stacks, and queues: what each one is good at, how they look in Python, JavaScript, PHP, and Go, and why picking the right one can make code tens of thousands of times faster.
Bits, bytes, and data types
Everything in memory is just bits. Data types decide what those bits mean, and why 0.1 + 0.2 isn't 0.3, an int8 can wrap to -128, and an emoji can be 4 bytes long.
Breaking a problem down
How to go from a vague request to working code: understand the problem, list examples and edge cases, split it into small functions, build and test each piece, then put them together. One worked example, start to finish.
Concurrency basics
Doing several things at once makes programs faster and introduces a new kind of bug. Concurrency vs parallelism, why waiting is the usual reason to go concurrent, async in Python and JavaScript, race conditions you can reproduce, locks, Go's race detector, and the database version of the same bug.
Conditions and boolean logic
True, false, and everything in between: truthy and falsy values, short-circuit evaluation, == vs ===, || vs ??, De Morgan's laws, and how to keep if statements readable.
Databases and SQL basics
Why most applications keep their data in a relational database, and the SQL you need every day: tables and keys, SELECT with WHERE and ORDER BY, JOIN, GROUP BY, NULL, constraints, transactions, indexes, and placeholders. Every example run against a real SQLite database.
Debugging systematically
Debugging is not guessing until it works. It's a method: reproduce the bug, read what the program tells you, form a guess, test it, narrow it down. One real bug traced start to finish, plus print and logging, debuggers in four languages, and git bisect.