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 some time on prototyping a modular SPA hub that meets the following core requirements: * from users perspective - it all looks like one app (seamless navigation, same looks, shared layout, etc.) * it consists of independently developed (by different people) modules, BUT these modules may use other...
Surprise, surprise - six months have already passed since previous edition [http://thoughtworks.fileburst.com/assets/technology-radar-jan-2014-en.pdf] of Technology Radar. Obviously no-one says it has to be treated as an absolute & accurate snapshot of reality - but if you check the past reports, it clearly visible that they...
Setting your applications may get really messy - especially on Linux: different applications have different configuration approaches, they keep their binaries & data in different file-system locations (these differ because apps may have origins within varying Linux distributions). Once you set things up once, it's pretty hard to...
Quite recently I've spend some time on discussing the development efficiency & how things have changed within last few years: you don't need whole development factory to achieve something meaningful. If you use modern tools & development techniques PLUS you have capable & motivated people you...
When I was working about my last blog post, the one about outsourcing the pain, I've come up with an idea of one, interesting type of pain software developers tend to forget about. Wait, they don't forget about it, they usually intentionally pretend it does not...
Straight to business - I've participated in a very interesting discussion about development architecture recently: which scenario works better & brings more benefit to the organization: 1. each team is responsible for all their deployment / maintenance mechanisms separately (let's call it Scenario A) 2. there'...
