The story of a downed programmer.
Hello Habr!
Every day I read on your pages the stories of people, their problems and projects. And, in general, I see that most of them are successful and they like their work. I like her too, but today's date on my personal calendar makes me rethink what I have been doing all this time.
Today is the year, Habr, YEAR as I develop a site for my company. And so far there has not been a single public release.
Tell us about yourself. I’m 21, part-time, I joined the company more than 2 years ago as an HTML coder, knowing a bit of HTML and CSS and not knowing PHP at all. For that time, this knowledge turned out to be enough - both sites were completely static and all the work was to add new pages to them and edit the old ones.
My acquaintance with PHP (I hadn’t done web programming before, I knew C / C ++ and picked Java a bit at my leisure) began with small scripts. He did it once, did the second one, and the authorities began to move me in this direction, making the tasks more complicated. Which I, of course, was very pleased. :) Having already reached the programmer level, I found out that the company ordered an online store site from one web studio. This store, however, was accepted by the management with serious flaws and generally glitches and required file processing, which was done by the invited "specialist". True, he quickly faded, despite a good salary, and the file was solemnly handed to me.
Fortunately, I didn’t have to dig deep into the store code, I was more concerned with what could be called the “front-end” - fixing buggy javascript, editing the design, organizing the process of buying goods, etc. In such mild conditions, I became acquainted in practice with PHP, SQL, XML, XSLT and, as they say, I felt the Force in myself. :)
The store was finished and released. Now it brings a stable income (although, in my today's opinion, it is terrible). All this greatly inspired both me and the management, who decided to get rid of the old static sites and create a completely new, modern, with an integrated store, newsletters and other goodies. Bitrix was chosen as the CMS, whose representatives gave us a colorful presentation of the features and ease of use. We were inspired even more ... And further went failures.
Every day I read on your pages the stories of people, their problems and projects. And, in general, I see that most of them are successful and they like their work. I like her too, but today's date on my personal calendar makes me rethink what I have been doing all this time.
Today is the year, Habr, YEAR as I develop a site for my company. And so far there has not been a single public release.
Background
Tell us about yourself. I’m 21, part-time, I joined the company more than 2 years ago as an HTML coder, knowing a bit of HTML and CSS and not knowing PHP at all. For that time, this knowledge turned out to be enough - both sites were completely static and all the work was to add new pages to them and edit the old ones.
My acquaintance with PHP (I hadn’t done web programming before, I knew C / C ++ and picked Java a bit at my leisure) began with small scripts. He did it once, did the second one, and the authorities began to move me in this direction, making the tasks more complicated. Which I, of course, was very pleased. :) Having already reached the programmer level, I found out that the company ordered an online store site from one web studio. This store, however, was accepted by the management with serious flaws and generally glitches and required file processing, which was done by the invited "specialist". True, he quickly faded, despite a good salary, and the file was solemnly handed to me.
Fortunately, I didn’t have to dig deep into the store code, I was more concerned with what could be called the “front-end” - fixing buggy javascript, editing the design, organizing the process of buying goods, etc. In such mild conditions, I became acquainted in practice with PHP, SQL, XML, XSLT and, as they say, I felt the Force in myself. :)
Breast on loopholes
The store was finished and released. Now it brings a stable income (although, in my today's opinion, it is terrible). All this greatly inspired both me and the management, who decided to get rid of the old static sites and create a completely new, modern, with an integrated store, newsletters and other goodies. Bitrix was chosen as the CMS, whose representatives gave us a colorful presentation of the features and ease of use. We were inspired even more ... And further went failures.
- Lack of development plan. The conducted seminar showed that creating a site on Bitrix is really simple - there is a visual editor, ready-made components. It seemed that the fine-tuning was required very little - to create pages with the necessary components, to correct templates for them - and here it is a product. Therefore, no one even thought to draw up TK, because any idea is so simple to implement! The devil, as usual, was in the details. The flight of imagination of the authorities quickly went beyond the standard functionality of the components, but it was not clear how to realize their own and what things might be needed. The first cones flew at me: “How do you need to figure this out? After all, everything is so simple there! ”
- Reassessment of forces. But here the first problems are overcome, an initial understanding of how the system works has come. Everything turned out to be quite logical, and my recovery began again. What I reported on, and it was decided to figure out in time how long it would take to create my product. It goes without saying that everyone wanted to get ready quickly, and the deadlines were imposed on me short. And I, like a complete fool, succumbed, decided to just strain up and give out.
- Weak research. The consequence of the foregoing was, of course, the occurrence of stupid problems out of the blue - did not take into account here, did not take into account there and as a result you get a crooked semblance plus a dead end in moving further. Each product can do something, cannot do something without outside interference in its code. What Bitrix cannot do was not taken into account by anyone, and the rush did not allow time to analyze the strengths and weaknesses in the application for a particular site. I had to change the functionality of the components, and I ended up in a completely dark forest. The serious CMS code for me at first turned out to be very, very complicated, there were no comments in the code completely or were very short, like “here we use the cache”.
- Lack of motivation. It was entirely my fault - the difficulties got me down and I just started to “pull the strap”, not planning ahead, not analyzing the root causes of the problems, and just sitting with an empty look, leafing through kilometer-long files with the component code, silently listening to the accusations that yesterday the invented "small" feature has not yet been implemented.
Now I am experiencing the rebirth of this project for myself. I figured out old problems, I know how to understand new problems, I try to think in detail what and how I will do. I actively argue my position with my superiors, explain why, from their point of view, it will be necessary to implement a trifle such as accepting credit cards for not an hour or two. The mood is fighting. :)
But today's date made me think that before that I had been doing garbage for a YEAR and wasted my time.