Since today, I'd like to make some sort of a change in blog posts published here. New ones are supposed to be shorter (max 400 words), more focused on a single thought, even if it means not covering my full opinion on a given topic. You can also expect more open questions left w/o answer. So much when it comes to plans, we'll
"Errare humanum est, sed in errare perseverare diabolicum."
(eng. To err is human, but to persist in error (out of pride) is diabolical.)
Now & then I re-visit my own idea / statement / opinion to find out that I totally disagree with it today. Actually I don't find it a problem, quite the contrary - only fools keep upholding stubbornly once formulated statement, regardless
This blog post has been inspired by the following article: Where the hell are all the great senioer software developers and hands-on engineering directors.
"You talk like a developer"
Let's start with a short story:
New dev comes to me as he's told I can help with a problem he has. After 5 minutes of conversation, we've got issue solved. He can't withstand &
Our industry is batshit crazy. No point in denying. What we do (services based on pieces of software) is so multi-dimensional that sometimes it's damn hard to find a common denominator between two: people, projects, products, architectures, methods. Obviously, it's got its pros (let's leave them for another story ...), but there are serious cons as well - one of them is related to job
Unfortunately, some still think that they can treat software engineering as any other type of work. Maybe it’s convenient, but it just doesn’t work. Here’s are two quotes I’ve overheard during just last week … :
"Scrum is awesome, it works really well if applied properly. And what’s even better, you can apply it wherever