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.

  • Rethinking the Print It action in Pharo
    28 July 20141:19:42 am by Tudor Girba
    In Smalltalk, "Print it" denotes the action of obtaining the textual representation of an object. It’s a great feature that can be used from any code editor to obtain a quick feedback. The way it works goes like this. You select the text, then invoke print it (in Pharo, it works through Cmd+p), and...
  • Managing Morphic keybindings with GTInspector
    20 July 201411:52:55 pm by Tudor Girba
    Pharo offers a Keymapping framework (developed originally by Guillermo Polito for managing keybindings throughout the Morphic interface. For example, defining an action bound to a keybinding is as elegant as: Morph new bindKeyCombination: $, command toAction: [ self inform: 'Action!' ]; ...
  • Beacon: a slim announcement-based logging engine for Pharo
    15 June 20142:48:14 pm by Tudor Girba
    Logging is a pervasive analysis tool, but most logging systems focus on text. There is a historical reason for this, but we can certainly do better in this century. Particularly in Pharo, where everything is an object, it should follow that logs should be made of objects and that scrolling endlessly...