"we push on save"
I've seen this lately... very cringe.
If your tests pass, why not?
Interview with Senior JavaScript Developer 2024 [video]
71–75 of 75 posts
Re: Interview with Senior JavaScript Developer 2024 [video]
#72I thought he was making stuff up - "t3 stack vs t4 stack". But about 2 minutes in, I realized that I'd heard of a few things that he's talking about so I looked it up and they're real! I think it's possible everything he's saying is true, more or less. LOL t3: https://create.t3.gg t4: https://t4stack.com
Wow. I thought he purposefully chose completely nondescript names as a critique of the ecosystem.
Re: Interview with Senior JavaScript Developer 2024 [video]
#73Earlier 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…
NHibernate, the codebase must have been ancient. What is surprising it is still actively being maintained but the documentation examples look just as old and alien.
Re: Interview with Senior JavaScript Developer 2024 [video]
#74only downside is its pumping "quinoa coin" at end, and when camera glances at the interview candidates notes
ah thanks!
must have missed that joke
Re: Interview with Senior JavaScript Developer 2024 [video]
#75I 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…
From my point of view, a lot of trouble could be saved if it were a priority in browser development to reduce the number of libraries and layers necessary to build things like SPAs. 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 primiti…
> if it were a priority in browser development to reduce the number of libraries and layers necessary to build things like SPAs.
But this is the antithesis of FE culture. When FE culture spun up there was a lot of mocking of javascript devs as not "real" devs. I think they felt the need to reinvent CS so that they could show they were legitimate. They never really recovered from that.