Yishayahu Steve Bar Yakov Gindi
I can solve most problems of how different systems interact within about 6 hours of focused daytime work — often faster. Whether it’s a networking layer trying to encapsulate traffic, or a Kubernetes cluster struggling to connect with AWS infrastructure, my strength is untangling the way one system talks to another. I don’t mind pressure or even raised voices in urgent situations. What blocks results is when existing practices aren’t communicated, and team members (even smart oens) are criticized for not magically knowing hidden rules.
I work thoroughly, and I expect to be given accurate information to do my job. With clear explanations of fields and requirements, I can configure and create any pipelines. What slows me down is tribal knowledge — when information is hidden, undocumented, or mistakenly assumed to be “common knowledge” for seniors. My best work comes when clarity is prioritized, because clarity unlocks speed, precision, and reliability.
“An Allegory of Prudence” by Titian 1565
The Helm Chart Incident (Tribal Knowledge Exclusion)
During onboarding, I was told to “fix the Helm release” The chart had bizaare uses of trafik and confusing nameing schemes that are different for public vs internal ports. The devs could not adequatly understand the difference between the different ingresses to properly answer how the app work. When I asked for guidance, the response was: *“You’re senior, you should know.”*
Insight: I value clear documentation. Tribal knowledge and hazing waste time and block reliability.
Hostile Mentorship and Performance Theater (BGP)
In a screen share, a contractor on a long irreversiable contract, reversed roles, demanding I explain BGP to him in front of the team. This wasn’t mentorship — it was humiliation. Later, I studied my brains off and worked really fast without assistance.
Insight: I perform best in collaborative mentorship environments. Toxic “performance theater” undermines learning and productivity.
VXLAN Encapsulation over Open vSwitch (Persistence Pays Off)
A while back, I spent four days solving a VXLAN encapsulation issue over Open vSwitch. Documentation was sparse, and each attempt failed differently. By tracing the encapsulation path step by step, I found all colleagues congratulated me.
Insight: In supportive environments, persistence and clarity lead to breakthroughs.
Traefik on Karpenter Nodes (Misleading Error + Yelling)
During a production outage, Traefik was deployed on unstable Karpenter nodes. The AWS Load Balancer Controller threw this error:
{"level":"error","msg":"Reconciler error","controller":"targetGroupBinding","error":"expected exactly one securityGroup tagged with kubernetes.io/cluster/<cluster-name> for eni <eni-id>, got: \[<sg-id-1> <sg-id-2>\]"}
The log pointed to security groups, but the real issue was that the instance wasn’t joined to the **Auto Scaling Group or Target Group** after a Karpenter upgrade. The fix required manually attaching the instance to both.
Under yelling — *“You’re senior, you should know!”* — the misleading log became paralyzing. Even now, it takes time to recall how off the message was.
**Insight:** I thrive when seniority means guiding with clarity. Misleading logs plus hostility create “panic core dump” moments; clear explanation unlocks solutions.
Summary of my Work Style
These stories illustrate the environments that trigger “panic: core dump” moments versus those where I excel. They reinforce my boundaries:
I am Least effective when information is withheld, then weaponized — whether through hazing, hostility, or passive‑aggressive criticism.
I am Most effective when ambiguity is treated as a chance to create clarity, supported by structured collaboration and doumentation. I thrive through persistence in an environment that values reliability.
Chaos is never an acceptable substitute for clarity. KH4Ø5 is only fun for a few minutes before it gets zapped into CVE compliance.
I tell all of the people in the SkatePark “If you got up it, it means you fell”. Resilience and clarity are how I rise again.
