> TL;DR Knowledge is power - you can't foresee & script creative way of knowledge workers if you really expect valuable outcomes. The only way is (once you get proper people first) to provide them necessary degree of freedom & contextual knowledge - up-to-date, comprehensible, applicable, broad...
> TL;DR Too many problems in modern software solutions development are related to chasm between 'thinkers' (analysts, people with business knowledge) & 'doers' (IT specialists, mainly programmers), yet we're so used to it we treat it as something carved in stone. Why not...
> TL;DR If maintainability & extensibility of your software are among the top priorities, readibility & easy-to-grasp correspondence to functional requirements are far more important than conciseness & technical "aesthetics" (e.g. compliance with patterns) of your code. That's why to build good solutions we...
> TL;DR The older I get, the less patience I have - that applies to people as well, but (fortunately) I keep it healthy -> what irritates me is not someone's lack of knowledge or mistakes made, but rather immature or non-constructive follow-up. What is really...
> TL;DR I've asked myself a question - what has made Leonardo da Vinci so exquisite that his fame lasts for half a millenium already - answer (based on biography & known facts) doesn't differ much from what depicts best software (& not only) engineers...
> TL;DR Many IT people (mainly executives & various managers) are guilty of building the walls between business and engineering parts of organisation: by introducing gated demand management, communication via specification, cooperation through proxy people and siloeing the competences they hope to achieve more order & control, additionally reducing...
