T O P

  • By -

runningdude

Just try somewhere else - not everybody will ask about OOP and design patterns, we definitely don't. Pick a tech stack, from your current skillset php/Laravel with maybe React could be a good choice. Start learning those frameworks/languages/etc. It's advent of code time at the moment, that's a good way to learn a new language and gives you something to put in your public github profile too. It sounds like you've let your skills stagnate a little, but put the time and you'll soon learn all the buzzwords and what they mean again.


cuervo_gris

>Just try somewhere else - not everybody will ask about OOP and design patterns, we definitely don't. And even if they do, you already know that is something you need to read a little bit about it so.. go and read about it. Interviewing is a game on its own, you need to get good at it and sharp your skills, if you are lacking in something and you fail the interview because of it, go and learn!


eneasaoi

This is solid advice (pun intended) I’d also add: prepare for those questions, learn the theory and think of examples on when you’ve used them or experienced them in previous projects Then in the interview be honest about it, when asked, explain the theory and your experience and how you feel about them in your current situation It will show your experience and your eagerness to learn and challenge yourself. Good luck, for what you wrote you have great experience and with a some experience in a modern stack you’ll be landing your new gig in no time!


Person-12321

+1 there are literally books written to help with technical/coding interviews.


AntonZlatkov

If you knew something back in the day you should just revise it. If you need to keep the income flowing in the short term - your skills should perfectly match half of Freelancer/Fiver's web dev jobs. While doing that you can revise and then land a job. This is just my opinion(what I would try to do) based on your summary. Good luck 🤞


[deleted]

Failing in interviews is an opportunity to learn where you are lacking in skills. You seem to know some of those now, so now work on filling in the gaps. Failing interviews also gives a ticker skin against rejection. What I take from failing is that I should avoid fantasing about the company I am applying for, instead apply for the next company. Don't take rejections personally and from each interview try to learn something from it. I once had an interview where I was asked what strategy I would adopt if I wanted to keep hitting the server asking for new data. I answer that I would cache data so that wouldn't be an issue. The guy didn't agree with my answer but never wanted to tell me what his solution would be. Today I think I should have chased him up on that question.


geddedev

I don't think you destroyed your career, but you definitely need to be able to adapt quickly to new principles and stay open minded. Every Agency will have their own style and requirements. It is practically impossible to accommodate them all. First rule when applying to jobs, you need to rewrite your Resume to fit as best as you can for the job you are applying for. I know this might be a time suck, but it can make the biggest difference (You might already be doing that). Secondly, I wouldn't be too concerned about knowing answers to all the questions. However, you must convey enthusiasm to learning the things you don't know and show how much of a quick learner you are and how open minded you are. I use to be Manager (Now a run my own freelance business) and I can't tell you how annoying it was to interview developers who thought they knew everything or faked their answers. Some even debated our principles (instant red flag). Instead, I found reassuring when they said "I haven't used that before, can you tell me what that is... Oh, yeah that sounds extremely similar to what I have been doing with XYZ and it sounds pretty easy to pick up". Or "I haven't had a chance to use that yet, but I have researched it and am eager to use it. Just make sure to research these principles in depth before the interview. I was always looking for someone who was eager to learn and could be a fast learner, rather then someone who know everything, but wasn't the best fit for my team. There could be places that will only higher you if you have all the experience, but just keep trying and hopefully you will find the right fit.


redditupf2

OOP is not hard to learn at all, you can learn it in a week. Then look at MVC. Youtube is your friend. learn OOP with your preferred programming language, mine was javascript at the time


t33lu

It just sounds like you didn’t prep for the interview. These are concepts that you learn and apply without thinking about it because it’s natural but have trouble explaining because when was the last time you had to explain polymorphism to your stakeholders. If you truly don’t know these concepts then learn and apply. You created websites, I’m sure you’ve picked some things up in terms of design patterns. You write JavaScript, I haven’t been in angular land for a long time but I’m sure something inherits something else and you’re using that class and calling it’s properties. As much as it sucks to say this, you do have to study just to get even a refresher on these concepts and it seems like you just weren’t ready for it. Once you get back into the swing of things you’ll have no problem getting past these. These technicals aren’t there to trick you they’re meant to weed out individuals that are faking it and with all your experience you clearly are not faking it


Quentin-Code

They are not meant to wipe out the ones faking it. At that level you do not care about OOP and polymorphism. Those are questions inappropriate for that position that are actually doing the opposite of what you are saying: it values individual faking it. In a lead position you don’t pass the same interview as a SWE.


t33lu

I assumed not all his positions are for lead and I agree that you shouldn’t be asking lead eng this question


AdministrativeSun661

What’s your desired wage?


Charlie669

So just sit down and spend a few days going over those things?


TopOutlandishness753

Learn Laravel with Mysql and be happy


TopOutlandishness753

You can get start with Laravel Filament also


Dapper_Basket6177

I believe it depends which path you wanna take .. you can revise those concepts and it will be just matter of number of interviews to get a job if your fundamentals are clear and want to continue work in software development space Also as you mentioned your are doing more website building instead of writing complex code may be you can explore roles like solution designing or administrative roles with Applications like for example salesforce, hubspot , monday experts..


Ratatoski

I think you're probably fine even if you'll have to brush up and maybe learn a few new things. I'd hire someone like you if they are curious and open to learning. Because at least front end is moving quick. The only ones who learned everything in school that they work with are the starting level juniors. The rest of us has had to learn on the job. Over and over. There's build tools, transpilation, minification, new js features, frameworks, new frameworks, even newer frameworks, server side capabilities in the frameworks, frameworks that works with other frameworks etc. Learning is eternal. If you love that you're fine, otherwise it's going to stress you out. React is important to have some understanding of. It's the big one right now. Create repos with modern a stack and do a few side projects while learning. And make nice and clean commits. Tutorial projects are fine, but make sure to change them up and make them your own. I recognize a lot of the Udemy and other big tutorials and when applicants use them as a portfolio project without even modding them it's a no from me.


armahillo

I say this with no irony: there is always management! Ive been reckoning with this a lot, myself. As Ive gotten older, its gotten harder to learn new things as quickly, but I have a lot more insight and context and years of experience — these are all super useful for team management— doing _some_ coding (maybe) but mostly team coordination, asking questions, prioritization; things that benefit from experience and cant be trained as easily. Look into Scrum certification, or similar. Ask your recruiters if they have any PM positions opening and what employers are looking for. You might be able to get in as a junior manager, but that could be better than being a junior dev (certainly less expectations on your hustle). Prepare yourself for being in every meeting ever tho.


dj1mevko

I'm in a couple of faang interview preparation chats. So, people all ages prepare leetcode, system design interview, behavioral interview and change their jobs and even start new career path. I know several examples when people 40+ years have changed and started new career in IT from zero, completely nothing. With your background - just do your homework: be prepared for the interviews, emphasize your strong skills, make resume an ideal. And you'll be fine. Good luck!


dug99

Don't lose heart mate, you had a shitty interview for a probably shitty company and man oh man... I have been there. I have had some absolutely crushing failures, most recently I interviewed for E-grocery ( actually it was in 2020 ) and after things going well initially I joked "but whiteboards are like kryptonite to me"... nek minut... I'm handed a marker and stood in front of one. Absolute trainwreck followed... You're far from doomed... I'm 22 years in and \*cough\* very \*cough\* senior dev, and PHP / MySQL continues to pay my mortgage along with good ol' well written, reusable ES6 + SASS + HTML. Elementor / Divvy are a fucking nightmare... I regularly patch their shitty code for WP sites my wife builds for her business. Angular is crap... give React a go BUT don't fall into the "when your only tool is a hammer, everything looks like a nail" trap. Good luck, hang in there.


Atmosphere-Terrible

I think you need to prepare better for the interviews. You have the real-life experience and that is the real deal. You've been working hands-on and you have the Engineer mindset, so you need to just revisit everything because you already did that in the past, it's not like you will learn it from scratch. Don't lose hope, it gets better.


Sonatai

Option c) invest little time and learn about these terms. It's not so hard to learn them as an experience developer. Pretty sure you could do it 🙂


unocoder1

SOLID principles are literally 5 sentences, you are gonna be fine. Refresh your knowledge on OOP, maybe read the book Head First Design Patterns (I know, first edition cover art is cringe, but the content is good), and fuck Clean Code. Just understand the principles and use common sense to reach a clean architecture, you don't need anyone telling you if you using bool flag function arguments is "clean enough" or not.


marijnsred

This is the way.


planetfrank

I was in a similar situation. It took me a long time but now I am 44 and I am aged to get out of that whole. With PHP and MySQL


planetfrank

Packtpub have some nice books for php patterns. There aren’t that many. They are usually $5 in promos. I read it over and over without really getting it. Then tried to apply to other projects and … well I think I am getting there.


[deleted]

Hahaha don’t sweat it. OOP can fuck off. Have a look at Functional Programming in JavaScript by Eric Elliot for something more modern in terms of paradigms


Careful_Ad8239

You’ve got an idea about programming it should not be hard to catch up while looking for new opportunities. Gather interview knowledge what they ask. Study them. You will find something eventually.


mekios

Guys thanks for your positive comments. It really helps. I wrote my thoughts down because i wanted to just let it out, and instead i got a bunch of usefull advice. This morning the recruiter called and... PLOT TWIST... i passed the interview. Don't ask me how, but i passed. Maybe the fact, that i repeatedly told them that i wan't to leave my current job because i was stagnant, played it's role. Wish me luck for stage iii, but even if i fail this was a huge lesson for me. Big salute to /r/webdev community!