Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Interview with Senior JavaScript Developer 2024 [video]

youtube.com

Post reply on HN
Print view View original

31–40 of 75 posts

Re: Interview with Senior JavaScript Developer 2024 [video]

#31

Post by nextworddev »

egeozcan wrote: post #13
nextworddev wrote: post #9

Earlier quoted context omitted.

It’s like dealing with the old Angular 1 and Meteor projects from 2015

Those are actually easy. The ones using the first versions of React with custom state management and weird conventions however, are a different story. Those, and debugging jQuery UI problems. I digress but in my career of using every technology possible, the pain I had debugging a huge (HUGE) jQuery UI project could perhaps only be matched by trying to make NHibernate (Hibernate ORM but for .NET) behave in some compl…

JqueryUI… that’s a blast from the past. I’m guessing it’s still used out there.

Re: Interview with Senior JavaScript Developer 2024 [video]

#33

Post by dclowd9901 »

dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

It’s not the same as the microservicesageddon (and yeah we were part of that too).

What I’ve been noticing is backend becoming incredibly slow and kludgy and there’s a want for FE for work around it. Since you can’t bleed a rock, we’re creating these incredible and evil machinations across everything but the server->db layer in order to get the page to load as quickly and efficiently as possible.

Frankly, we should just dump the servers and let the FE query the db directly. We’d probably do it fucking better anyway.

Re: Interview with Senior JavaScript Developer 2024 [video]

#34

Post by dclowd9901 »

triyambakam wrote: post #14
dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

I think the editing style is stressful. It could be funnier if it were slower paced.

It actually reminded me a lot of Jonathan Krisel’s directorial/editing style (Portlandia). I think both this video and that show are hilarious.

Re: Interview with Senior JavaScript Developer 2024 [video]

#35

Post by rezonant »

ramesh31 wrote: post #12
dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

>And so with server components and Nextjs they’ve reinvented PHP. Except worse. There will be PHP-7 monoliths out there running on Apache until the heat death of the universe. Try updating a Node project that hasn't been touched in two years.

To be fair, a lot of those PHP monoliths aren't even using Composer, and regardless updating them would probably be painful as well.

That being said, just installing old Node.js projects can be painful, unfortunately. It's got a lot better with newer NPM versions that use lock files by default, but it still leaves a lot to be desired. Often updating the Node project is the only way to get it running, because somewhere in the stack someone broke semver, or your OS is newer and some native extension does not compile on the new version, or you need to use an ancient Node.js to run it because it depended on some behavior that was deprecated and removed in the 5 Node.js versions released since the project was written.

A particularly notable thing recently is that newer Node.js doesn't support older crypto types, breaking most dev servers built for older Node versions. This has been a pain lately.

Re: Interview with Senior JavaScript Developer 2024 [video]

#36

Post by bee_rider »

triyambakam wrote: post #14
dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

I think the editing style is stressful. It could be funnier if it were slower paced.

The joke is just that JavaScript is silly and over-complicated and build on a billion different libraries that update every 30 seconds, right? IMO it would be funnier if it were about half as long.

The weird cuts are part of the gimmick. I think part of the joke is how stressful it is to listen to.

Re: Interview with Senior JavaScript Developer 2024 [video]

#37

Post by jacobsimon »

beepbooptheory wrote: post #18
whoknowsidont wrote: post #17

Earlier quoted context omitted.

>that people were using React to build websites, when React wasn’t designed for that problem. It was designed for SPAs. React generated HTML on the server from the very start with Node.js. You always had some form of hydration, even before there was an explicit API and process for it. It was built by Facebook... to build a highly utilized and extremely popular website. React had pretty popular examples and integratio…

Idk if this is charitable. To gp's point: isn't the website of Facebook a SPA? The overall point isn't that React et al have no place, its just that they became so prominent from the changing face and market of the web itself, that somewhere a long the way we forgot it could be any way else. To the point that it is now molding js development in general.

If Facebook’s website can be characterized as a SPA then wouldn’t most websites fit the definition of a SPA? Except the most static of websites like blogs.

Re: Interview with Senior JavaScript Developer 2024 [video]

#38

Post by rezonant »

dclowd9901 wrote: post #33
dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

It’s not the same as the microservicesageddon (and yeah we were part of that too). What I’ve been noticing is backend becoming incredibly slow and kludgy and there’s a want for FE for work around it. Since you can’t bleed a rock, we’re creating these incredible and evil machinations across everything but the server->db layer in order to get the page to load as quickly and efficiently as possible. Frankly, we should j…

Frontend only devs who know the first thing about efficient queries are exceedingly rare.

Solutions like Firebase that do exactly what you are describing are extremely expensive and just as limited in terms of functionality, and properly designing security for them is quite difficult. For quite awhile I was on that train until I just couldn't justify the price and limitations, and my frontend stack to deal with those problems became excessively complex.

Re: Interview with Senior JavaScript Developer 2024 [video]

#39

Post by [deleted] »

dimal wrote: post #11

I couldn’t make it through. It’s funny but also stressed me out. I feel like the front end web dev community is going through its equivalent of the microservices/kubernetes madness that overtook the server devs in the past few years and they’re making everything 10x more complex than it needs to be. Like, server side React frameworks like Nextjs solve a problem that never should have existed in the first place — that…

[deleted]

Re: Interview with Senior JavaScript Developer 2024 [video]

#40

Post by rezonant »

hu3 wrote: post #8
gjsman-1000 wrote: post #5

Who here wants to work on a minimally-maintained PHP project from 2011? Nobody? In 10 years from now, this JavaScript crap will be just like that PHP project is perceived today. Except it will be much worse , because the PHP project didn’t have dependency hell like this. At least the PHP project wasn’t also your phone app.

The future is already here. As a tech lead, consulting for one of my clients, I have to oversee the maintenance of three JS-heavy projects (backend too) that are imploding under their own weight of technical debt. And a good part of that are dependencies.

For a long time I worked at a client driven development shop, and we picked up lots of codebases from other developers. There were apps in PHP, Java, .NET. All of them were buried in technical debt. You can take any programming language and build a project buried in technical debt.
Post reply on HN