my biggest unexpected engineering lesson from my short adventure at merkle:

if you're cracked you have enough confidence to ship code to high-traffic prod without testing it first

stuff that i would estimate in my head for 2 days @gt can do in 2 hours because he just looks at the code, knows what to change and ships it -- while i need to find a way to run in a replicable environment, test, give others and only then im comfortable with shipping

bell curve: test in prod -- automated tests / staging / replicated envs -- test in prod

Chasing Curiosity. People, Nature, Machines. Hakuna Matata, "Its a problem-free philosophy.”

Woj is kind and is gassing me up. 🙂

I personally don't think I am "cracked" and do think its more about the error resillient systems, logging, monitoring, tracking, continuous ability to deploy or revert if needed and the actual culture of shipping.

With that being said, one thing I have found it helped me improving my hard skills: reading a lot of code. Not just the code related to what I worked on or had to review but big systems at scale. I also had the privilidge of working with multiple A+ engineers in my career so far.