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.
This blog post is about Enterprises whose core business is NOT IT, but they consider IT services as an important part of their everyday operations. Large Enterprises in 2015 (at least in Europe) are pretty from what we remember from 2000, 2005, 2010. There are still some dinosaurs & they&...
Few days ago I've run into this article on InfoQ: http://www.infoq.com/news/2015/05/ioda-architecture I found it amusing enough to dive deeper here (link taken from the article): http://geekswithblogs.net/theArchitectsNapkin/archive/2015/04/29/the-ioda-architecture.aspx I won't keep you...
This blog post is some kind of post-scriptum to something I've written quite recently: GHOST_URL/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...
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: > 1. "WTF?! I have to work with this legacy code, instead of creating something completely new?" 2. "WTF?! How can...
It usually looks like that: 1. 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...
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...
