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.
Majority of my co-workers and acquaintances associate me (and my professional work) with the .NET stack. This association is so strong that when I tell them about my recent works with Scala/Akka, they think I'm nuts (or close to): > What's the point of learning...
Reactive applications. Scalable & responsive. Resilient & fault-tolerant. Event-driven & asynchronuous. The benefits of RAs are well and commonly known (if you're not up-to-date, make sure you get yourself familiar with Reactive Manifesto: start with the following link [http://www.reactivemanifesto.org/#reactive-applications]), but it's not...
It seems that reading "Peopleware" has made me even more aware allergic to the overall stupidity and brainlessness of typical, iconic (dilbertian?) corporate world. I didn't plan to spend several blog posts on these topics, but it was the sheer reality that has made me to....
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....
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...