We have previously written about several CodeGym programmers. Our next story is about the head of the development team Alexander Myadelets. Sasha became interested in programming at school, later this hobby grew into professional development. Having worked in many companies, Sasha has been working at CodeGym since 2014: first he wrote tasks for the course, later he moved to the backend, and then he began to lead the development team.
“I started writing the most primitive games”
In the ninth grade, I changed school to college and we got a new subject - Computer Science. We began to study Pascal on it, and at first I didn’t quite understand what it was: we were given some manuals, they contained examples of programs, we retyped them, rewrote them on sheets. Often they didn't run because there were typos, such as missing a semicolon. A little later, I got a computer and started installing some games, before that I only played with my friends. Once a classmate said that you can make games in Pascal. I was very interested in this: it's very cool when you can write something and it is visually displayed. I started writing the most primitive games. During the 10th and 11th grades, this is what I did. That's when I realized that I wanted to become a programmer. In the environment in which I communicated, programming was not mainstream. This profession was not popular and there was no information that programmers had high salaries. I went to enter the Donetsk National Technical University. It had several specialties related to programming: system programming, software, computer engineering. I read the description and it seemed to me that system programming is the coolest thing offered. I went in this direction. My specialty involved both software and hardware development. The knowledge that was given at the university was not useful to me, but the ability to deal with something, to do something on time was useful. When I graduated from university and went to work, it seemed to me that it was easier to work than to study. In the first year we studied Pascal,
“I was invited for an internship in Poland”
While still studying at the university, I participated in the Olympiad from an American company, won one of the prizes, and I was invited for an internship at the Polish branch of this company. It was my first trip abroad: then I saw how programmers work, what technologies and tools they use. I went on an internship as a specialist in the development of equipment in the VHDL language. There I met guys who programmed in C++. It seemed to me that software development was closer to me, and at that time I was not very competent in this language. I was recommended a book by Bjorn Stroustrup ( programmer, author of the C++ programming language- Ed.), I bought it, began to read and realized that it was difficult for me, I don’t understand. I put it aside and a year later I returned to it - then it became clear to me what was written in it. During the year, my level improved significantly because I practiced a lot. It seemed to me then that I had already figured out C ++, and I was invited again to the same company, only in another city, in the summer for several months for an internship. Then I went as a C++ programmer and realized that again I didn't know anything. Even now I am a little ashamed of the level with which I arrived then. I didn't understand anything. But it was an interesting experience and I learned a lot. At the university, we had many difficult courses, but they were not related to this. So I graduated and realized that I wanted to be a C++ programmer.
“It was my first interview, but I got accepted”
After university, I found a job on the first interview at XITEX Software. I consider myself lucky. The salary was minimal, but they took me, and I began to gain experience. We have developed a visual editor for the report generator. Later, the company retrained and started making games. I worked for a year in this company and it seemed to me that I already knew everything and I could have another interview. One of my classmates, who works for an IT company in Kyiv, suggested trying to get an interview at his company Codeminders. I passed the technical interview, but they told me that I have too little experience for the client, and therefore they cannot make an offer. I continued to work at XITEX Software. I worked there for two years, and the director of the company said that he was opening another company in Kyiv and offered me a place there. I agreed. I moved to Kyiv and only worked for a week at the Kiev branch of my first company. Codeminders, which I interviewed a year ago, found out about this. I had plus one year of experience, so this time they made me an offer. I ended up changing jobs. It was one of the key companies I worked for because I met a lot of guys there that I still talk to today. I worked at Codeminders from 2009 to 2012. I felt good there, my experience grew, I had many friends. But I decided to change jobs again, because I wanted to get experience in a big company. At that time, only EPAM, Luxsoft and Ciklum were large companies in Ukraine. I tried to pass an interview at Ciklum and realized that you need to prepare for interviews. Before that, I was interviewing for the position of a junior, and at that time he already claimed the position of signor. I realized that despite the fact that I have experience, I am not ready to answer all the questions that are asked in the interview. There are interviews when people are trying to find out what you know, but there are vice versa - what you do not know. There was quite a lot of this “what I don’t know” thing. I started looking online for questions and answers for interviews, pumping. Thus, having prepared, I passed an interview at EPAM: I worked on a project at Barclays Bank. A serious team worked on the project in terms of technical skills - all were seniors. There was quite a lot of this “what I don’t know” thing. I started looking online for questions and answers for interviews, pumping. Thus, having prepared, I passed an interview at EPAM: I worked on a project at Barclays Bank. A serious team worked on the project in terms of technical skills - all were seniors. There was quite a lot of this “what I don’t know” thing. I started looking online for questions and answers for interviews, pumping. Thus, having prepared, I passed an interview at EPAM: I worked on a project at Barclays Bank. A serious team worked on the project in terms of technical skills - all were seniors.
“I decided to work with Java”
In 2014, one of the colleagues I worked with at Codeminders said that there was a cool position at Ciklum and asked if I would like to move there. So I moved to Ciklum and continued to work as a C++ developer. A little later, one of my ex-colleagues told me that there is a wonderful CodeGym startup, and someone is needed who can write tasks. Then there were about 16 levels with tasks, and at the other levels there were only lectures. But there was a catch - I did not know the Java language. I have a younger brother, he is also a programmer, he writes in Java. A long time ago, we talked with him about the prospects of languages, and he advised me to switch to Java. I decided to try. When a programmer already has a lot of experience, it is enough for him to learn the syntax of a new language, I didn’t need knowledge of frameworks at that time. So I switched to CodeGym and became a developer. A couple more programmers were hired with me. One guy wrote tasks, the second was engaged in backend. After some time, we completed the missing tasks, but the guy who was engaged in the backend left, and his tasks gradually passed to us. Gradually, I began to work on the backend. CodeGym had several employees at that time. The main backend developer then was Dima Vezhnin (founder of CodeGym), but he had a lot of responsibilities, so the whole backend smoothly passed to me. Then new guys were added, and we started redoing tasks for CodeGym 2.0 - this was a new version of the system, which, at the end of solving the problem, not only told you whether you had decided or not, but also made hints about what was wrong and what needed to be corrected. When I came to CodeGym, it was just a small resource with lectures and tasks, an important feature of which is checking solutions online. There were no such resources at that time, at least on the Russian-language Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. an important feature of which is checking solutions online. There were no such resources at that time, at least on the Russian-language Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. an important feature of which is checking solutions online. There were no such resources at that time, at least on the Russian-language Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. at least in the Russian-speaking Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. at least in the Russian-speaking Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. and frontend, and testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. and frontend, and testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. I thought that the leaders were resting, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. I thought that the leaders were resting, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer.
Tips for a novice developer:
Find a mentor.
It's great when there is a person who knows the programming language you are learning. When I learned my first programming language, this was not enough for me - to discuss tasks that are incomprehensible with someone. It's good to have a team of like-minded people. On CodeGym, this is solved by the "Help" section.
Practice doing interviews.
I have been both an interviewee and an interviewer, and therefore I know that those who have passed at least 5 interviews look cooler than those for whom this is the first time. It's like in sports: you need training. There is no need to dream about a single vacancy, prepare diligently for it and hope that you will come and get this job on the first try. You need to pass 5-6 interviews - and then your chances of passing your dream interview will be much higher.
Search online for lists of interview questions.
The interviewer needs to somehow determine your level. Therefore, he asks questions and evaluates your knowledge on the answers. These questions can be found, studied, understood.
Practice.
Much more likely to get a job if you have experience. In this regard, the internship helped me. For those studying CodeGym, an internship at the end of the course can help.
When you read something and don't actually practice it, it's quickly forgotten. At CodeGym, tasks are responsible for the development.
Upgrade your soft skills.
There are good specialists, but they do not know how to interact with other people. It interferes with work. It seems to me that it is easier for sociable people to grow their careers, they quickly join the project, because they can come up to ask something, and not try to figure it out alone with something that their colleagues have long figured out.
Do not be afraid to agree to a small salary at your first job , literally in a year, if it is a year of real experience, you can apply for a much larger salary.
So I switched to CodeGym and became a developer. A couple more programmers were hired with me. One guy wrote tasks, the second was engaged in backend. After some time, we completed the missing tasks, but the guy who was engaged in the backend left, and his tasks gradually passed to us. Gradually, I began to work on the backend. CodeGym had several employees at that time. The main backend developer then was Dima Vezhnin (founder of CodeGym), but he had a lot of responsibilities, so the whole backend smoothly passed to me. Then new guys were added, and we started redoing tasks for CodeGym 2.0 - this was a new version of the system, which, at the end of solving the problem, not only told you whether you had decided or not, but also made hints about what was wrong and what needed to be corrected. When I came to CodeGym, it was just a small resource with lectures and tasks, an important feature of which is checking solutions online. There were no such resources at that time, at least on the Russian-language Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. an important feature of which is checking solutions online. There were no such resources at that time, at least on the Russian-language Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. an important feature of which is checking solutions online. There were no such resources at that time, at least on the Russian-language Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. at least in the Russian-speaking Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. at least in the Russian-speaking Internet. Now CodeGym is a big platform with a lot of stuff. I already manage a whole team that deals with backend, frontend, testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. and frontend, and testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. and frontend, and testing, and Android development. Leadership also implies responsibility. I am responsible not only for the results of my work, but also for the results of the team. All people are different: there are more and less responsible, more and less competent. But nevertheless I understand that I have to control everything. When I was just a developer, I thought that the leaders were having a rest, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. I thought that the leaders were resting, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer. I thought that the leaders were resting, just handing out tasks. When I had to take on this role, I realized that it is much more difficult than it seems from the side of the developer.
GO TO FULL VERSION