ashwiniag
A concept that serves as both a negotiation tool and a practical decision-making framework, on efficiency of an algorithm that suits the needs of current problem. Big O just tells how slower my program is going to be as the input size increases. So technically, It doesn't dictate
In my current organization, I wrote a helper script long back to organize and set up Kubernetes contexts across multiple GCP projects and environments, with custom naming based on cluster labels. I also created another script to handle all EKS clusters across AWS regions using a specified AWS SSO profile.
— The nightmares we all live are truly an inspiration to never live. Honesty is a fragile illusion, a reflection of never being good enough. We live to rule, and we rule to live—trapped in the chaos of collective minds, yet bound by the desperate need to be seen. Why?
We’ve been building gokakashi in Go for a while now, and we had this wild thought: “What if users could define their own evaluation conditions on top of the scan reports?” Something like this in the config file: check: condition: | sev.critical > 0 || sev.high > 0 &