Have you ever met a Bottleneck Superhero (BS)? I guess you can't tell as the term doesn't tell you anything. No surprise as I've just coined it for the sake of this blog post :> Yes, people who know me in person do know how I like naming things (or people) ;)
Hero of the (every) day
Ok, let's start with the description of such a
Once in a while I try to catch up on some classics I've somehow omitted to read. One of them is (was) Lencioni's "The Five Dysfunctions of a Team". Title may cause setting some wrong expectations, subtitle is crucial here - "A Leadership Fable". Why so? It's written from executive's perspective & its intended audience is mainly executives (of various levels). Don't flee just
I've recently read Lencioni's Five Dysfunctions of a Team - widely recognized classic on leadership & executive management. I'm not going for a full review here (you can easily find my review on Goodreads), but I want to refer to one of book's key output thoughts (paraphrased for the sake of brevity):
Conflict in a team (or any other kind of collaborating group) is
This blog post is some sort of a supplement to my previous post on building teams organically - you can find it here.
As we all know, software developer job market is terribly twisted by huge disproportion between demand (crazy) & supply (barely dripping). Huge gap between these two has resulted in uncontrolled boom of a particular trend I find strongly harmful: developer "body-leasing"
Have you heard about groupthink before? If you didn't, this blog post is for you - better to know such vicious enemy before you actually encounter him ... The most clear (& still concise) definition I've found goes like that:
"Groupthink occurs when a group values harmony and coherence over accurate analysis and critical evaluation. It causes individual members of the group to unquestioningly follow
It usually looks like this: there's already a decision about new product / project, people are extremely happy & eager to start straight away, silently expecting to "do it all perfectly" this time, avoiding all the mistakes from the past. But before they get into actual work, there's the sweetest & the most pleasant work to be done ... Visiting the armoury to pick the optimal
The way people tend to twist the idea of self-organization & bottom-up team empowerment is both scary & fascinating in the same time. But the amusing part fades away quite quickly when you realize all the inefficiency & impotency that happen as a side effect. One of the most common (& most fatal ...) anti-patterns is known as design by committee.
I guess everyone has
Have you heard about The Iron Law of Oligarchy (TILoO)? No? There's no shame, I haven't (until recently) either, but now since I did, I have some remarks hopefully worth sharing.
OK, but first - what's the TILoO about? Here's the briefest version:
Rule by an elite, or oligarchy, is inevitable as an "iron law" within any democratic organization as part of the "tactical
The term HiPPO (Highest Paid Person's Opinion) is getting quite popular in project management world (& IT in particular) recently. What's the fuss about? When there's a decision to be taken & various options are discussed, people tend to lean towards the opinion stated by the Highest Paid Person present. Why? Because ...
- ... this is usually their superior
I was chosen by Heaven.
Say my name when you pray.
To the sky! See Carolus rise.
No man alive or dead commands me, I answer to the Lord!
Hear my orders, question me and die.
What I say was set in Heaven, and so it shall be done!
Sabaton "Carolus Rex"
Anointed by the gods
We have a huge problem with leadership in
Another conference (Confitura 2015), another boost of positive energy, inspiring ideas, sense of belonging to dynamic & developing community. I'll skip the usual session reviewing part this time, I'll focus on a very selective list of personal remarks instead:
Confitura's supposed to be a free conference: that's how its Orgs want it. But being a free Java conference held in a capital
There are important thinking barriers to cross (break?) in a professional career of a software engineer. They are marked with some sort of epiphanies, for instance:
- "WTF?! I have to work with this legacy code, instead of creating something completely new?"
- "WTF?! How can I troubleshoot that if I don't have access to production DB?"
- "WTF?! I've just wanted to swap lib A for