McSwag
Joined 7 years ago
Joined 7 years ago
That said, I think the intentional choice to not use sirens was likely a good call in this case and an example of good leadership. If the community is conditioned to recognize the sirens for tsunami’s only maybe that’s where the reform should start. If they CAN be used for other things, can they have different sounds for different things. It doesn’t need to be complicated.
Way way more often, the case is either flat out bad management or misalignment of the employee expectations with management and/or organizational vision which is way way harder to quantify so thus, nobody does. In the latter, there are often performance issues anyway.
All that said, I’ve worked for companies and have also seen people fired just for simply “looking.” Usually this is a sign of clear toxicity in the company culture because the management ego was hurt when they found out their employee was disloyal. We all know the company would just kick an employee to the curb at the first sign of trouble so it’s unfair to expect anything else from an employee.
There’s some innate connection that happens when I make real eye contact with another mammal only feet away from me. You can’t really earn the respect for nature or the respect of nature from a documentary.
Honestly it’s this same lack of connection I get on Zoom calls and I think it’s undervalued and difficult, if not impossible to measure.
I do think zoos have positively impacted many people, myself included, my kids (who are extremely passionate about taking care of the planet and animals partly due to their exposure). Of course I also feel the need to explain the business/darker side of zoos but young kids aren’t ready for the world to be so grim. They need to start learning coming from a place of optimism and hope. There will always be time for the other parts when they might actually be able to do something about it.
Kubernetes has a lot of merits and open source community support which is attractive which means out of the box integrations are vast.
That said, Nomad builds in a lot of sensible default behaviors that are way way closer to production ready with significantly less effort. Many things in Nomad, with Consul and Vault “just work” like you’d expect. Some of it seems like magic.
Kubernetes on the other hand does almost nothing for you to make your custom app production ready out of the box. This means there’s a ton of room for error and incorrectly configured applications. CNIs, Ingress, PodAffinity, PodDisruptionBudgets, Services, HPAs, ServiceRoles, Secrets management are not defined for you and must be exactly correct or orchestrated in clunky and obscure ways, or a ton of effort needs to go into filling these gaps. “Just use EKS/GKE” quickly becomes a list of subsequent decision trees and you need to hope yoy made the right decision because if you don’t your choice will be deprecated in 6-9 months.
The two config options for Kubernetes are Helm/Kustomize Yaml. Both are great for quick POCs but at production scale are completely inferior to HCL and generally an absolute nightmare to work with on the day-to-day.
If I’m a team of one in a startup, I’d choose Nomad.