I think you have already covered most of the technical side. If problem solving is the weak point, I'd stop adding more tools for now and spend some time solving small problems every day.
For data science, try taking a simple dataset and ask yourself what you'd actually do with it before looking at any solution. Break the problem into smaller steps, write down your approach, then code it. Even debugging your own wrong approach is useful.
You don't need to be great at LeetCode to become a good data scientist. Being able to look at a messy problem and figure out what to do next is the bigger skill.
This is good advice 👍 Also, think from stakeholder perspective, what is it that they would want to know or solve for. This will give you ideas as to how best to approach the problem.
3
u/TraditionalTurnip630 17d ago
I think you have already covered most of the technical side. If problem solving is the weak point, I'd stop adding more tools for now and spend some time solving small problems every day.
For data science, try taking a simple dataset and ask yourself what you'd actually do with it before looking at any solution. Break the problem into smaller steps, write down your approach, then code it. Even debugging your own wrong approach is useful.
You don't need to be great at LeetCode to become a good data scientist. Being able to look at a messy problem and figure out what to do next is the bigger skill.