# Build Better: Master the Fundamentals Today! Newsy: Dev Concepts Weekly Published: 2025-10-20T13:00:00.280Z Source: https://newsyai.com/edition/9c7517bf-7335-4690-a844-320fb5eacc19 Archive: https://newsyai.com/newsy/249754d5-9f20-4825-9aeb-daeec7c365c9.md --- # The Pros Know the Fundamentals Better! Daily Edition — October 20, 2025 > “Simple pieces, clean seams, steady change.” Below are 3 high‑leverage topics (about 90 seconds each) to compound your growth as a developer. No jargon—just ideas you can use today. --- ## 1) Compose, Don’t Inherit: Build With LEGO, Not Family Trees Inheritance feels tidy—“this is a kind of that”—until the family drama starts. One change in a parent ripples through the cousins, and a small tweak becomes a reunion gone wrong. **What it means** - Favor small, focused pieces you can plug together (composition) over deep hierarchies. - Model capabilities (“can log,” “can cache,” “can validate”) rather than bloodlines (“is a SuperUltraService”). **Why pros care** - Composable pieces are easier to test, reuse, and replace. You can evolve behavior by swapping bricks instead of rewriting a clan. **How to apply** 1. Start with verbs: list the behaviors your thing must do. Make each a small module. 2. Keep pieces narrow: one reason to change, one job done well. 3. Wire them together at the edges: pass pieces in via parameters or configuration, not hard‑coded global singletons. 4. Prefer “has a” and “uses a” over “is a.” **Metaphor** - A food truck: change the menu by swapping a grill insert, not by rebuilding the truck from scratch. **Try this today** - Find one class with “and” in its description. Split it into two small parts and compose them. **Connect to the craft** - Composition gives you optionality. It turns your codebase into a box of reliable bricks instead of a brittle family tree. --- ## 2) The Dependency Diet: Be Picky, Wrap It, Watch It Libraries are like power tools—amazing, until one slips. Every external dependency is borrowed complexity you must service forever. **What it means** - Choose fewer, better dependencies. Hide them behind your own small interface so their churn doesn’t become your churn. **Why pros care** - Most outages and upgrade pain come from the edges. A disciplined dependency strategy keeps your core stable and your upgrades boring. **How to apply** 1. Pause before adding: does your language or standard library already solve this? Is the dependency actively maintained? What’s the transitive bloat? 2. Create a thin wrapper: expose only what you need via your `Adapter` or `Gateway`. Your code calls your wrapper; only the wrapper calls the library. 3. Pin and plan: lock versions, track release notes, and schedule upgrades like routine maintenance—not emergencies. 4. Measure blast radius: keep dependencies out of core domain logic; concentrate them at boundaries. **Metaphor** - A universal travel adapter: you can swap countries (libraries) without rewiring your devices (domain code). **Try this today** - List your top 5 dependencies. For each, answer: what’s our wrapper? who owns it? when’s our next planned upgrade? **Connect to the craft** - A healthy dependency diet buys you speed later. You move faster when the floor isn’t shifting under your feet. --- ## 3) Make Deletion Cheap: Design So Things Can Leave Great teams aren’t just good at adding features—they’re excellent at removing them. If deletion is risky, your codebase will only grow barnacles. **What it means** - Structure code, data, and configuration so you can retire parts with confidence: no hidden ties, no surprise side effects. **Why pros care** - Deletable systems stay lean, readable, and safe to change. You prevent “forever features” and reduce cognitive load. **How to apply** 1. One entry, one exit: give each feature a single switch (flag, route, module) where it can be turned off and removed. 2. Reference by contract: other parts depend on a stable interface, not on internal IDs or tables that are hard to untangle. 3. Separate lifecycle data: mark data created by a feature so it can be archived or migrated independently. 4. Sunset playbook: announce, disable by default, remove code paths, delete data, then delete the switch. **Metaphor** - Removable wallpaper: apply it cleanly, peel it off without tearing the wall. **Try this today** - Pick a stale feature. Add a single kill switch and log its usage. After two weeks of zero traffic, remove it—code, config, and data. **Connect to the craft** - Deletion is the ultimate refactor. When it’s easy to remove things, everything else—testing, upgrades, onboarding—gets easier too. --- ### Quick Recap - Build with LEGO: small, composable pieces beat deep inheritance trees. - Be selective with tools: wrap dependencies and plan upgrades. - Design for goodbye: features should be easy to turn off and remove. Keep stacking fundamentals. Small, sturdy habits today compound into superpowers tomorrow.