Humanitarian programmer

    For some reason, I was considered a good mathematician in elementary school. Sent to the olympiads in mathematics and physics, scolded for poor results and sent again. It is worth noting that from the Olympics I still brought the first two places, but they were regional in German. In high school, the situation did not change for the better, but I still understood the geometry. But at the university, I already felt like a little boy surrounded by a crowd of smart uncles and aunts. I could not survive the first session.

    I often read stories here about how people became true programmers. As at age 13 they hacked into school servers and came up with ingenious viruses. I envy these people and their mindset. My acquaintance with programming happened in elementary school when I drew circles and squares in QBasic. I loved the GOTO team and didn't understand Pascal at all. Since then, a lot of time has passed, I learned a lot of new terms and make a living web development. But sometimes it seems to me that these are all the same circles with squares, they just whistle and funnily mumble. I never learned Pascal.

    I started doing sites right after an unsuccessful attempt to get a higher education. I sat in a computer club, played in CS and suddenly it dawned on me - I need to learn HTML. Fortunately, my friend suggested where you can read about it. The first site was in pure HTML and it gave me a lot of trouble adding a new menu to all the files, so the first acquaintance with PHP began not with echo 'hello world', but with if - include. This became a real insight for me, I quickly bought one of the many books “PHP and MySQL for Dummies” and plunged into reading. I like it.

    My first serious project was the site of this computer club, which I did absolutely free of charge "for free and hosting." It was like in the song "Island of Bad luck", just the opposite. That is kind on the face, but terrible inside. However, later it was thanks to him that I got my first normal job.

    I understand perfectly well that I started from the wrong place. Many will say that in the beginning it was necessary to understand the basics. Data structures, algorithms. Of course, this is the right approach. But I suspect that in my case, such a training scheme would turn out to be a failure. Why? Because I wouldn’t understand anything corny. Because I'm tight.

    I opened my first book on OOP and design patterns about 4 years ago. Opened and closed after 5 minutes. Nepanyatna. The next time I moved a couple of pages further, but understanding did not increase. Since then I open different books on patterns (and on other topics) with a frequency of once every 2 weeks, but only a part is understood. And only the part that I somehow encountered in practice or spied in someone else's code.

    I admire people who easily juggle with OOP terms and can sketch architecture on paper to solve any complex problem. Which can take a look at the intricacies of the code and quickly understand how and why it works. If I pick up a pencil and put a blank sheet of paper in front of me, instead of architecture, I can draw only funny squiggles.

    And at the same time, despite the absence in my dna of a gene very important for a programmer, I really like it all. I like to look at my code, which, although simple and ill-conceived, is MVC. I like to typeset and give advice to my less experienced friend. I like to write long selects, although it may take a couple of hours. I like to sculpt all kinds of chips on JS.

    Every time I start something new, I am filled with enthusiasm. I try to read a lot and keep up with the times. Most likely I will never become a cool high-paid specialist, but I will not die of hunger either.

    Also popular now: