Design

One assert per test?

Should we have a single assert per test? Are custom asserts useful? What about diagnostic messages? And how to structure our tests? Maybe we should have tests mixed with production code? Alex answers all these questions, prompted by a conversation on Twitter started by Mattias Verraes https://twitter.com/mathiasverraes/status/1752236595091054671.

One assert per test? Read More »

Object-First Design

Structurally, objects are nothing more than a set of partially applied, cohesive functions. And thinking in objects should (perhaps) not start with writing the “class” keyword. In this video, Alex is offering an alternate perspective to the common “class-oriented development” used in many of the modern programming languages. This perspective is not meant to be

Object-First Design Read More »

Google Technical Debt approach vs. Usable Software Design

In a recent paper, a Google research team details how they empirically determined the types of technical debt and ways to manage it inside the organization. The ideas in the paper bear a very close resemblance with Usable Software Design, in that the engineers are interviewed about the challenges they face with the design and

Google Technical Debt approach vs. Usable Software Design Read More »

Fitness and Workout for Software Architecture Talk

Most of the attention in software architecture is given to new styles (eg. microservices, serverless) or technology changes. Too little attention is given to the process of creating, evolving, and maintaining the architectural models and decisions. Yet this process is immensely valuable since with the right process you can adopt innumerable architectural styles and adapt

Fitness and Workout for Software Architecture Talk Read More »

0
    0
    Your Cart
    Your cart is empty
      Apply Coupon
      Available Coupons
      individualcspo102022 Get 87.00 off
      Unavailable Coupons
      aniscppeurope2022 Get 20.00 off
      Scroll to Top