Most annoying thing ever is using google search on safari iphone. They constantly ask you to switch to chrome with the default button highlighted to open chrome/app store. So annoying.
If passing their interviews isn't the same as being a good developer, then those people have to not only admit that the people they hire may not be good at the jobs they are hired for but they themselves aren't good at the job they sell themselves as doing. It's obviously easiest to accept an explanation that doesn't require them to reach that conclusion.
in fairness to some interview processes there are ways you could legit pass a valid interview and then short change the job. We do a problem scenario / proposed solution that's shared a few days in advance. Good candidates (and good frauds) can ace this with strong technical skills, relevant experience and maybe an hour or so of prep time. We'd take this as strong signal, because (and I'd hope more companies do this) we're optimizing for talented candidates, not minimizing people who are going to work multiple concurrent jobs.
> but they themselves aren't good at the job they sell themselves as doing.
In my opinion and experience, being a competent developer and being a good interviewer are even less related than being a competent developer and being a good interviewee (and the latter are already very unrelated).
I really like Gemma 3. Some quantized version of the 27B will be good enough for a lot of things. You can also take some abliterated version[0] with zero (like zero zero) guardrails and make it write you a very interesting crime story without having to deal with the infamous "sorry but I'm a friendly and safe model and cannot do that and also think about the children" response.
Qwen3 and some of the smaller gemma's are pretty good and fast. I have a gist with my benchmark #'s here on my m4 pro max (with a whole ton of ram, but most small models will fit on a well spec'ed dev mac.)
My pessimistic take on it is in the future code will closer to AI where its just a blackbox where inputs go in and outputs come out. There will be no architecture, clean code, design principles. You will just have a product manager who bangs on a LLM till the ball of wax conforms to what they want at that time. As long as it meets their current KPI security be dammed. If they can get X done with as little effort as possible and data leaks so be it. They will get a fine (maybe?) and move on.
As far as I know there aren't many ways to have a completely full stack project. The typical laravel app is a server-rendered app that happens to have a bit of interactivity coded in js.
A Next.js app can generate components server-side and then modify then reactively (in a functional programming style, not with jQuery hacks) on the front-side.
I know right? I sometimes get jealous of laravel PHP folks, but then again JavaScript is the only language I have advanced proficiency with, so what can I do.
I'd venture a guess that other languages might be easier to learn because of the advanced JavaScript skills.
ECMAScript inspired languages (of which JS is one) are plenty.
Laravel is awfully a funny joke that any devs who follow opinions f what they heard about what was "good" or "bad" totally miss out on what's going on there.
I find it's hard to keep things simple, and easy to let things get complex. That's before complexity arrives from the user's needs on it's own.
