@maria_fibonacci Ppl confuse understanding _what_ happened (the series of casual events that lead to the failure), with _why_ it happened (why the system was is in a state where the failure could occur). The latter is messy with no single cause, but you gotta know what triggered the failure too!
Anyone know of research on possible positive feedback loops between textile manufacturing and rag production during the industrial revolution? Was that significant at all?
Had a nightmare last night where I kept bumping the yubikey on my laptop and couldn't delete the resulting slack messages fast enough to get out of the app before accidentally spamming it with more codes. 😰
This Wed's @kubernetesio Policy WG meeting will have @nikhilbhatia to give a project update on @OpenPolicyAgent gatekeeper project, and I will have a short talk regarding policy across deep RL and cloud https://t.co/35fsWhXpiJ
Exciting to see some attention given to policy in the kubernetes space! It's way more interesting than it sounds :). Join us in wg-policy for lots of discussion and cool stuff. https://t.co/vavc4aw5X0
@cheddarmint@youngnick@TheAmyCode Maybe should be, but I’ve been too busy working on open source 😎.
Most of my scripts haven’t made it out of the private repo where I keep my env setup, and hide the evidence of my procrastination tweaking colors and formatting for the term output.
@cheddarmint@youngnick@TheAmyCode This is what I do too, with some custom bash scripts to set it up for new clusters and such. It’s also helpful for stashing any yaml or logs specific to that project or cluster.
"how do you effectively manage first-class extensions to Kubernetes over time?"
We thought _a lot_ about this problem and I think we came up with something pretty great is response. Check out @jimmyzelinskie's intro here!
Tech leadership is broken. Most people think the goal is to win a debate. Tech leadership should be about enabling others to debate and deliver a right/optional solution rather than arriving there yourself.
1/ Of course Google's AI bot that sounds human poses some terrifying problems. Of course it must be tweaked. At the same time, this is how innovation has always happened: leaps forward with terrifying blind spots that must then be addressed. Innovation is messy.
“Think of an Operator as an extension of the software vendor’s engineering team, that watches over your #Kubernetes environment and uses its current state to make decisions in milliseconds.” https://t.co/6EgjDyYDqT