How to speed up the work of a programmer?

Question

PHP

Good afternoon, please tell me how did anyone develop the speed of programming?
The reason for the question: I recently started working as a programmer in one of the offices, among the other interns in the princepe I keep at the level (except for one), I solve, let's say, about 40 tasks per month. Experienced developers decide about 100 or more, what could be the reason for such a difference?
Actually, I'm currently looking for an answer to this question. While there are thoughts:
1. Gain experience - and speed will increase.
2. Make code blanks.
Maybe someone else has some ideas, thanks.

Answer 1

The main thing you need is to write less code that will implement the task assigned to you.
Before starting a task, you need to decompose it. You've done that, added specific items to your product backlog (I use trello for this), start doing it. Set yourself any time-tracker, for example toggl and measure the execution time. Work like this for 2-3 weeks.
When you collect some statistics, you will see where your time goes. Then start optimizing what you repeat from project to project. There are two ways here:
Optimize your routine, i.e. You need to constantly collect some front-end scripts, upload files via FTP / SSH somewhere, then definitely dig in the direction of grunt / gulp. If you work with the back end, then it may make sense to delve into the capabilities of your IDE, set up automatic creation of libraries, packages, modules, etc.

Answer 2

Do you want to reveal the secret of how to speed up absolutely any process?
1. Determine the most time-consuming part of the process (factors that slow down the process).
2. Figure out how to speed up / automate / delegate / remove this part (get rid of factors).
3. Go back to step 1.
For example, if every two hours you only take 10-15 minutes off just to read someone's twitter, that's more than 13 hours of wasted work time per month. Start tracking what you spend your time on.
In your case, out of those 40 tasks, try to remember the ones that took the longest. Better yet, start timing the tasks you'll be doing. Analyze why you spent more time on some tasks than on others. As a result, they should identify specifically your problem that slows down the work, so solve it.

Answer 3

1. Design solutions before writing code. Colored markers in a notebook. Write down microTK before writing code. In a notebook or in any text editor. In general, writing code is easy, you know, right? Figuring out what to write is another matter.
   These simple things helped me increase my productivity by about ten times.
   And yes, do you use VCS and frameworks?

Answer 4

The number of tasks is not an indicator. They may be different.
From "I want the month and day to change places here" to "add store functionality written from scratch".
Of course, with experience, you can quickly solve simple and mundane tasks. Since you are working together with experienced programmers, ask them what tasks they solve, what they use, what they advise and why there are so many tasks (compared to you) that they do not bite.
The question is too general.

Answer 5

What for?
I have been solving one problem for the second year, and it does not bother me at all.

Answer 6

Frameworks.

Answer 7

by technique:
-2nd (3rd!) monitor
- correct IDE
- fast computer

Answer 8

unambiguously make code blanks.
now completely for all orders, even if the customer does not need it, I make a version in the form of a plugin / library for myself.
helps a lot to reduce the time for the following orders. well, if you make blanks, you need to adhere to the same style of writing code. which increases its readability and speed.
then, before taking a task, if there is no similar solution from those already completed, you should google it. even if the task is very simple / typical, or, conversely, something complex and non-standard.
for 90% of tasks, you can find a ready-made solution / solution algorithm / library.
learn the tools. npm, bower, composer, vagrant, grunt, etc., which suit your specialization.
free up a lot of time, learn to use the right patterns

Answer 9

1. Don't do what the computer can do (puzzle it)
2. Don't do the same job twice (use the results of what you've done if possible)

Answer 10

All you need for speed is coffee and cookies. Everything else comes with experience.

Answer 11

Well, never thought about it.
Speaking about myself... I don't use any time trackers, or time-something else, no felt-tip pens (especially colored), no notebooks, and so on, and I also don't look at other colleagues. I have such a mindset: all sorts of “drawing games”, collective planning, etc., only distract and tire me. Perhaps because of this it will be difficult for me to advise something intelligible, but ...
1. Work as best you can. There is no need to strive for the stars, because if there are inclinations, it will manifest itself. This is how you develop the right self-esteem.
2. Read literature, smart, and not "C ++ for a month", but "Architecture of Enterprise Applications" and others like it. So you will have a theoretical platform for understanding both micro-architectures and more serious things.
3. Observe yourself to understand: what periods of the day you are most comfortable working (when you are most productive), and what factors influence this. That way you can plan.
4. Do not try to memorize the syntax and semantics of languages, but to know some general things, as well as places where you can quickly find the answer. So you will have free space in your head.
In general, work hard, read literature, and everything will be fine.

Answer 12

You can not measure the speed of the programmer in the number of tasks completed. If so, then your work is organized incorrectly. All tasks should be evaluated in terms of labor intensity - this is a complex indicator. Usually expressed in hours. The whole team should evaluate. Read about scrum.

Answer 13

Experienced developers decide about 100 or more, what could be the reason for such a difference?

Because they already remember the past analogues of the problem, and do not look for a solution from scratch.

Answer 14

Learn more about working with the IDE and set up plugins to automate routines.
If we are talking about Windows.
Prepare a bunch of small bat scripts to run the same set of console commands.
Go to the terminal emulator www.conemu.ru

Answer 15

Quit using php with its stupid frameworks - there are so many great frameworks like rail, janga. And of course you need to stop using Windows, and remember Ctrl + R in the bash

Answer 16

IDE from JetBrains significantly speeds up the development speed and increases the prof. level