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…
Interview with Senior JavaScript Developer 2024 [video]
21–30 of 75 posts
Re: Interview with Senior JavaScript Developer 2024 [video]
#22Re: Interview with Senior JavaScript Developer 2024 [video]
#23Re: Interview with Senior JavaScript Developer 2024 [video]
#24I 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…
There’s been a lot of movement in this direction for CSS which is great, but it needs to happen in HTML and JavaScript too. Just a few cycles of implementing popular libraries as base browser functionality and adding better widget primitives would do wonders to reduce complexity and bloat.
Re: Interview with Senior JavaScript Developer 2024 [video]
#25Who 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.
In a more serious note: I don't think the language matters that much when working in legacy codebases. What matters the most is the (usually undocumented) business logic that one needs to decipher based on the code. I'll take any day of the week a documented PHP project from 2011 than any Go/Rust/TS/Kotlin undocumented project of 2024.
Re: Interview with Senior JavaScript Developer 2024 [video]
#26turned out to be prophetically true in many many ways.
Re: Interview with Senior JavaScript Developer 2024 [video]
#27Re: Interview with Senior JavaScript Developer 2024 [video]
#28Who 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.
Re: Interview with Senior JavaScript Developer 2024 [video]
#29"we push on save"
Re: Interview with Senior JavaScript Developer 2024 [video]
#30I 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…