in: Optimized May 2009
Make sure that the quality of every part meets certain minimum requirements, or some local problems will bring you down globally.
in: Optimized November 2008
IT pro’s are famous for their social ignorance. For me, that is true to a fairly degree, but I should not speak for my colleagues. But is anyone really interested in the human side of the IT-pro after all?
in: Agile Holland website October 2008
Gert Poppe illustrated organizational improvisation by comparing it to improvisation that jazz musicians engage in. After the presentation I asked him if he was aware that Henry Mintzberg wrote an interesting article on this subject. Gert didn't. Good for him because, I far as I know ;-) Mintzberg didn't. Karl Weick did …
in: Optimized April 2008
The title reminds us of the fact that yesterday doesn’t matter anymore today, and that today doesn’t matter anymore tomorrow. It’s generic zero-based budgetting: only look at future costs by zeroing out the present and the past. Because tomorrow does matter today.
in: Optimized September 2007
Things become a commodity when they are no longer “art”. As long as you’re seen as an artist, you don’t have to worry about prodcutivity. But as soon what you make becomes common, you loose prestige, and the consumer becomes frugal. In that situation, productivity is a prerequisite for succes.
in: Optimized March 2007
“a state of complete physical, mental and social well-being and not merely the absence of disease or infirmity.” For IT: hardware, software and interfaces that are not merely free from defects, but are in good condition. No systems that just run, but systems able to do the marathon within two hours and a half!
in: Optimized October 2006
One common European payment area. Will that make payments cheaper than the institutions and systems that run our payments nowadays? All replication can be undone. That’s a gain. But it will not be a free lunch. As usually every advantage has its downside.
in: scriptie June 2002
Being aware of the existence of and knowledge about the operation and effect of evolutionary processes on all levels can clarify the perspective on the world of the researcher, the advisor and the manager, for, although rarely the only explanation, it almost always explains a part of it.
in: Informatie December 2000
Too much confidence in a model leads to selective perception: you don’t see what does not fit the model.
in: informatie October 2000
Testing is not something that simply follows building. The systems are so complex that during design attention must be given to the fact that testing is a part of the process.
in: informatie October 2000
‘No one has yet proved himself wise enough to propound a universal system of constructs. (…) For the time being we shall have to contend ourselves with a series of miniature systems, each with its own realm or limited range of convenience.’
in: informatie September 2000
Causal model play a central role in charting norms and values, problems and solutions, goals and actions realizing those goals.
in: informatie September 2000
A component is a part of a larger whole. A service is an action, performed when requested. The meaning of this words depends on the context in which they are used. When the context is not clear, the meaning isn’t either, resulting is misunderstanding.
in: informatie July 2000
In that area between ice and water something special happens: to change zero degrees ice in zero degrees water an extra 300 joule is needed per gram.
in: informatie June 2000
A core quadrant describes core quality, pitfall, challenge and allergy in their mutual relationship.
in: informatie May 2000
IT-departments don' have a choice between opportunistic or systematic. They must choose for which projects a systematic and for which projects a opportunistic approach is best suited.
in: informatie April 2000
The formula satisfaction = result x expectation contains two variables we can use to influence satisfaction: next to result also expectation.
in: informatie March 2000
…that it is better to learn to deal with fuzzy situations that waisting energy in denying them.
in: informatie January 2000
not developing the functionality that is not used after all, would save a lot of development time.
in: informatie December 1999
Architecure is a subject worth mentioning in this context: much so-called architecture-wisdom has the character of Murphy's Law and the Peter Principle.
in: informatie November 1999
The motivation of employees and the motivation of end-users seems to be alike where it come to satisfiers and dissatisfiers. The already mentioned infrastructure is never a reason for applause. And just as bad coffee does, problems with the infrastructure result in high scores on dissatisfaction.
in: informatie October 1999
Why do we react the way we do? Because we see what we see, and we think about that in the way we think about that.
in: informatie September 1999
… concepts should only be defined to a certain extent. Everybody who has participated in useless discussions in which people tried to define essential differnces, black against white, in a world that only knows varaitions of gray, will recognize The ‘to a certain extent’.
in: informatie July 1999
The analogy does not imply that systems become more chaotic over time, but that it takes energy to prevent his.
in: informatie June 1999
Every solution introduces its own, new problems. And like the total amount of energy in a closed system, the total amount of problems does not change.
in: Informatie May 1999
Toulmin built a framework for the qualitative judgement of reasoning and argumentation on a level that is independent of the field in which the assertion is made. This model is valuable for IT too: the quality of our reasoning and arguments are links in the chain that determines the quality of our products and their acceptance.
in: Informatie April 1999
[...] it is impossible for a theory of social behaviour to be simultaneously general, accurate, and simple. At least, that is what Thorngate postulated (1976). According to Thorngate the social scientist faces the dilemma that choosing two properties leaves the third one out of range.
in: informatie March 1999
In their book ‘AntiPatterns’, Brown c.s. describe tens of these ‘constructions to be avoided’, grouped by three perspectives on software development: the developer’s, architect’s and the manager’s. It’s a book with a clear message: it can be done better, and it should be done better.