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.

  • Boosting GTSpotter with preview capabilities
    2 February 20157:50:38 pm by Tudor Girba
    GTSpotter is a novel search interface for spotting objects that we introduced a short while ago. It is part of the Glamorous Toolkit and it is now also available by default in the latest Pharo 4.0. You trigger it with Shift+Enter and you search. For example, GTSpotter allows you to search through t...
  • Improving the print-it support in GTPlayground
    17 January 201510:50:02 pm by Tudor Girba
    Print it is one of the actions that exists since ancient times in Smalltalk environments. A while ago, we enhanced the GTPlayground with a Print It action that does not affect the existing code. Unlike in the classic behavior in which the printout gets inserted in the code editor, the improved versi...
  • Identifying a configuration problem with GTInspector
    4 January 201512:48:29 pm by Tudor Girba
    When releasing the latest version of the Glamorous Toolkit we noticed a little problem: while in Pharo 4.0 the code worked just fine, in Pharo 3.0 we got a problem due to a reference to a class that exists only in Pharo 4.0. The problem came from the GlamourCore project, but I could not exactly see ...