Managing Complexity

Design is always about trade-offs, and good design is often about eliminating unnecessary complexity from our ideas. As we finish our test-double-free code, we look at the tradeoffs. Is our Null Socket.IO-based design less complex than using conditionals? Is it less complex than using a test double? With everything working and clean, we take stock of our solution.

  1. E456An Alternative to Test Doubles

    Wed, 19 Oct ’16
  2. E457A Null Connection

    Mon, 24 Oct ’16
  3. E458State in the Union

    Wed, 26 Oct ’16
  4. E459Re-Port-ing

    Mon, 31 Oct ’16
  5. E460getLastSentPointerLocation()

    Wed, 2 Nov ’16
  6. E461Trigger the Network Event

    Mon, 7 Nov ’16
  7. E462No More Test Double

    Wed, 9 Nov ’16
  8. E463Null Socket

    Mon, 14 Nov ’16
  9. E464Managing Complexity

    Wed, 16 Nov ’16
  10. E465Testing Concurrency

    Mon, 21 Nov ’16
  11. E466Event Handling

    Wed, 23 Nov ’16
  12. E467Test the Null

    Mon, 28 Nov ’16