a big company as .net dev for the financial field. Too much Legacy code, i m not coding at all. I m using datastage and ssis tools to create batch process and that s not what i want. Now, i have accepted a work for a little and tiny company, just a few of employes, but they re working with Java, angular, spring and more "newest" technologies. The salary is the same but i m switching from a multinational to a very Little company. It Is the right choice? What do u think about it? What i was thinking is that it is Little, but still i can improve my skills better than now... Some advice please? @dburyak what do u think about it?
I am interested one thing. How much is your salary?
It it's totally your decision. Do only what you feel good for you. "listen to your heart" ))) Personally, I don't like big companies. Much buroucracy, less opportunities if you are unlucky with project/team/relations/etc from the very beginning. However, if you're lucky, then this is the opposite. Big companies = many (not all) big projects = legacy code, maintenance, old technologies. "If it works then don't touch it" is fundamental for huge projects, so you're inevitably going to stuck with outdated technologies. This may be ok for many people, because, it's like a comfort zone, you don't need to learn many new things. This may sound crazy if you're 20-25, have just graduated, but things are very different when you're older, have family, kids, old parents, etc. Your attitude to the work changes, priorites are revised. Small companies is the opposite. Definitely, you would get more skills with small company and new technologies. But big companies with legacy code also give you some unique skills (work with huge codebase, bad design identification, work with scm, collaborating with many people, conferences, etc.) But what I can suggest you, make the decision only after you get as much info as possible. Ask around for insider info about the company/department/team/project, even this may be enough to decline or accept an offer. During the interview get as much info as possible, what's the project about, technologies used for the project, what you'll be doing, how big is the team, who are you going to work with (I mean how much senior/junior/middle devs), which teams are you going to collaborate with, ask to show you your work place, get acquainted with your potential team lead (most probably the person who is interviewing you), etc.
Обсуждают сегодня