Decide knowingly

Humane assessment is the method for making software engineering decisions. It helps your team take into account the reality surrounding your system.

Everyone makes decisions

The goal of assessment is decision making. Managers decide the strategy. Architects decide the technical direction. Developers decide the implementation. Daily.

Decisions require accurate information

Effective decision making requires accurate information. But, software systems are large. Thus, manual inspection does not scale. You need analysis tools.

Details are essential

Software systems are complicated in specific ways. The system details are essential for your decisions. You need custom tools that provide the information that matters. Craft them.

Assessment is a human activity

Analysis tools are important to handle the scale of problems, but in the end, assessment is a human activity. Regardless of how smart the tools are, it is still the human that has to infer the relevant information and transform it into action.

Approach problems individually

Not all problems are created equal. Some are of continuous concern. They deserve daily attention. Some only appear once. These require different approaches. Learn their particularities. Deal with them individually.

Why a method?

Decisions are made everyday. It's just that the effort is implicit and unoptimised. Assessment must become explicit and made integral part of the overall process. You need to approach it systematically. You need a method.

  • The emergent nature of software systems (slideshow)
    28 June 201511:14 am by Tudor Girba
    This slideshow offers a visual argument, based on the System Attraction visualization, of how software systems have emergent structures. This slideshow strengthens the argument I made previously that the evolution of software architecture is a complex game, and it offers the motivation for why t...
  • Moose 5.1
    4 June 20158:37:21 am by Tudor Girba
    We are happy to announce version 5.1 of the Moose Suite: Screenshot.png Description This is a minor release. The key highlights are: * It is based on Pharo 4.0. * Roassal2 comes with several new builder, most notably the new Mondrian builder (RTMondrian) and...
  • Guiding a rename effort with GTInspector
    17 May 20154:09:41 pm by Tudor Girba
    After a debate on the Pharo mailing list, we ended up choosing to rename all variations of the example* pragmas to gtExample*. Furthermore, as a second step, we also wanted all methods annotated with gtExample* to start with an example prefix because this would not conflict with the behavior from th...