Although 'Geek' defines some identity for a developer, being geek doesn't sound proundly for me. One having accepted this identity delimits oneself at the same time.
When you think you are Geek also create responsibility related to being Geek. Then it is easy to say: I am Geek, expecting an excellent requirements to start working or I don't wanna talk to stakeholders, this analyst's job, I am Geek or something else.
I've seen many IT-related conferences speeches. My observation is lots of speakers builds their authority around of being Geek. They leverage IT-business cooperation problems, present business-IT relationships with distorting mirror and think it's funny. Well, that is funny for geeks, but not for agilist.
Differentiating from 'Others' is a very powerful strategy for a speaker or for an individual in general. This strategy underlines what a group of individuals have in common and how they differ from 'Others' (read: business), helps to feel more self-confident. But this strategy doesn't help to be more open to a relationship with 'Others'.
So don't be Geek, but Agilist :)
agile (41) anti-patterns (17) architecture (33) books (10) buissness analysis (1) cases (1) code speaks 2u (3) communication (1) conferences (13) consulting (1) conversation patterns (26) customer collaboration (14) ddd (5) design patterns (15) desing (1) dialogi (1) dsl (2) effectiveness (19) embedded (1) events (22) gtp (4) info (2) infoq (5) kanban (2) lean (2) master (1) measuring (1) orm (2) pea (2) product humanisation (1) refactoring (13) requirements (7) retrospections (1) retrospective (1) scrum (9) scrumguide (1) sm (1) soft skills (4) software craftsmanship (14) tdd (1) team (20) time management (3) tutorial (1) uml (1) user stories (1) visions (28)