What should junior php know for 2020 and is it worth going to all interviews?

Question

PHP

In general, I'm 28 (I hope it's not too late, although according to the girl who left packing - they won't take you anywhere, you're too old), I decided to go to IT for junior php. Before that, he did not work in this area. There were attempts to get a job last year, at that time knowledge was not enough. Due to circumstances, I could not continue the study. Now I plan to refresh my knowledge again and reinforce all the existing ones.
Interested in answers to a couple of questions:
1) How well should jun know HTML?
2) What should I pay special attention to with php and where is it better to take a task test? Or it’s just stupid to take and make a site with registration based on MVC with some kind of content there, and this may be enough to not be ashamed to show at the interview.
3) Is it worth it immediately after completing the courses and a couple of months of practice to take on the framework? That year I taught Laravel, watched a video of a person from India, where he spoke quite well on this subject. Is there another idea to buy Laracast courses and take them, but I don’t know about the expediency?
4) When I went to interviews, I did not dare to go for everything. I understood that the level of knowledge was not quite sufficient, although I saw certain advantages. It was immediately clear where I was lagging behind and so on. Is it worth going to absolutely everything, even if you understand that you are not quite ready yet, or wait a couple of months, and thoroughly bring it to the ideal?

Answer 1

What junior php should know for 2020

how did you get sick of your 2019, 2020, insanity and nothing more ...
3 letters of such life partners
"there, in one furnace" (c)
Find an employer-mentor, don't care what you will write on, a framework, a free CMS, a studio CMS, the main thing is that you understand the principle of work and can solve problems.

Answer 2

Stop freaking out. A developer is a profession like any other. There is no need for super-skills.
Study, do projects, go to interviews. If they don't take it now, they will take it in three months.
28 old? Lol.

Answer 3

People need to understand one simple thing. Programming is not something you know, programming is the ability to solve problems. If you have this ability, you will acquire knowledge and work sooner or later, and sooner rather than later, you will find it. If there is no this ability - then how the chip will fall. There are mentally retarded employers who put knowledge ahead of coding ability.
Just make yourself a project that interests you. Make a website that interests you. You will see that it is too long to write it in pure PHP, then you will try frameworks, and you will see that frameworks make it easier and faster to write code. Yes, technologies are needed because they make life easier, but studying them as such without real application will not make you an expert. Writing your own project will make you a specialist.

Answer 4

I’ll tell you by my own example, I started working as a programmer at 28, I won’t say that my knowledge was great, I knew layout, I understood OOP, CRUD operations, I was offered a job as a Bitrix developer to support sites, I spent 4 days studying Bitrix from video lessons, I didn’t understand a lot but slowly figured it out. Another nuance, in my city there are no vacancies, I had to look for a remote job. Maybe you should also start small and not grab onto frameworks. Look at the vacancies from the series "need a man orchestra" for the first time to gain experience, such ones are also suitable.

Answer 5

(I hope it's not too late, although according to the girl who left while collecting things)

I partially understand it, you reveal your problems to the audience, which are not important to anyone. Because everyone has their own.
one.

How well does jun need to know HTML?

Good enough to understand what semantics is, what accessibility is and not sculpt divwhere you can put p, span, aside, nav
2.

What to pay special attention to in php and where is it better to take a test task?

To begin with, it is worth learning the basic operations in the language (functions, loops, working with arrays), I advise you to look in the direction of the Hexlet PHP course, at one time I went through it myself. There you will get acquainted with basic operations, such things as composer and so on.
3.

Is it worth it immediately after completing the courses and a couple of months of practice to take on the framework? That year I taught Laravel, watched a video of a person from India, where he spoke quite well on this subject. Is there another idea to buy Laracast courses and take them, but I don’t know about the expediency?

You seem to have problems with the desire to finally go to work. A year ago, you were learning Laravel. What is the problem a year ago to look for a job as a June? Why such a jump in time that a year later you decided to learn frameworks again.
4.

When I went to interviews, I did not dare to go for everything. I understood that the level of knowledge was not quite sufficient, although I saw certain advantages. It was immediately clear where I was lagging behind and so on. Is it worth going to absolutely everything, even if you understand that you are not quite ready yet, or wait a couple of months, and thoroughly bring it to the ideal?

A bunch of cockroaches in your head, stop being afraid, you don't have to know everything ideally. This is not a poem by Pushkin or Mayakovsky. You must understand the concepts and mechanisms of development, with which tool and how it is done. I'll tell you a big secret. Everyone, everything, always googles. They also write shitty code. Therefore, start with the fundamentals, google test options (or interviews) for a PHP junior and go through 3-4-5-10 times. I think 6 times will work.

Answer 6

1. If a reference point is purely backend, then it is not needed at all, although for general development it would certainly be a plus to know the basics
2. Try to study everything that comes in, courses, books, articles on the Internet. Definitely without practice. And about the courses, it helps a lot when you have someone to ask, but such a person may already appear when you get a job
3. That's how you feel that it's already possible and then take the frameworks.
4. Worth going for everything.
Ps don’t worry about age when you came to your current place of work there was an employee of 35+ years in the profession and he gave odds to the young

Answer 7

Ability to write functional tests using the bridge of your framework.
This requirement has many dependencies.