HN user

bak3y

86 karma
Posts0
Comments38
View on HN
No posts found.
DARPA's new X-76 5 months ago

There's no magic wand fix to healthcare, it and the related insurance industry are incredibly busted.

What I am dead certain of though is that involving the government in it will be worse, not better.

DARPA’s new X-76 5 months ago

hopefully we never will - the last thing I want the government MORE involved in is healthcare

As a former sysadmin who had part of his career in that paradigm, I never again want to wait until 10:30 PM to run manual production deployments handed to me by a developer and hoping their documentation was correct.

Give me CI/CD pipelines deploying containers to a k8s cluster during the day.

Just coming back around to this, we also used Splunk consultants for their SIEM solution and the first one we got wasn't very good, but the second was amazing (I wish we could have hired her directly).

The guy we had help us tune our clusters after I rebuilt them all was also very good. Fortunately I'd done most everything by the books and we overkilled the nodes with hardware (we had some older hypervisor nodes lying around I stole for Splunk).

And you're glossing over the pain points that drove the industry to coin DevOps - those times when the zip didn't contain everything it needed to run in production properly and the admin guy had to call the dev multiple times in the middle of the night because their app didn't start properly on deployment. Or the install/startup procedure wasn't documented properly. Or it changed and the document didn't get updated. Or there was a new, required environment variable that didn't get mentioned in documentation anywhere. Or a new, required library was on the dev's local workstation and not on the server. etc etc

Anecdotal - I took over a small, ill maintained Splunk installation at $JOB-2 and reworked it following Splunks current best-practices and it ran like a top as of when I left that place. Having done that process I'm fully convinced that if you're going to run Splunk on-prem you need a dedicated sysadmin for it that knows Splunk's stack. And that kind of person isn't cheap to hire or keep in that role.

As long as upvotes can be manipulated (multiple accounts/bots) then having downvotes in places to reduce noise is necessary IMHO

Meanwhile the place I work writes all microservices in go and all of my team's (DevOps) tools are also written in go...