If you've been working in nothing but PHP, you assumedly know web dev. HTML, CSS, Javascript, the principles of APIs and REST, Database access, etc.
If you have strong fundamentals in all of those, the language abstractions on top of that should be very straightforward for you to pick up.
People will blast me for this, but my honest advice is "fake it till you make it". If you can confidently convey your expertise in the interview, and pass the tech screen, and rapidly get up to speed if/when you're hired, then that's all that really matters. Most job listings don't tell you the negative stuff either.
How does the company you're applying to know what you worked on at your previous roles? They don't. Don't tell everyone all your sins. Vanilla PHP and cruddy WP template work, all deployed with FTP? No, you worked on Laravel with React, and maintained the CI/CD pipelines for deployment. Don't sell beyond your means, but appreciate that if you were stuck working on garbage and they refused to let you use best practices, you have to look out for youself.
IMO this was a reasonable baseline... maybe ten years ago =/ These days companies are swarmed with so much expertise, especially after the FAANG layoffs, "I know some basic web dev" won't get you anywhere. You won't even get a rejection email, much less a tech screen.
It's a really saturated space and a lot of businesses are pretty cautious right now after the layoffs of these last couple years.
Legacy support, basically. You're hired to maintain some key legacy monster created by people long since fired, and there is no option of refactoring it due to sunk cost fallacy by the business.
So, you're stuck just doing nothing but little "keep the lights on" tasks, your only job is to keep the buggy mess running, and you have little-to-no opportunities to modernize or do any best practices due to the limitations of the legacy monster and total lack of interest on the business-side.
Very cool stuff, and great work. Minor UI nitpicks (my personal bugbear):
- Lesson content section has unnecessary horizontal scrollbar visible
- No visual distinguishing or handling for scrollable area (vs the finished display area) had me trying to scroll with my mouse hovering on the lefthand side often, and momentarily confused why it wouldn't go. Make the whole main body section scroll the content, ideally.
Yes, I was thinking of fixing the second point, but then I was annoyed with it and left it like that. If I knew that it blows up here on Hacker News I would have fixed it.
I'm not sure where you see horizontal scrollbars though. Are you on Windows?
If you have strong fundamentals in all of those, the language abstractions on top of that should be very straightforward for you to pick up.
People will blast me for this, but my honest advice is "fake it till you make it". If you can confidently convey your expertise in the interview, and pass the tech screen, and rapidly get up to speed if/when you're hired, then that's all that really matters. Most job listings don't tell you the negative stuff either.
How does the company you're applying to know what you worked on at your previous roles? They don't. Don't tell everyone all your sins. Vanilla PHP and cruddy WP template work, all deployed with FTP? No, you worked on Laravel with React, and maintained the CI/CD pipelines for deployment. Don't sell beyond your means, but appreciate that if you were stuck working on garbage and they refused to let you use best practices, you have to look out for youself.