How do you program?

Question

Programming

I work in open space, I have little experience, there are very few programmers, mostly all kinds of evangelists, CEOs, designers, managers of all kinds, and I have never really seen how people write code.
The films show that it looks like this: a person sits down and begins to write. I don’t have this at all, every time there are some new tasks, I have to go to Google to look for answers on how to do this or that, I constantly monitor errors through the terminal. I have never sat and written for more than ten or twenty minutes in a row, I have no idea how it is when a person sits down and writes a hundred lines of code in a row. Explain, am I so dumb that I can’t write, or do many people write the same way?

Answer 1

Experience. Over time, some tasks begin to be solved without Google. Sometimes I sit down and write the admin panel without stopping all day, then I check - everything works. And sometimes I go smoking for hours thinking how best to do it, so that later it would not be excruciatingly painful. Sometimes I climb into Google or here for answers. But the more practice - the more continuous coding.
OpenSpace is evil. Try to communicate less there. Usually those people who talk a lot and know little. You can pick up shit ideas, break your brain, lose faith in humanity and the triumph of reason.

Answer 2

Practice. This skill will come with experience.
Gaming headphones are great against open space.
I'm interested in the logic of the moderators, I repeated the words of TS'a, but for some reason they didn't like it.
I always thought that a good answer half consists of a question, respectively, how to answer the question: "I'm so stupid that I can't write", to answer in the affirmative? If the answer "Yes, you're so dumb and can't write" is considered incorrect?

Answer 3

There are no programmers in films.
And yes - 10 minutes of thinking - 1 line of code - reality. In general - do not measure efficiency by lines - this is a big mistake.
Sometimes it's even worse with tz. managers - an hour of sticking and then half an hour of high-speed writing code.
And all this is the norm! The main thing is the result!
PS there is also Ballmer's peak...

Answer 4

This is the norm, IMHO.
Here is an article, almost on topic: https://codeahoy.com/2016/04/30/do-experienced-pro...

Answer 5

I have something like this:
1. I'm trying to understand the essence of the problem being solved
2. I'm trying to remember whether I solved a similar problem?
3. If I couldn't remember, I try to come up with a solution.
item 2. and item 3 - no more than 15-20 minutes for seemingly obvious tasks. For example, how to format a string in python or how to write a fixture in
a py.test test . and item 5 no more than 15 minutes. 6. If it’s not even there, then I inform my colleagues in the team that I have a plug and I need time. Maybe someone will come to my aid or tell me to postpone the task and do another equally important task 7. If I need to continue, then I ask my friends on skype or somewhere else
8. If there is still no help, then I go to Stackoverflow, toster, python.su, etc.
Everywhere you need to strike a balance. You have to think, you have to try. And be sure to consider that you are part of the development process