Decide knowingly

Humane assessment is the method for making software engineering decisions. It can be used for steering agile architecture, for guiding migrations, or for splitting monolithic applications.

Join a Steering Agile Architecture course
Next one is in Hamburg, Germany on July 7-8

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 code reading 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.

Recent blog posts

  • An informal experiment about not reading code
    14 June 20162:44:57 pm by Tudor Girba
    Over the past year, I conducted an informal study on how developers think about code reading. The study took the form of a dialogue that I have with software engineers. I had it in various forms with more than 1000 engineers. The dialog goes like this: Me: I help teams to not read code. Engineer: ...
  • Discovering and managing GTSpotter extensions
    5 June 20168:13:57 am by Tudor Girba
    GTSpotter is moldable. The default Pharo 5.0 image comes out-of-the-box with 122 distinct types of search processors. Understanding and controlling these processors is key for using Spotter to its full extent. The first thing about it is to learn what these extensions mean. Each of these extensions...
  • The impact of moldability
    4 June 20166:16:56 pm by Tudor Girba
    We say that Glamorous Toolkit (GT) is a moldable development environment. There were a couple of emails on the Pharo mailing list in the recent period that questioned the usefulness of moldability. More specifically, the questions were raised in relation to the newly introduced GTDebugger. The conce...
  • Communicating Pharo 5.0
    16 May 20169:00:15 am by Tudor Girba
    Pharo 5.0 is out. This was a great ride. As it has become customary, I worked on capturing one aspect of the work around Pharo 5.0 in a visualization. Choosing only one prominent aspect was not easy this time. For example, the VM just got 30% faster. Just like that. And there is a new moldable debu...
  • Pharo 5.0
    13 May 20166:39:39 pm by Tudor Girba
    Dear World, The time has come for Pharo 5.0! Pharo50-screenshot.png Pharo 5.0 is our most significant release yet. Here are some highlights: * The PharoVM is now based on Spur, the new memory management, and it brings with it a 35% speedup! * A new unified foreign function interface (UFFI) rep...