Chief Galen Tyrol

Concepts imported from YouTube curation: https://www.youtube.com/playlist?list=PL-ow7a_42PpTmXB7kms5mZ7y6bCaDn-Dy

The interpersonal half of running projects, grounded in organizational and social psychology rather than management folklore. Starts with the conditions that let a team tell you the truth — psychological safety, listening, feedback — then works out through delegation, meetings, negotiation and influence, into the judgment problems that wreck schedules: the planning fallacy, decisions under uncertainty, scope trade-offs and burnout. Every concept traces back to a named finding you can go read.

Riding and maintaining a mountain bike on the North Texas prairie. Starts with the ground you actually ride — black-clay gumbo that must never be ridden wet, limestone ledges, mesquite thorns, and summer heat — then works through body position and cornering on tight, twisty, low-elevation singletrack, tire choice and pressure for loose-over-hard hardpack, and the drivetrain, brake, wheel and suspension work that keeps a bike running through it. Every concept is one video and five questions, and every one has its prerequisites mapped two layers deep, so you can start wherever your knowledge actually runs out.

Concepts imported from YouTube curation: https://www.youtube.com/playlist?list=PL2-FHRIF3qm8Nc4jQ_axpiEf1XEics8mc

Concepts imported from YouTube curation: https://www.youtube.com/playlist?list=PL2kbnl4tl3vZ-AC02mVPhqv_YxlMkcH3X

How do you get from a page of requirements to a system design you can defend in a review? Solutions architecture is the discipline of making that trip on purpose: turning vague quality goals—fast, reliable, scalable, secure, affordable—into measurable scenarios, decomposing the system into components with clear contracts, choosing the tactic that buys each quality attribute, and writing down the trade-off so the next person understands why. This path walks that sequence. You will learn to write a quality attribute scenario with a stimulus, a response and a number; to separate a constraint from a requirement; to decide where a synchronous call ends and a queue begins; to reason about availability, scalability, latency and consistency with the arithmetic behind each rather than the vendor's slogan; and to record an architecture decision so that it can be revisited when its assumptions expire. The design examples use cloud building blocks—load balancers, caches, standby databases, queues—because that is where most systems are built today, but every Concept is vendor-neutral and holds on any platform. You need to have built or run at least one web service with a database. No certification is assumed or targeted.