Fundamentals of Containerization
Containerization fundamentals: images, layers, namespaces, cgroups, and why containers make software portable and reproducible across environments.
Containerization fundamentals: images, layers, namespaces, cgroups, and why containers make software portable and reproducible across environments.
Empirical software engineering fundamentals: how systematic data collection and analysis replace opinion with evidence about how software is built and used.
Architecture decision making fundamentals: how to spot decisions that matter, weigh trade-offs, judge reversibility, and record choices with ADRs.
Data architecture fundamentals: the staging, core, and semantic layers, why architecture is not tools, and how batch and streaming data land.
Analytics engineering fundamentals: the role between data engineering and analysis, ELT, the transformation layer, testing, and the semantic layer.
What is Ollama and how does it run large language models locally on consumer hardware?
Learn the fundamentals of technical leadership: credibility, vision, communication, empowerment, and decision-making that turn engineers into leaders.
Agent accessibility fundamentals: make your APIs and software products discoverable, predictable, and usable by AI agents.
Software traffic management fundamentals: control planes, service meshes, sidecars, and routing strategies for resilient distributed systems.
Software automation fundamentals: core principles, build systems, infrastructure as code, and when automation pays off versus when it creates more problems.
Concurrency and parallelism explained: why they differ, how threads and async work, and how to reason about race conditions, deadlocks, and synchronization.
Software systems integration fundamentals: strategies, patterns, and trade-offs for connecting systems that need to work together.
Why JavaScript works the way it does: dynamic typing, prototypes, closures, and the event loop. Concepts behind the design and when it fits.
Why Rust exists: memory safety without garbage collection, ownership, and fearless concurrency. Learn the concepts behind Rust's design and when it fits.
Why FinOps exists and how it works: visibility, accountability, and the Inform-Optimize-Operate lifecycle. Learn the concepts behind cloud financial operations.
Why Azure works the way it does: regions, Entra ID, resource groups, and core services. Learn the concepts that shape Microsoft cloud decisions.
Why AWS works the way it does: regions, IAM, shared responsibility, and core services. Learn the concepts that shape cloud decisions.
Glossary of terms for software fundamentals (maintainability, design, naming, and related topics).
Why software maintainability matters: structural complexity, understandability, technical debt, coupling, and code smells. Learn the principles that keep code changeable over time.
Fitness review skills turn fundamentals into repeatable, scored code reviews across architecture, security, reliability, and more.
Why graph databases exist, when to use them, and how they differ from relational databases. Learn nodes, edges, and relationship-first querying.
Timeout fundamentals for software: why timeouts exist, connection vs read vs write, choosing values, and avoiding cascading failures in distributed systems.
Logical fallacies like sunk cost, false dichotomy, and confirmation bias derail software projects. Learn to recognize and avoid faulty reasoning traps.
Understanding centralized software systems: when single points of control work, why they're simpler than distributed systems, and when to choose them over distributed alternatives.