Two small systems that taught me real-world engineering better than any job ticket

Over a two-week vacation, I worked on two projects: DIY e-paper reader Full-stack Excel-based invoicing app for my dad. I started thinking I was smart enough to tackle the problems quickly. But every step humbled me from UX design to product thinking, hardware quirks, deadlines, and real-world constraints. These projects weren’t about "building something perfect." They were about the lessons in iteration, discovery, and the countless blind spots I never knew existed. DIY e-Paper Reader Don’t buy a jet engine for a bicycle Hardware Restraint: I stuck to the philosophy of avoiding over-specification. There is no point in sourcing a "jet engine" (expensive, high-power components) for a "bicycle" (a simple e-reader). I chose a hardware stack that matches the actual utility of the project. Iterative Buying vs. Over-Committing The Incremental Build: Instead of buying a massive kit of parts all at once and risking e-waste, I opted for an iterative approach. I built the project in stages, ensu