aalbertson

Being not hosted on my same tech is one thing, still being self hosted so I can externalize it for a federal implementation is another. Definitely needs to be self hosted for ALL components. :)

Lowes search was also down.

you know, this explains why I have lost a couple domains in the past. What a shady shitty thing to do.

speaking of bug fixes, might check the spelling of your "The Service" button. ;)

you won't need a load balancer... it will just serve infinite scale (effectively) as they take care of that automatically.

`Oh, and that small server you’re worried about? You’ll be fine.`

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.

Ramdisk maybe?

That may be one of the biggest annoyances of "Agile Methodologies". It's this idea that we can just keep micro-incrementing anything forever. While the principle works great, you end up with this model where you never actually stop/complete/etc...

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.

Elon Musk != Donald Trump. When he makes statements/estimations, even if they prove significantly conservative, they are truly grounded in verifiable facts.

Coming from the Farm culture/environment growing up, I can support this idea that it is in part the "non-corporate" aspect. It's very very much the personal, non-technological, Stay out of my business, get off my lawn, view points and feelings that drive some of this.

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.

Need a new standard...

...and keyboard shortcuts....don't forget about those!

All I can say is....L.O.L....

Go compare keyboard shortcuts between all these services and you'll quickly change your mind.

no, it does not fit the bill. It needs truly arbitrary job running.

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)