Is it worth it to get a job in a web studio where mainly the completion of sites on cms?

Question

Career in IT

I went to courses, learned html, css, js, php, mysql. In general, a standard set. After and during the course, he actively studied at home, tried. To be honest, I’m ready to work almost for free, the main thing is to get experience in a good team, to work with OOP and all things, you know. About 2 weeks ago I started looking for a job (I compiled a resume in php as a developer) and literally after the second interview they took me to the company ... However, there are some doubts whether I will learn a lot in this place and is it worth getting a job there at all or is it worth looking further? Is cms experience relevant for a future web career?

Answer 1

the question is nothing at all.
You can't learn anything in a team either. especially when she sucks and is badly managed. and vice versa - you can independently grow into a good specialist.
It's just a matter of motivation and your own brains.
I would go and work for a year or more:
1. maybe it doesn't suck: you can work with the same CMS in completely different ways.
2. there will already be experience that you can trump.

Answer 2

Work is not about frameworks, it's about communicating with people. So worth it. And learn at least that not to ask such questions

Answer 3

Work experience is work experience, you work for a year and there you yourself will be hunted, as happened to me. The main thing is that there should be something in the work experience column, this is the HR barrier, so to speak.

Answer 4

You can go go. Test your knowledge. All the same, courses and real projects are completely different things. In extreme cases, no one will stop you from quitting after half a year. There will be work experience and an idea of ​​what they rivet there on these cms.

Answer 5

Relevant. Go. The same 8 Drupal, for example, is made on Symphony. And the layout for WP is generally priceless)))))))))
In fact, it is the work with popular CMS that gives an understanding of how it all works ... and how not to do it)))))))

Answer 6

There is writing beautiful, ideal code, but there is real life and real business tasks, and, unfortunately, in real life it very rarely intersects. With the current level of CMS development, only very rich studios with very specific requirements can afford to make their own system.
As already mentioned, you need real work experience, and having an offer in your hands, it would be foolish to disagree and look for something purely programmer (for this, in Yandex, Mail.ru and others, but there without experience it’s not a fact that they will look at all) .
And finally - learn to value your time, this is a very expensive resource that you need to learn how to sell if you want to achieve something. This is to the phrase "ready to work almost for free", I know many cool specialists who, in order to raise their salaries from 90 to 200 tr. it would be enough just to update the resume, but they underestimate themselves.

Answer 7

Well, you won't know until you try.
No one keeps at work, they don't like it.

Answer 8

You don't have a choice. Go.

Answer 9

To be honest, I'm ready to work almost for free

Never say that. Especially HR. Name the minimum, but still the price for your work.

and literally after the second interview I was hired by the company.

Go ahead and compare. Grabbing the first option would be extremely stupid. You understand what you need from the company, choose the one that will best meet your expectations.
Experience with ready-made solutions is as relevant as with self-written ones. If this is Websudia, then you are most likely to work on projects with clear deadlines and most likely on a relatively fresh stack. If it's not Bitrix, if it's run, it's a trap and no one needs experience with it, except for the same Bitrix developers. The main thing is that in the studio you will gain experience in coordination, understand what high-quality processes are (or how painful it is when they are not) and that 50% of web development is communication and defining requirements, not writing code.