News for hackers. Stuff that matters.
Re:We have used too many levels of abstractions and now the ... by kaba0 on Saturday October 21, 2023 @08:56AM (#37966450)
With all due respect, this is some elitist nonsense.

Sure, a frontend dev who strictly works on that won’t know much about, say, the OS layer. But they don’t have to, it’s not part of their job in any way.

There is no shortage of young people that work on areas that makes them require deep knowledge of many different layers of the stack, it is simply not necessary for every IT-related job. But one can absolutely pick it up if they want to.

Re:We have used too many levels of abstractions and now the ... by bakugo on Saturday October 21, 2023 @09:20AM (#37966604)
> Sure, a frontend dev who strictly works on that won’t know much about, say, the OS layer. But they don’t have to, it’s not part of their job in any way.

The HTTP protocol, HTML and vanilla JS are not "the OS layer", and yes, it's part of your job as a web developer to at least understand the basics of them. There are many so-called "frontend devs" nowadays who literally only know React, and if you asked them to create a basic webpage where clicking a button changes some text in an element without React, they'd be completely lost.

Usually the problem with this kind of developer is not just that they don't know, it's that they don't care. They WILL inevitably run into problems that require this basic knowledge to solve because the frameworks can only hold your hand so far, and instead of trying to figure out what's going on under the hood that's causing their issue, they will instead shrug and go "it's not part of my job" and just write a bunch of garbage spaghetti code in an attempt to work around the issue.

Re:We have used too many levels of abstractions and now the ... by zdragnar on Saturday October 21, 2023 @09:34AM (#37966674)
I think the critique is that you're applying this too narrowly to front end developers.

Pretty much anyone who has been around long enough has met someone with years and years of experience doing exactly one thing, whether that's WordPress or java CRUD or something else where they have blindingly obvious gaps in their knowledge that someone with their experience shouldn't.

The lack of deep knowledge isn't limited to a single field.

Re:We have used too many levels of abstractions and now the ... by pawelmurias on Saturday October 21, 2023 @09:33AM (#37966667)
Shit developers used to cobble something together in PHP and had a bunch of horrid code on the web to copy and paste. Looking up some deeper part of the stack is not that hard for a legit dev.
Re:We have used too many levels of abstractions and now the ... by kaba0 on Saturday October 21, 2023 @11:56AM (#37967880)
There are people who suck at their jobs in every industry. My wider point is that the skills required for a good web developer is vastly different than, say, a compiler dev. The latter is not a “webdev who is a better developer”, they need much more business-knowledge, understanding what the client meant, predicting future requirements, etc.

This is an entirely new business domain, it’s not really trying to be the same.

Re:We have used too many levels of abstractions and now the ... by leptons on Saturday October 21, 2023 @09:10AM (#37966540)
I once worked with a back-end dev who didn't know what RAM was. He knew C# and ASP.NET but couldn't point to RAM on a motherboard or explain what it really did. About all he could describe it as was "temporary storage". Their lack of basic knowledge of how computers work really showed in the crap code they wrote. It was no wonder it was their code that ate up all the RAM on the server because they never put much thought into the hardware it was running on. I know this is anecdotal, but there are plenty of devs just like this out there.
Re:We have used too many levels of abstractions and now the ... by slmkbh on Saturday October 21, 2023 @09:27AM (#37966635)
I talked to a guy who "managed software development", and when I asked him about the resources om their developer machines (some kind of VM), he got angry at me when I laughed nervously when he didn't know what RAM was.

No wonder a lot of modern software is terrible.

Re:We have used too many levels of abstractions and now the ... by paganel on Saturday October 21, 2023 @12:08PM (#37968005)
> but couldn't point to RAM on a motherboard or explain what it really did.

To be fair, the last time I "opened up" a computer and changed its RAM was about 10-12 years ago, and since that time I've only worked on a Mac Mini and on a laptop meant that "opening up" computers became a thing of the past.

Re:We have used too many levels of abstractions and now the ... by leptons on Saturday October 21, 2023 @12:46PM (#37968401)
This was years ago, in a Windows shop, everyone had a desktop PC. Not important that the guy didn't know what was inside his desktop, but it's the lack of understanding of the server hardware his code was to run on that was the problem. In all servers and desktop PCs ~10 years ago, RAM comes as DIMMs and would be easy to locate for anyone with a passing interest in computers. I'm not talking about Apple know-nothing fanbois here.
Re:We have used too many levels of abstractions and now the ... by codegeek on Saturday October 21, 2023 @09:50AM (#37966777)
It is not elitist to point out the flaws in modern web devs who don't know what an HTTP protocol is and the structure of an HTTP request (headers vs body etc). I interview a lot of them who cannot explain the difference between a form submitted directly vs through Ajax but they surely know how to send a POST request through node/express.
Re:We have used too many levels of abstractions and now the ... by sillysaurusx on Saturday October 21, 2023 @10:54AM (#37967271)
I don’t even know the difference between a form submitted through JS vs a browser. Who cares? Unless there’s a problem, there’s no reason to know such things. And I’ve written http webservers by hand.

People here have way too much confidence in their interview questions being a good signal for experience. It’s pretty wild.

Re:We have used too many levels of abstractions and now the ... by codegeek on Saturday October 21, 2023 @11:35AM (#37967657)
"Who cares? "

You are proving my point. You should care.

Re:We have used too many levels of abstractions and now the ... by sillysaurusx on Saturday October 21, 2023 @11:41AM (#37967708)
Why? I’d rather care about ML.

My point is that your question is some esoteric gotcha party question that may as well be out of Trivial Pursuit. But you’re treating it like anyone who doesn’t care is just being a bad engineer. There are countless ways engineers spend their time, and choosing what to work on is the most important choice of their careers. It’s on you to justify the claim that knowing the difference between a JS form submit vs browser submit matters at all, let alone that it’s a distinction that comes up in day to day life.

Re:We have used too many levels of abstractions and now the ... by nucleardog on Saturday October 21, 2023 @12:32PM (#37968260)
The issue isn’t that every single person in the IT field needs to know HTTP in detail. The issue is that people who have invested in training for a role and are applying for a role do not understand fundamental technologies that are essential to that role.

For you that would be trying to work in ML not understanding any of the theory or how it works, but having used OpenCV with some premade models a few times.

For a frontend web developer who, as a large part of their role, will need to communicate with backend systems… that’s not understanding how their FE web application actually communicates with BE systems.

And from experience… yes, this is very common. And it has a noticeable impact on their effectiveness. Trying to debug why some interaction between your application and the BE application isn’t working while thinking the dev tools network inspector is just black magic and nonsense makes your job substantially more difficult.

This does make these people bad engineers. They are not able to understand and solve a huge class of the problems that they face day-to-day and instead (in my experience) often fall back on “just try a bunch of different things until something works for reasons I don’t understand” which is a poor way to approach work and leads to overly complex, buggy, brittle systems.

Re:We have used too many levels of abstractions and now the ... by recursive on Saturday October 21, 2023 @05:09PM (#37970450)
If you're a web developer, form submission is not esoteric trivia, although ML may be.
Re:We have used too many levels of abstractions and now the ... by quesera on Saturday October 21, 2023 @12:18PM (#37968096)
> I don’t even know the difference between a form submitted through JS vs a browser.

I think you do. GP just phrased it oddly.

The distinction is between a traditional HTML form and browser page load, vs XMLHttpRequest.

Ultimately it's all HTTP though and on that level, there is no difference whatsoever.

Re:We have used too many levels of abstractions and now the ... by drzaiusx11 on Saturday October 21, 2023 @12:58PM (#37968509)
I strongly believe tech interviews should be about seeing _how_ a candidate works and less about _what they know_. Everyone has holes in their knowledge, but can easily be filled by training or on the job experience if they have excellent problem solving skills. Maybe they never needed to know the protocol level but can deliver excellent ux results regardless.

I've started nearly every position in my career in a different domain without prior knowledge, including workflows, protocols and the languages that implement them. I may be an extreme case, but we exist and your process inherently excludes us. I've worked in robotics, consumer electronics, healthcare, fintech (not even in that order, although that probably would have made more sense.) I've delivered in each domain as well as my expert colleagues. But if you asked me to implement a LLM, I'd shug and tell you I don't know how, but I _would_ explain my process for HOW I would learn to.

(Edit: typo)

Re:We have used too many levels of abstractions and now the ... by codegeek on Saturday October 21, 2023 @01:11PM (#37968629)
"how_ a candidate works and less about what they know"

I do get your point but depends on the role you are hiring for. I have had candidates get upset at me (for example: bootcampers) because they couldn't explain how to submit a basic HTML form but wanted me to look at their github "portfolio" that was done during the bootcamp with React/Express Code and what not. Their title was "Front end React Developer". That is a problem and I usually wouldn't hire those people.

Re:We have used too many levels of abstractions and now the ... by drzaiusx11 on Tuesday October 24, 2023 @09:16AM (#37998769)
If you're specifically _not_ looking for react front-end developers, then the on-the-job training for those candidates on the position you're filling _can_ be cost (time) prohibitive in certain orgs to "get up to speed." Likely you should filter those candidates out earlier if that's your case. Sounds like you are, but I'd like to also point out that this strategy has it's own costs.

For example, I would take a react developer with obvious gaps and a strong willingness to learn on my back-end services team over a passable back-end dev who was set in their ways (unwilling/uneager to learn new tech, entrenched opinions stated as fact, etc.)

Naturally, my approach is not a one size fits all situation and a great deal depends on org structure and mentorship opportunities being in place for it to work. The benefit being you avoid monoculture "silos", and have more cross collaboration and transfer opportunities between teams (some may call this "full stack", I wouldn't)

Several high performers on my team are "self-taught", work comfortably across several languages today and can pickup new tech easily. They came in knowing their "one stack" at the time. If they were "bootcampers" or not seems irrelevant and somewhat reductive/offensive.

That said, if the candidate in question shows _no_ understanding of their problem domain, can't reason their way out of a paper bag, and get visibility upset from questions when you try and tease that out, that is a certainly a red flag in my book.

With respect to your example given, however, it could be argued that http details because of the abstractions in place inherent in react, aren't critical domain knowledge for what is essentially a UX dev. If they can ship an experience your users enjoy more than the candidate that can recite the HTTP 1.1 RFC and cannot, then what have you gained in hiring the latter other than maintaining a culture of pedantry?

TL;DR it comes down to how much risk your team is willing to take on, as there's always risk inherent in hiring ANY candidate, including those that don't already check all your boxes in regards to tech know-how. I'm merely stating that by overlooking candidates that don't fit your self-imposed mold, you're likely missing opportunities for rewards that can pay dividends when it does work.

Re:We have used too many levels of abstractions and now the ... by moffkalast on Saturday October 21, 2023 @10:02AM (#37966853)
Besides, it's not like getting a CS degree doesn't mean getting acquainted with all layers of the stack. They still teach assembly, C, CPU architecture, low level networking, etc. It's just that most people rather specialize in something far less tedious. And there's definitely more areas to pick from today than had ever been before.