> It's easy to assume you're great especially working under "passion coders" who keep stuff afloat.
i work on compilers+hardware so that's the backdrop here.
here's a real hypothetical for you (ie it happened but i'm not going to use specifics): our internal proprietary compiler is spitting out incorrect atomics instructions that deadlock our internal proprietary multi-core DNN accelerator. this incorrect code is downstream of a big, lucrative, customer's (you know which one) LLM model.
now the question: is it the "passion coder" that will solve this or the grinder?
i work on compilers+hardware so that's the backdrop here.
here's a real hypothetical for you (ie it happened but i'm not going to use specifics): our internal proprietary compiler is spitting out incorrect atomics instructions that deadlock our internal proprietary multi-core DNN accelerator. this incorrect code is downstream of a big, lucrative, customer's (you know which one) LLM model.
now the question: is it the "passion coder" that will solve this or the grinder?