Photo by Nandhini Kumar on Unsplash
As developers, we're presented with the vastness that is software engineering. This, along with the ...
For further actions, you may consider blocking this person and/or reporting abuse
This is a great analogy! Loved the writing, as well.
However, had you not said sorry to broccoli there in the end, I don't know if I'd be singing the same tune. Broccoli is my jam! 🥦
Thank you!! I know right? One of my favorite dishes is this AMAZING Beef n' Broccoli recipe. Super easy to make too!
Haha, just saw this notification again from yesterday. Checked out the beef & brocc... and man, that does look amazing!
I do enjoy broccoli, so maybe not the greatest analogy for me. But my "broccoli" was physics programming while I worked in gamedev about a decade and a half ago. I really hated programming physics and I thought why the hell should I? There were so many other exciting areas, so I just stepped away and did graphics, shaders and visual effects programming. I was much happier because of that. So I chewed a bit and spit out my "broccoli".
I think the main difference here is that you're talking about a fundamental skill, like certain types of algorithms or techniques, and those are essential. I would rather eat those. For me that would be dynamic programming. I have yet to discover when that thing is going to be needed in my daily job, though. But if your broccoli something more of a domain, like webdev or ML, I think it's totally fine not to chew and just pick something else.
What are your 'broccolis'? Do you also turn away from it or do you force yourself to eat it every month?