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 enjoyed Ben Horowitz'es books. Both of them. Far more than his interviews/lectures on-line, even if I find some of the references he makes (especially hip-hop ones) annoying. But in the end: he's a brilliant guy with incredible experience plus he knows how...
I'm sure you know how deadlines work: 1. collect the requirements/expectations & grok through them (understand them) 2. estimate the effort needed to deliver the outcome, quantify risks, "guesstimate" unknown unknowns, ... 3. ... and "collide" what you've got with current commitments &...
Disclaimer: I'm not a psychotherapist. This whole post is based on my individual observations & experiences - these may apply to you, but also may not. Don't blame me, but if you find these scribblings relevant, toss me a +1. I'm not going to...
> "Conversion, software version 7.0 Looking at life through the eyes of a tired hub Eating seeds as a pastime activity The toxicity of our city, our city" "Toxicity" - System Of A Down I've already written a similar post some time ago...
There are so many myths about software architecture ... * that it's done once and there's no further cost associated * that if you do it properly, it will serve forever * that there's "the correct way to do it" & you measure correctness with "...
Quite recently I've shared my personal interpretation of "seniority" in tech (based on the concept of "leverage" - shamelessly stolen from Andy Grove ...). This term ("seniority") is frequently closely associated (as an enabler) to the role of an "architect" -...
