4,086 karma · joined May 17, 2012
These have been quite big developer heavy companies. If companies like these don't think they can motivate the cost for Slack, I wonder if there are any than can.
Now that agile practitioners have learned that requirements and upfront design actually is helpful, the only difference seems to be that the loops are tighter. That might not have been possible earlier without proper version control, without automated tests, and the software being delivered on solid media. A tight feedback loop is harder when someone has to travel to your customer and sit down at their machines to do any updates.
So we went full circle, again.
Why would it foster an unhealthy relationship with food to learn that some things are unhealthy and eaten only at special occasions? An unhealthy relationship with food would rather be to think that you can eat sweets whenever you feel for it.
Energy drinks, vapes and snus might be popular among teenagers, but has there ever been a time when you have been able to control what teenagers do to any higher degree.
This kind of discussion is a bit off topic here, but I think it is important to remind people that the idea that private always is better than public is ideological dogma, not science. But your latest comment makes me believe you agree with that.
I’m certain some have used those ideas, but that is not what the philosophy itself is based on.
And to be fair, some crud work is repetitive enough so it should be possible to get a fair measure of at least the difference in speed between developers.
But that building simple crud services with rest interfaces takes as much time as it does is a failure of the tools we use.
There’s no reason to involve our knowledge of the system. Entropy is a measure of the number of possible micro states for a given system, and that number exists independently of us.
That doesn't sound like microservices at all, but a distributed monolith.
I'm so sorry!