Skip to content
ExponaBLOG
Series · Day 100 of 100

Engineering Craft

  1. 51
    Write a design doc before big builds in Engineering Craft
    An hour of writing saves weeks of rework.
  2. 52
    Estimating software work honestly: a step-by-step guide
    Late projects are often honest estimates ignored.
  3. 53
    Handling scope creep without conflict: a practical guide
    Saying no is part of delivering.
  4. 54
    Agile practices that actually help: a step-by-step guide
    What worked across three projects I led.
  5. 55
    Standups that don't waste time: best practices explained
    Fifteen minutes, focused on blockers.
  6. 56
    From senior engineer to tech lead: a step-by-step guide
    What changed when I stepped into leadership.
  7. 57
    What 'senior' actually means: what developers should know
    It was never about years of experience.
  8. 58
    Mentoring junior developers: what developers should know
    How I help juniors grow faster.
  9. 59
    Feedback that lands: a practical Engineering Craft guide
    Specific, timely and kind.
  10. 60
    Running technical interviews: what developers should know
    Interviews that predict real job performance.
  11. 61
    Signals I look for when hiring: best practices explained
    Beyond 'can they code'.
  12. 62
    Onboarding a developer in one week: a step-by-step guide
    A plan that gets new teammates shipping fast.
  13. 63
    A README that onboards: a practical guide for developers
    New developers productive in ten minutes.
  14. 64
    Talking tech with non-technical stakeholders in practice
    A leadership skill nobody puts in the job description.
  15. 65
    Translate tech debt into business impact for production
    'Refactor' doesn't get budget. 'Faster releases' does.
  16. 66
    Production releases as a tech lead: a step-by-step guide
    How I keep deployments boring.
  17. 67
    A post-release monitoring checklist in Engineering Craft
    The first hour after a deploy matters most.
  18. 68
    Security fundamentals every engineer needs: a deep dive
    Lessons from my cybersecurity master's and real projects.
  19. 69
    Threat modeling in 30 minutes: best practices explained
    Find security issues before writing code.
  20. 70
    Sessions vs JWT: an honest comparison, explained simply
    Neither is modern or legacy. They are different trade-offs.
  21. 71
    Least privilege everywhere: patterns, pitfalls and fixes
    Give every user, service and key only what it needs.
  22. 72
    OWASP API Security risks for developers, explained simply
    The API vulnerabilities I check for in every review.
  23. 73
    Check ownership on every request: lessons from production
    The most common API vulnerability is the simplest.
  24. 74
    Designing multi-gateway payments: lessons from production
    Lessons from integrating several payment gateways.
  25. 75
    Reconciliation jobs catch silent failures for production
    Money mismatches hide until someone checks.
  26. 76
    Integrating third-party APIs safely in Engineering Craft
    Lessons from Amadeus, Twilio and Meta integrations.
  27. 77
    Wrap every vendor SDK: a practical guide for developers
    Your business logic shouldn't import vendor code.
  28. 78
    Building a personalization engine: a step-by-step guide
    What I learned building personalization for a global retailer.
  29. 79
    Rule engines for non-engineers: best practices explained
    Give business users power without breaking production.
  30. 80
    Email systems that scale: a hands-on guide for engineers
    Lessons from building a personalized email service.
  31. 81
    Transactional vs marketing email: lessons from production
    Different purposes, different infrastructure.
  32. 82
    Lessons from building a trading platform for production
    Real-time data and precision under pressure.
  33. 83
    Precision math in finance apps: best practices explained
    Floating point and money don't mix.
  34. 84
    A performance optimization method: a step-by-step guide
    Measure, fix the bottleneck, verify — repeat.
  35. 85
    Profile before you optimize: what developers should know
    Intuition about performance is usually wrong.
  36. 86
    What building four side products taught me: a deep dive
    Lessons from SEOlenz, Expona, QRzeo and Giftcey.
  37. 87
    A tunnel platform taught me networking, explained simply
    Building an ngrok alternative was a crash course in infrastructure.
  38. 88
    How I learn a new stack fast: what developers should know
    My repeatable process from .NET to Go to Flutter.
  39. 89
    Mistakes I made as a junior developer: a practical guide
    So you can skip a few.
  40. 90
    Using AI in the engineering workflow in Engineering Craft
    How I use AI assistants without lowering quality.
  41. 91
    Adding LLM features to products: lessons from production
    AI features are product features — with new failure modes.
  42. 92
    Documentation people actually read: a step-by-step guide
    Docs are a product for your team.
  43. 93
    Why I document everything: practical tips and trade-offs
    My memory is bad. My docs are not.
  44. 94
    Practices for remote and hybrid teams: a practical guide
    What keeps distributed teams aligned.
  45. 95
    Sustainable pace beats heroics: best practices explained
    Burnout is a delivery risk.
  46. 96
    Growing your career by building in public for production
    The habit that brought me opportunities.
  47. 97
    How I prepare for senior interviews in Engineering Craft
    A system, not a cram session.
  48. 98
    Choosing technology: a decision framework for production
    How I pick tools for a new project.
  49. 99
    Boring technology wins: a practical guide for developers
    Proven tools let you spend innovation on the product.
  50. 100
    100 days of engineering craft: lessons, explained simply
    Wrapping up the series — and what's next.