3 ms·
> "The author is also right about the cause: it's developers always chasing the newest toys." That's certainly true. But undefined and wishy-washy business nee
by chiefalchemist 9y ago
> "The author is also right about the cause: it's developers always chasing the newest toys."
That's certainly true. But undefined and wishy-washy business needs don't help either. It's easy to look at something finished and think "that's not right, that's not what I would have done."
Sure there's negligence or just poor decisions. But often there are good reasons for wonky architecture, and often those reason have little to do with technology and the people who implemented it.
- sidlls 9y agoWhen throughput is a few GB (< 10) of data per day, most of it coming in a large batch that doesn't have any real time requirements for processing and someone starts blathering about Kafka and Event Sourcing that is not a wishy-washy business need, that's unvarnished resume driven development.
- chiefalchemist 9y agoTrue. I think what I'm implying is there is a co-dependency going on. That is, in light of the lack of a clear (biz needs based) path a given team / individual is going to do what they feel is "right." That decision is going to have a natural bias. If for no other reason, people learn that ultimately the only person looking out for them is them (especially when the business isn't even looking out for itself).