51–60 of 175 posts
I hope the world realizes that clouds are not just fluffy white things in the blue sky, but can create destructive storms too, with wind, rain and so on. Make sure your infrastructure is ready to weather such storms - have local backups and fallbacks, make sure your code is available even if github (or the Internet) goes down. The more I hear 'cloud', the more I try to depend only on tools that work offline.
If only we had a version control system that didn't rely on a central hub...
Fossil tracks issues (tickets), documentation, and wiki pages at the same level as it tracks code, so when you clone a Fossil repo, everything gets downloaded to your local computer. You can then respond to tickets and perform repo maintenance offline, syncing everything to the server when you're back up.
Edit: A few weeks ago I got a job a one-hour train ride away. I can commit, close tickets, and write docs on my way in, sync everything to the internet when I get to work, then do the same on my way back - even though I don't have a net connection during my commute. It works great. (Ok, not as good as not having to travel at all, but great nonetheless!)
Taking bets on if this is the chinese government testing out GreatCannon v2.0.0