The last company I worked for the lead dev had the same amount of experience as me but he didnt even know how to implement ajax. The only reason why he was given the title of "lead" was because he was with the company since it started 3 or 4 years ago. These kinds of people love to throw their opinions around as if they have been programming for decades.
I would never hire any of these 2 guys. First of all a senior developer has to solve difficult problems within a constant time. You would know a senior developer because it thinks of the problem in algorithm and not a programming language syntax. 1. Check their code ? How if many of the programmers i know have code under NDA for the companies they work for . My code is hidden 99%. 2. PHP5.x or 7.0 argument. What are you guys smoking ? A large number of code base are on php 5.x and most company management don't want to invest in a refactor to php7 . Have YOU guys ever work in a Tech Company before , cause your point of view tells me , you didn't. 3. Skills for programmers . Oh boy , you guys have ever hired ? Language depended questions are never to be asked of a senior developer , because it is less of a focus at this level. Algorithmic and problem solving skills are paramount . Design patterns and knowledge about the technologies involved is a required.
funny enough I've been coding for about 7 years in which 3 years of them i had to maintained that huge old school applications and refactoring was never on the table also I never published a piece of code on GitHub , it's really weird that they have a single point of entry and fail everyone else based on it , yep these guys are dumb and hype based :)
Yeah, the 5.x vs 7.x thing is stupid. This actually means this guy is a technology-hyped developer. Also talks about how "transition from 5.6 to 7.1 is almost without breaking changes"... oh my god, I can tell he is not senior developer just by that sentence, to underestimate that is crazy... Anyway, off I go.
I just failed a php interview. I said during the “soft skills” rounds that I don’t do tests but want to learn. He said (a developer) that this isn’t a problem. Once I handed my assignment at round 3 they told me I don’t have a basic understanding of tests. Why not make me fault at round 2? I have anxiety about doing job interviews and that’s why I’ve only had 3 in the past 8 years. Just like the comments the person interviewing me called ideas like “100% test coverage” idiotic. I don’t know much about testing, but someone I respect called Gary Bernhard who said that doesn’t seem like an idiot. It really makes me not work at a company when colleagues keep calling things idiotic without explaining why. These comments remind me of that attitude. The guy in the video has a way of doing his job, which is different, but doesn’t mean he isn’t a “real senior developer” I hope to find a better job soon. I have another job interview today which will be the 3rd company I’ve contacted in the past months, but I read that some people contact like 20 companies, which feels very daunting
If I work as a senior, I give my best at work, so I don't have time to contribute to open source projects or my pet-projects. That's why I think that an empty github account is more valuable for the employer.
Hey, there are so many companies in India which are very rigid about using very old technologies like php 5.6. But even Developers are very ready to work with and doing code with latest versions. Then what will your review?
This video and the guy's point are a bit deprecated, as is the version of PHP described by him. :) The "framework-agnostic" code is nearly a utopia in complex real-world projects. It might be, but only for some cases (or you are a big company like facebook able to hire tons of developers to maintain your code). For most cases, you would use the framework, and there are reasons: - Who will maintain your framework-agnostic code? - Is it secure? - Do you have many developers willing to write code in plain PHP and raw SQL? - Do you think the quality of your code will be on the level as if it was written in the framework? PHP could be comparable if your Senior is a really skilled enthusiast, but SQL is most likely not. - Do you think you will write it fast and easily reuse in any framework? C'mon. You can stick at one stack and reuse it in any project that comes in and there's no reason to maintain "framework-agnostic" code because the framework is reusable itself. I'm talking about at least modern Laravel.
When we are speaking about "framework-agnostic code" we mean that code is using a framework but is not code is building on a framework. It's a big difference.
Yes, by using normal standards pieces of code can even be put in composer packages and reused all over the business. This isn't higher level programming either. It's just about using standards that have been around since the 80's or even older. There is no reason to lock yourself into a framework when dealing with business logic.
"Do you think the quality of your code will be on the level as if it was written in the framework?" What do you mean by this? If you can't write quality code without using a framework then your skills are seriously lacking. I don't know who's peddling these lies that Framework code is quality code. Most times, it's just a bunch of nonsense useless abstractions (try reading Laravel's source). And the worst part is, using the framework inevitably forces you to depend on these nonsense abstractions, causing your code to be unnecessarily obfuscated and complex. In fact, I am of the strong conviction that you cannot write truly clear concise readable code using a Framework. Frameworks have their place and it's in RAD and prototyping. That's where their appeal ends. If you are serious about creating any long-lasting software you shouldn't be using a framework.
Watched this twice and stopped at the same point. Not picking someone as senior because they use older versions of PHP is a poor reason. There could be many reasons for this, mostly working with legacy code. IMHO a more senior dev will actually be better here since they will be used to working with a range of versions of PHP and not sure the fancy new stuff.
Bro, there are systems done in 5.4 being used, then if the standard is on version of PHP, what if you got employed and you asked to manage such system? I think there are some true points but the ones they have missed they missed big time
Job Spec: 1) Must have atleast 5 years experience in atleast 2 javascript frameworks... why? So he can solve an algorithm in vanilla C# on a white board. 2) Must know at least 4 programming languages... VERY WELL and he must have an example of this in his Git repo which we may or may not steal to implement somewhere in our own system. 3) Must know how to use Docker and Kubernetes and Flamingo and Castro and a Jumbo Jet. 4) Must Know Git and have atleast 10 projects that we will not look at because we dont have time... but he must have it. 5) Must be able to work in a team, but also independently, he must communicate and be able to ask A LOT of questions, but he must also be able to work independently and ask NO QUESTIONS. 6) He must also be able to read the executives minds and implement features before they even ask for them. 7) He must also be able to write code on a atomic level.
Man, it feels bad being a PHP developer lately. Laravel is an insane framework and the language has evolved a lot it's performance. But seems like people have dropped it before and the language specific content lately has been pretty bad. There is good content still, but some type of content is getting worse and worse. I'm looking for interviews questions advices, and the top videos are either misleading or with just plain wrong advices. The only good thing is that I'm looking for senior roles right now, and the questions at this level seem to be more language agnostic, or open questions about how to implement some stuff that I know how to do on the framework I'm looking for. It's the third bad video in a row on the top PHP related videos to help with interviews questions and stuff like that. I guess the best thing to do right now is study more advanced algorythm stuff and general programming paradigms and stuff like SOLID, design patterns - which aren't as relevants in interviews but they teach you some good logic you can add to your tools belt I guess.
??? First two points are wrong: 1. Business have PHP 5, legacy milion of lines of code and you saying that dev is not senior coz of business history 🤷 and boss decided to not change them 2. Knowing PHP 7 make you better dev due to new features - how PHP would make you better dev ? This depend only on dev potential dev imagination, dev logical approach etc. DOH .
Especially when someone calls HTTP a "pattern"... IT-manager from some utopia world where his senior developers are unable to design/reuse the framework, so instead they're wasting time writing a "framework-agnostic" code.
If he/she can do any of the following A.) Fix your WordPress site B.) Setup multiple server with XAMPP or equivalent. C.) Knows how to properly CURL D.) Knows how to manage private and public states. I might consider him senior or with seniority experience on PHP
THE COMMENTS BELOW SMDH must have not watched the video, he said if he asked the interviewee why he is using php, and he says that his boss told him so , means that not a good reason DUH
Can you stop asking for git* ? A lot of PHP developers are working for companies working with closed code, which is stored in-house. There will be nothing public in git*. That's just idiotic. Just talk to the guy. This is coming from a (currently) 37-year old dev with > 15 years of experience. What I have in git are a few changes of public libraries.
