Geek, agilista, blogger, codefella, serial reader. In the daylight - I navigate & lead software engineering. #lean #design #aws #elixir #analytics. I speak here for myself only.
I've spend last few days on some activities that were not necessarily related directly to software development: * I was taking part in organizing Technology Architecture workshop (including Call for Papers phase) * I was setting up some local knowledge exchange sessions for enthusiasts * I was trying to trigger an...
It's kinda embarassing, but I've just recently read Tom DeMarco's & Tim Lister's "Peopleware" - the book I believe I (and everyone else, who's involved in working with other people on software development) should have read yeaaars ago. Anyway,...
All the considerations below are based on DevOps <-> Dev scenario, but IMHO vast majority of them applies well to any supplier <-> buyer scenario. DevOps' reality is somehow simple: * they work for other developers (their "clients") * their goal is to make other developers focus...
My #confspree continues - this time I've invaded Budapest to participate (as a crowd fodder) in Craft [http://craft-conf.com/2014/about.html] - two-day long conference about software craftsmanship (surprise! surprise!). It was the first edition of Craft, so there was a chance that the whole thing...
Last few weeks have been quite busy for me and my gang of Merry Men. We're doing a lean project of development architecture refreshment for a large enterprise and we're not wasting time - we aim to deliver the changes as quickly & frequently as possible (even...
This is part III of coupling consideration topic. If you want to check my past coupling-related posts, you can find them here: * Part I [http://gebski.tumblr.com/post/76150235763/the-silent-assassin-that-knows-no-mercy-how] - the theory of coupling * Part II [http://gebski.tumblr.com/post/...