Can anyone relate to the following scenario:
You receive a task, but you have no idea where to start (it's a big chunk of code that has to be written). After a more senior developer tells you the steps you should take, you still feel they're too big to deconstruct and start, which makes you anxious and causes uncertainty, even imposter syndrome. How should this be handled?
I can't say that I've done something like this at work as my working experience is rather than logistics, but saying that when we did have big issues maybe even to big, what we would do is try to break them down into smaller ones so it reduces the natural anxiety.
I've always been thrown in the deep end, and even now i'm trying to build a platform which is the biggest thing I've built there are days it's overwhelming but I know its something that I must do, if it takes me longer to do it then that's fine :)
I wouldn't think impostor syndrome comes into play, this only comes into play when you might have someone who says that they can code in xyz but they cant. But remember its always important, if you do feel that its a bit too overwhelming, just ask if maybe the project or item can be split and you might be able to manage it a bit easier :)
Mark
Breaking up solutions into small steps is a useful skill that takes time to learn (and might also take some knowledge about the problem domain).
So don't worry, you'll likely get better at it with practise.
What would probably be wise to do is ask the senior developer to break it down some more. Or to break down one of the steps that (s)he described. Breaking it down together would be even better if there's time.
Take notes, or break up the steps in the issue tracking system (e.g. stories in Jira).