I learned this lesson much younger than most, before I even have had career "success" or whatever. In some ways I'm happy to not have this problem, but it feels isolating to not have suffered with the masses.
You do seem like an earring kind of guy tbh. It's a compliment.
Yo... so that analyst role. 👀
I'm not sure. By 5am I called it that I wasn't going to sleep, so I did a peloton workout. That should at least get me through work, and then I'll probably nap for 3 hours and sleep as much as possible tomorrow.
If the journey of writing is worth it, it's not a waste of time. So more realistically there's 3 pillars: - constructive storytelling (the side dishes) - important info (the meat) - stupid fluff (condiments you won't use) Figuring out what condiments your readers wouldn't use is key.
That is fairly subjective. But my rule of thumb is that if I can boil down the thought into three tweet lengths *without losing important nuance and context*, it is not worth longer form. Does the sentence provide important info or is it just storytelling prose? - is another good question I ask.
You are correct, that photo was taken in Wisco 😊
I stand by that my bio here says "no one of consequence", but I do technically work for a data orchestration company. Also, here's my much more realistic picture.
As data people, we should know better that redundancy is important. Only deploying the community direct to prod with no dev environment? How could we.