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.
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...
Few days have already passed since the Tesla Powerwall [http://www.teslamotors.com/powerwall] announcement Supposedly the first "wave" of hype has already cooled down & it may be a good time for a personal statement: > I do believe. That this item may truly change the future...
The concept of Microservices, even if a bit ephemeral, gets a lot of love nowadays. Reasons are quite straightforward, so I'm not going through that once again - what bothers me is some kind of misconception / overinterpretation I've already encountered few times. Microservices (MS): * YES, encapsulate service...
The struggle against coupling doesn't just seem eternal. It IS eternal. Multi-dimensionality (compile-time, deploy-time, run-time, ...) of the problem, easiness of breaking the state that was achieved with the great effort, complexity of validation / monitoring (try to quantify coupling in a way that makes sense...
