gandolfinmyhead

why is it that big time banks choose the shittiest, most expensive and buggy cms that have equally expensive talent rather than build custom ones based on open source tech (actual open source tech not half assed solutions put on git that no gives a hoot about) for less than half of the price?

A lot of folks are jumping on the AWS train, especially after Netflix partnered up with AWS. people are scrambling to get their AWS dev/sol architect certificates, every board room meeting has yet another Buzzword added to the list to be slapped around, and hence to protect myself from being dragged into projects that may potentially not need the overhead of AWS, what sort of projects don't need to go anywhere the services offered by AWS?

Recently I've gotten interested in Apache Storm, and was reading this article `http://nathanmarz.com/blog/history-of-apache-storm-and-lessons-learned.html, and got stalled at `Before Storm, ... we were very unsatisfied with this approach. It was brittle – we had to make sure the queues and workers all stayed up – and it was very cumbersome to build apps.` Do you folks read such things, accept it and move on, or do you try to recreate it in order to further understand motivations (or consider it a waste of time), or do you build test projects to see it get complex over time and understand the motivation? If you do the latter, do you have any tips for minimizing the effort involved?