Being an Internet old-timer has some cons. I miss ol' good times when the word netiquette had some significance. Times have changed and [ ... long, sour rant here ;) ... ]. Nowadays people tend to use some Internet tools mindlessly, without caring how it affects other people work / time. E-mail is a great example.
This blog post is some kind of post-scriptum to something I've written quite recently: http://no-kill-switch.ghost.io/antipattern-attracting-the-work/ Not something completely new, just an additional remark, an important point I think I've missed then, but I find it important enough to shape another, short blog post just about that.
It usually looks like that: Discussion seems fruitful, brainstorming normalizes & catches "the flow", people sync well & come up with a shared conclusion. Verbal statements happen. People nod in ecstasy. Deductions appear. People nod in ecstasy (again). And people diverge with a sense of a job well done ("We
Change is what I do. This is what I get paid for. Usually it's not just "you're at A, get to B" but more like "we think you should be somewhere there, go figure out for yourself, then carve a path towards a better place, but make sure we'll think
Few days ago I've written a blog post about feature teams - I wasn't hiding that it was inspired by C. Larman's book about scaling Agile. Or rather by one of the chapters that I've found very interesting & thought-provoking. There's another excerpt I keep coming back to, because I've
Let's start with some bold statements: Team that did shitty waterfall work will most likely do a shitty agile work too (you can freely substitute the word 'agile' with Lean Six Sigma, CMMI3+, XP or whatever) Nice tools can make a noticeable impact (by improving morale, increasing dev agility, etc.
"Doveryai, no proveryai." ("Trust, but verify.") Ronald Reagan (to Mikhail Gorbachev) Developing an enterprise-level software product is never easy ("thanks, Sherlock!") & clearly doesn't depend on pure programming skills only ("now you tell me?!"). That's why we have all those "processes", "activities", "methodologies", etc. Their shared (& sometimes indirect) purpose
Honestly, I like to speak to a wider audience about cool things we (my team(s)) do. I don't think it's a typical show-off, even if it helps me, my collegues & my employer to strengthen personal or enterprise brand. What I love most is diving into details of solutions
I've always wanted No Kill Switch to be 50% tech + 50% leadership+mgmt blog. But it just doesn't work out like that. I'll tell you a secret - I publish regularly twice a week, which is quite often, but I never struggle with finding a topic for the next blog
Self-governing, self-stating, self-managing, self-organizing TEAM. Combined human potential. Direct interactions & co-operation. Simplifying communication routes. Power to the (team) people. Yay. Yes, that's right, agile approach promotes all the team-related statements listed above. Scrum team, in favorable circumstances, can perform magnificently without any kind of manager support (not mentioning one
The subject of 10x engineers & their existence is back. Again. It's just the nicknames that change: rockstar programmers cowboy programmers 10x engineers Personally I thought that's not much to be said beyond what Scott Hanselman did here almost 1.5 yr ago, but the fire is still burning &
Straight to the point On-line software services are everywhere: I do shopping, check map / route / timetable, order food, communicate, do financial operations, read books / news, watch movies, listen to music, play games - ALL OF THAT thanks to on-line software via Internet. It all looks like sci-fi movies coming to