Exactly! And it’s same goes with code, graphs, UI, etc. Less is Better! The shorter and simpler approach to the given problem to solve is usually the ideal one 👌
Love this! I’m Harrison, an ex fine dining line cook. My stack "The Secret Ingredient" adapts hit restaurant recipes (mostly NYC and L.A.) for easy home cooking.
Great advice! Number one especially. One of the anti patterns we pick up from school is when it comes to writing, longer = better. Absolutely not!
Exactly! And it’s same goes with code, graphs, UI, etc. Less is Better! The shorter and simpler approach to the given problem to solve is usually the ideal one 👌
So true! So many of my peers coming from a research background also struggled quite a bit with this.
Such a nice read !!!!! Thank you so much for this
Happy you found it insightful!
There is absolute truth in that people will read your work. Practical advice...two versions. Thank you.
Thanks for sharing, it deeply resonated with me. I love the idea of making stakeholders fill out the form before jumping in to do the analysis.
Those all very real and practical insights. Thanks for sharing, Andres!
These are killer insights.. be an expert in your area and don’t rush the results or your analysis..
Thank you for the advice! I had a question for clarification though, how do you prioritize business questions/impacts when you have multiple requests?
Love this! I’m Harrison, an ex fine dining line cook. My stack "The Secret Ingredient" adapts hit restaurant recipes (mostly NYC and L.A.) for easy home cooking.
check us out:
https://thesecretingredient.substack.com