You shouldn't worry about it that you need more time. Only with a lot of experience you will learn better to estimate your work or to divide the tasks meaningfully. Every experienced developer knows this and will understand that you need more time.
It seems to me that you have to do many different tasks at the same time.
My advice, focus on one thing at a time.
So that you also have a sense of achievement, divide the individual tasks even more into subtasks. The best way is that they do not take more than 30-40 minutes per task. Maybe even less.
such techniques can help: en.wikipedia.org/wiki/Pomodoro_Tec...
You must not be afraid to ask questions!
Good experienced developers will take time to explain things to you if you ask.The best thing would be to ask someone to do code review with you on a regular basis. if you get a lot of criticism in the beginning, do not take it personally (as long as it is constructive). You can only learn from it
When you have learned something new, it's best to recap it later again and write it down.
Your superiors know how difficult it is at first. I'm sure you'll have puppy protection for e.g. a year.
Wowsers. Thank you so much for the advise. I often get told I should aim for small tasks and this is a work in progress for sure.
Dividing a task by minutes up to maximum an hour seems super valuable. Will apply this for sure.
I keep forgetting how helpful code reviews can be. Will encourage myself and my colleagues to provide me with these as mush as possible.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You shouldn't worry about it that you need more time. Only with a lot of experience you will learn better to estimate your work or to divide the tasks meaningfully. Every experienced developer knows this and will understand that you need more time.
It seems to me that you have to do many different tasks at the same time.
My advice, focus on one thing at a time.
So that you also have a sense of achievement, divide the individual tasks even more into subtasks. The best way is that they do not take more than 30-40 minutes per task. Maybe even less.
such techniques can help: en.wikipedia.org/wiki/Pomodoro_Tec...
You must not be afraid to ask questions!
Good experienced developers will take time to explain things to you if you ask.The best thing would be to ask someone to do code review with you on a regular basis. if you get a lot of criticism in the beginning, do not take it personally (as long as it is constructive). You can only learn from it
When you have learned something new, it's best to recap it later again and write it down.
Your superiors know how difficult it is at first. I'm sure you'll have puppy protection for e.g. a year.
Other people have same problems too, although these people have a lot of experience:
dataquest.io/blog/how-to-overcome-...
Wowsers. Thank you so much for the advise. I often get told I should aim for small tasks and this is a work in progress for sure.
Dividing a task by minutes up to maximum an hour seems super valuable. Will apply this for sure.
I keep forgetting how helpful code reviews can be. Will encourage myself and my colleagues to provide me with these as mush as possible.