How to overcome the fear of a blank slate?

Question

Python

Realized that my problem is a subject.
I don't write code. I want to program, but the process of programming is practically not used.
I watch technology videos, I read books, I take tutorials that are all the same. I doubt the choice of language "java or python".
And I don’t undertake it because I’m afraid that I won’t cope, that the code will be terrible, that I won’t finish it and get bogged down in a heap of crutches, or that it’s too easy to write at all. Some kind of schizophrenia - I want to write code and I don't want to write code at the same time. Has anyone had a similar experience and how to deal with it?

Answer 1

Just stop making excuses and start doing what you love. Stay calm and carry on! Life is too short to waste it on your fears and complexes;)

Answer 2

Go work as a loader. Coding is not for you.

Answer 3

In writing, there is a trick “I don’t know what to write about” - as soon as you write this line, a meaningful desire to write about something immediately appears. Then it is enough to erase the first line, and as if it was easy to take it and write it like that.
Try to come up with lines of code that are similar in action. I am not strong in programming, but I will try to depict the essence:

function nihuyanedelat () { $loh == 0; NCNecros == 0;}
function pishicodbleat ('clean', 'perfect', 'no-crutches', 'more-money') {
    var $lenivaya_jopa = [name]=>"NCNecros";
    if (!loh) {
        $(workay_po_hardu) { document.respect('true'); 
    } else {
        $(sosai) { life.realise('false'); 
    }

day.addEventListener('NCNecros').onPC&morningСoffee = pishicodbleat();

Answer 4

A good way to deal with a subject is the method of short iterations. That is, as @gleb_kudr said , start with something very simple and implement it without thinking about the quality of the code. Then see if the code is too bad if you need to refactor. Then add some more small functionality, refactor again, and so on. You should read this book .

I doubt the choice of language "java or python"

- try to write something simple on both. A good programmer should know more than one programming language.

Answer 5

You just don't have the right job.
There are cases in history when people became programmers simply because they urgently needed to solve a specific problem (for example, to do data processing for scientific work).
And you, apparently, are trying to start programming just like that, "in order to be." Hence a lot of internal contradictions: "yes, why do I need this?".
Find a task to your liking and go ahead with the song.
As for the crooked code, it can really become a strong stopper ("the solution exists, but it's kind of crooked, so I won't use it, but sit and think about a more beautiful one").
Personally, I struggle with this in the following way: if I feel that I have blunted, I write a crooked implementation marked "FIXME: ...". This allows you to move on, and in the process you can either come up with a normal solution, or the logic of the code can change beyond recognition (and the crooked solution will go away by itself).

Answer 6

"No way, stay in the ass" (c) Lebedev

Answer 7

there was and sometimes there is such a feeling that there is not enough partner(s) - I like the idea of ​​pair programming :) Or if you are a student, you can start doing an interesting joint project.

Answer 8

I was so afraid too, and then once - and I already work as a programmer and fulfill third-party orders)
@Meehalkoff correctly says that life is too short

Answer 9

If age allows - a liter of vodka.
If it does not allow - read books, watch videos, wait ...

Answer 10

One day you either start writing code, or you get tired of reading books.
And then everything will be resolved

Answer 11

It is very familiar, here the way out is either to get a job in a good company as a junior, or to deal with it on your own. The second is more difficult, but for me personally there was no choice. No education, work experience, plus your own business project, far from IT, but which you can’t quit. Total - a minimum of free time, the absence of any support from more experienced colleagues. It's hard, but I want to write, because. it's the only thing that really fascinates.
My advice - take the simplest task and do it, don't quit. Find yourself a like-minded person, work together.
If you are interested in Python, you can work together, it depends on what area your interests are. If the web - that is, there are a couple of interesting ideas that have not yet been decided on, a partner would greatly help.

Answer 12

- Modules, Components - stop developing "applications", but do it through component composition, where a component can be either a small input with a popup or entire views. With this approach, you develop only components, small ones at first, then you start composing bigger ones, and so on. Thus, the fear of the whole application disappears, and you concentrate only on small parts.
- Modules, Layers - divide applications into layers.
- Tests- discover testing. Many people still develop like this - they wrote the code, launched the application, checked the result - but you need to write the code and write the expected scenario, and the test runner will run this part of the code and check whether everything was written correctly by us.
In general, happiness is in the right architecture.

Answer 13

Sign up to codeacademy.com and start a lesson in any language. if you know html css at least at the initial level, then jquery, if not - php. You can take ruby ​​or python, but for them tasks on the Internet, for which a beginner can cut down much less money, and a long absence of the opportunity to apply their knowledge in practice will not positively affect the process. Just don’t put it off until the evening or the weekend in a week, but now - there is really no difference between whether you read something or code - time is running out anyway, only the second option will give you bonuses in the future.

Answer 14

It helps a lot to break what you want into small and very simple pieces, make each of them separately and then easily put them together when you're done.
Maybe of course you will not finish, but even in this case you will do more than if you had not started :) And the resulting pieces may still be useful in the future.

Answer 15

Basically my problem