For me, it's Randy Johnson's bird hit. A bit morbid, but the just incredible timing and impact is just mind boggling. https://www.youtube.com/watch?v=Ih_ovjbwQGk
57 karma · joined January 11, 2013
yeah.....only if you didn't write shitty code, have 5 layers of "oh, lets use XYZ feature and service!".
Not hating, just pointing out this cannot be universally true. You're lucky because you wrote a reasonable service. Many are not.
I'm not saying we should stop that, by any means, precisely the opposite actually, however what we DO need to do is be more focused on actually building sustainable products and services, that generate (gasp) REVENUE/PROFIT, and learn to "Fail Fast" when it becomes a drag.
In many cases you have a "handshake and your word is your honor" system in place that drives business forward. No one is stressing about much, beyond the weather, and they have a more peaceful perspective on life in general.
That CERTAINLY has room for some technological improvement, but would have to be done in a very careful, well thought out and implemented way. Case in point, if it quits working or requires data fulltime (try getting data/cell/internet on a 10,000 acre farm in the middle of nowhere), then you will fail because even if you CAN convince a large portion of farmers to adopt the tech, once they start having enough problems with it? Out it goes, back to paper, phone calls, and a handshake.
Go compare keyboard shortcuts between all these services and you'll quickly change your mind.
I want to be able to just drop in some arbitrary command (e.g. df -h /some/build/agent/dir/ | grep 99%) that would not be worth it to me to write a script, commit it to git, get that deployed and running.
In fact, I AM a fan of this being in git, but the example I'd use is an improvement on TeamCity, where you can configure your job and project configurations to "commit to git" so that you can easily restore when you need to rebuild a server or reload a previous version.
Sooooo many use cases for arbitrary jobs. Many of which may be short lived, but want them automated in some way.
(speaking as a sysadmin/eng/devops/cloud dude)
Correct me if I'm wrong, but isn't slack a closed ecosystem, akin to Skype?
The big difference with RDS is that you don't get the full gambit of clustering capabilities that SQL server supports. This is mainly due to the fact they don't have a shared storage model that SQL cluster failover requires.