Slowly solving tasks, how to fix it?

the5x2020-04-25 01:26:28

Work organization

the5x, 2020-04-25 01:26:28

Guys, there is a problem.

When I start doing a new task, or a set task, I always do it, it's very slow.
I start writing code, I get to a point and then I can get stuck for several hours looking for
a solution, or until someone helps. And so with any given task.
I can't write from start to finish . Slow performance.

Tell me how can this be fixed?

Answer the question

In order to leave comments, you need to log in

8 answer(s)

Ronald McDonald, 2020-04-25
@the5x

It was so. This "hand is not stuffed", the reception is not on some technology, but on the very principle of sorting out errors and finding a solution. Will come with experience.

Robur, 2020-04-25
@Robur

the answer depends on these questions:
What area?
What experience and level do you have?
Is there anyone nearby who solves the same problems many times faster?
Why do you think you are doing everything very slowly?
Have you tried to immediately go and ask someone who can help as soon as you get stuck?
Do you get stuck all the time on the same thing or are these diverse tasks and do the familiar quickly?

Valentine, 2020-04-25
@vvpoloskin

Industry not specified. But, apparently, the organization lacks a person who will say "look here and do it by analogy, the deadline is in an hour." Well, or another option - incompetence.

Em Ka, 2020-04-25
@Mirkss

I will write you a specific way to increase the speed of work.
The method was once taught to me by a professional tutor, and for many years of use, I and everyone with whom I shared were convinced of its effectiveness in various fields of activity.
1. Break the task into clear subtasks.
2. Before the beginning of each stage, write down on a piece of paper the name of the stage with the note "started at /time/"
3. At the end of the stage, make a note of the time "finished at ....".
It may seem strange, but it really increases the speed of work dramatically and contributes to its increase in the future.
Good luck!

Andrey Ryazantsev, 2020-04-25
@fo_otman

It's like that for everyone. Even experience does not always help here. Every project has its quirks. That's why I really don't like to work on pre-estimation. You never know what difficulties you will run into. As a rule, the customer does not agree to an adequate assessment, and to which he agrees, then you feel like an idiot that you missed all the deadlines.

Sergey Shat, 2020-04-25
@sergeyshat

Real and strong, quality - always slow, difficult and long.
A good doctor studies for 10 years and gets another 10 years of experience, then it becomes a little faster :)
And so are specialists in all areas.

approximate solution, 2020-04-25
@approximate_solution

You wrote that in the company for 6-7 months, when you got settled, according to your feelings - were you a solid junior? Or went with a bang, with God's help?
For your understanding - a solid jun, able to quickly solve typical tasks and turn to older comrades for experience, when blunting on a conditionally medium / difficult task - about 1 year - 1.5 years of work (this is if you were not born with a silver spoon in your mouth and not gifted with the gift of programming).
In addition, you are doing the biggest stupidity of a beginner, it is always easier to grow as a specialist - when they share experience with you, for this, middles, seniors exist in the company to increase your efficiency through the prism of their work. Do not hesitate to contact colleagues, if colleagues try to put themselves above you, and try to humiliate you on the topic of frequent requests for help, then I sympathize with you and your choice of company.

Daddy_Cool, 2020-04-26
@Daddy_Cool

"then I can get stuck for a few hours looking for
a solution, or until someone helps."
Give an example!
They forgot to put & in the scanf function - or found out that "in principle it should be done, but it's not clear how" - such as converting data via the USB protocol to HDMI, creating a class of arrays of structures from classes with pointers to structures, etc. .?
Perhaps insufficient basic training - if you have to go to Google for every sneeze.
Perhaps insufficient knowledge of a particular stack.
Perhaps you have tasks at the junction of stacks, and you physically cannot know everything.
Perhaps you have a bad memory and you forget what you googled a week ago
. Perhaps you have poor attentiveness, you fly into other thoughts and miss mistakes.
Perhaps you just have difficult tasks. Won - the thermonuclear reactor has not yet been done normally and the robotic car has not been done either.