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.

  • Debugging a duplicated behavior with GTInspector
    2 February 20169:30:54 am by Tudor Girba
    I have just spent a beautiful 15 minutes tracking a bug down. It was so exciting that afterwards I decided to spend 2 days documenting the experience because I think it offers an elaborate example of how transformative development workflows can be with moldable tools in a live environment. The bug ...
  • Spotting senders and references with GTSpotter
    19 January 20162:41:05 pm by Tudor Girba
    A recent discussion on the Pharo mailing list revealed that people would like to have the possibility of looking for senders of a symbol and references to a class in one step in Spotter. A complementary request was that when we know that we want to search only for senders, we do not want to search f...
  • Spotting Pragma users with GTSpotter
    9 January 201610:41:20 pm by Tudor Girba
    Finding pieces of code that are annotated in a certain way can be challenging in many IDEs. In Pharo, this is fairly straightforward using GTSpotter. For example, how can we find all methods annotated with ? Spawn Spotter, and type menu #pr. This will search for menu and show only the results from...