3 ms·
”Prod is on fire and nobody can figure out your burrito pasta” ”Isn’t this a wonderful learning opportunity for all of us” Debugging time is never a good time
by nikanj 7y ago
”Prod is on fire and nobody can figure out your burrito pasta”
”Isn’t this a wonderful learning opportunity for all of us”
Debugging time is never a good time to start honing new skills.
- cbsks 7y ago“Burrito pasta” is a great term! Is that something that you just came up with? It sounds like spaghetti code but even worse because it’s covered with a messy layer of beans and guacamole and wrapped in layers of tortilla.
- nikanj 7y agoJust came up with it. The complexity of monads and other post-grad level CS stuff mixed with good old spaghetti code. Next up: some doofus who learned high-order Haskell in middle school, and takes offense of me calling it complicated. PS: https://blog.plover.com/prog/burritos.html https://blog.plover.com/prog/burritos.html
- enriquto 7y agoOf course, Kernighan's lever is most useful on individual projects. In an industrial context there are often other constraints. Nobody is saying that you have to always write the most clever code you can. But if you never do it, you will improve your skills very slowly, if at all.
- spenczar5 7y agoWriting simple code is difficult, more difficult than writing clever code, and is a better skill to grow.
- wtetzner 7y agoI would hope at least most of the debugging happened before the code made it to production.