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.
> "Deadline." > "Commitment to the fixed scope." > "Requirements specification." Those three statements have made my flesh creep, did you get the same sensation? They are definitive, they are scrict, there are about formal responsibility & discipline. And they are the essence of...
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,...
The idea of decomposing application into layers (logical vertical split) or tiers (physical vertical split) isn't new - it's bread'n'butter of systems architecture. Reasons for such a split are still the same (as they were in 90s, 80s & beyond): * to reduce...
The prose of life Test automation ain't trivial & there are several reasons for that, including: * need for scalable structure (hierarchy, naming, etc.) * dealing with dependencies (coupling) * insufficient speed of execution affecting dev agility * shared resources impairing isolation * inertia of data (incl. configuration, parameterization, etc.) But there are...
There's one thing that freaks me about agile adoption in large enterprises. WAIT. NO. There's one thing that particularly freaks me about agile adoption in large enterprises: Full conviction that it can be done only in a top-down way It has to be a shift in...
I can't recall precisely when I've heard about Conway's Law [http://en.wikipedia.org/wiki/Conway%27s_law] for the first time - most likely because it has left me unimpressed. > "Organizations which design systems ... are constrained to produce designs which are...
