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.

  • & GTInspector trailer
    15 August 20141:34:18 pm by Tudor Girba
    As part of the submission for the ESUG 2014 Innovation Awards, we launched a webpage dedicated to the Glamorous Toolkit for Pharo at And, to make it more exciting, we put together a trailer to exhibit the power of the inspector and the playground.
  • My NDC 2014 talk on Pharo: Playing with Live Objects is now available (video)
    13 August 20147:11:55 pm by Tudor Girba
    The talk I gave at NDC on "Pharo: Playing with Live Objects" is now publicly available. On the one hand, the talk shows how programming with Pharo can be both serious and fun at the same time. On the other hand, the talk exhibits the liveliness of Pharo through demos of the GTInspector.
  • Rethinking compilation notifications in Pharo
    3 August 20149:57:48 pm by Tudor Girba
    Recently, we rethought the Print It action in Pharo. On that occasion, we replaced the text inlining with a popper that leaves the initial text editor untouched. Another behavior that lends itself to a popper treatment is the notification of compilation errors. Suppose that we have a case like th...