So if you do not know
Posted: Sat Dec 28, 2024 5:59 am
It is better to answer something like this: "I do not know this, but I know this and this in Spring" and so on. This way your knowledge, albeit small, will be noticed. I got a job at a browser game development company (I will omit the name of the company so that the management does not get angry), I am developing the back-end part of the game.
That is, I work with the database, write add-ons, add features, bosnia and herzegovina whatsapp number database connect the back and front. I also work on algorithms, use Spring (everything is standard: markup, beans, parsers). I work with Tomcat, PostgreSQL and Hibernate. In general, I support and improve the project to the best of my ability and the tasks assigned to me. For now, I am a junior. The first 2 months of work I did not understand anything, deadlines were tight, I sat for 12-14 hours on my own initiative, but .
.. it bore fruit. True, I have a serious mentor (a cool senior with fifteen years of experience). He says: "Figure it out yourself, look for how it works," that is, he does not help, and if he does, then very rarely. And you know what? It is right - to force the programmer to think for himself. If from the very beginning I had not toiled for days and nights, but asked everything in a row - this would not have led to any professional growth.
That is, I work with the database, write add-ons, add features, bosnia and herzegovina whatsapp number database connect the back and front. I also work on algorithms, use Spring (everything is standard: markup, beans, parsers). I work with Tomcat, PostgreSQL and Hibernate. In general, I support and improve the project to the best of my ability and the tasks assigned to me. For now, I am a junior. The first 2 months of work I did not understand anything, deadlines were tight, I sat for 12-14 hours on my own initiative, but .
.. it bore fruit. True, I have a serious mentor (a cool senior with fifteen years of experience). He says: "Figure it out yourself, look for how it works," that is, he does not help, and if he does, then very rarely. And you know what? It is right - to force the programmer to think for himself. If from the very beginning I had not toiled for days and nights, but asked everything in a row - this would not have led to any professional growth.