5 ms·
Interview with Senior JavaScript Developer 2024 [video]
- wpasc 3y agoI know HN is more serious that humorous, but I love his interviews
- zamalek 3y agoThere is always an underlying truthful critique to his stuff.
- dvh 3y agoMy favorite is when he's reciting job requirements: "SQL, PHP 4, 5, 6", then looks closer and says surprised "6?" https://www.youtube.com/watch?v=6KefznccsY0&t=87s https://www.youtube.com/watch?v=6KefznccsY0&t=87s
- gjsman-1000 3y agoWho 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.
- holoduke 3y agoI like to work on old legacy systems from the 00s. They are all relatively simple without too many dependancies. Code is often spaghetti, but its often also not having 20 layers of abstraction. Nowadays code is so damn abstract with layers of enheritance, delegates, messaging etc. Very difficult to understand apart from the makers. Give me old code. I like it.
- egeozcan 3y agoLet me introduce you to JSF and the magic templates. Not all old code is equal, and not all JS-heavy projects are bloated.
- hu3 3y agoThe 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.
- nextworddev 3y agoIt’s like dealing with the old Angular 1 and Meteor projects from 2015
- egeozcan 3y agoThose 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 complicated (but CRUD after all) data-heavy projects.
- nextworddev 3y agoJqueryUI… that’s a blast from the past. I’m guessing it’s still used out there.
- egeozcan 3y agoYes. Perhaps not in the public web but there are so many internal tools using it. It has a lot of issues but the average jQuery UI project is so old that some users will actually complain if you fix bugs because it breaks their workflow (speaking from personal experience)(there was an xkcd for this I think).
- neonsunset 3y agoNHibernate, 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.
- spookie 3y agoI've worked on one last year. A JS developer was surprised at how fast everything was.
- dakiol 3y ago> Who here wants to work on a minimally-maintained PHP project from 2011? 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.
- mv1234 3y agohttps://www.youtube.com/watch?v=y8OnoxKotPQ https://www.youtube.com/watch?v=y8OnoxKotPQ Similar video. I've seen their channel described as "the best workplace videos I can never show my coworkers."
- dimal 3y agoI 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 people were using React to build websites, when React wasn’t designed for that problem. It was designed for SPAs. And so with server components and Nextjs they’ve reinvented PHP. It’s like, we could have skipped a five year step and used PHP/Rails/whatever.
- k__ 3y agoYes, I also have the impression that the whole SSR story is a step backwards. Especially with the prevalence of CDNs nowadays.
- ramesh31 3y ago>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.
- rezonant 3y agoTo 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.
- 3y ago
- bugbuddy 3y agoHard to relate because they didn’t mention the BUS.
- evbogue 3y agoThis is a follow up to Interview with Senior JS Developer https://youtu.be/Uo3cL4nrGOk?si=6e8Aks_xmUSdYC6u https://youtu.be/Uo3cL4nrGOk?si=6e8Aks_xmUSdYC6u from two years ago.
- abledon 3y agoYou can see the Krazam influence on the whiteboard shots lol.. I hope this format picks up more steam.
- edem 3y agoI do trunk based development. i have a script named "c" that does `git add --all && git commit -m "progress" && git push` and another one named "p" that does `git push prod`. apart from that i use effect-ts and express with kita.js and a few small libs and do persistence with pg. the rest is written by me and somehow i don't feel the need to add anything to it. not everybody needs k8s, microservices, and all that crap that will fail at the worst possible moment.
- throwaway4good 3y agoLooks good to me.
- Maxion 3y agoI'm stealing this.
- 5350-uiop-1130 3y ago"move fast and break things" turned out to be prophetically true in many many ways.
- biccsdev 3y ago"we push on save"
- igorguerrero 3y agoI've seen this lately... very cringe.
- ukuina 3y agoIf your tests pass, why not?
- bogdan 3y ago> Validbot It's actually valibot. Unwatchable.
- hyrepire 3y ago> we ship on save is a great line
- vlod 3y agoIt's scary how much of that I understood. smh
- dunk010 3y agoIn case you want another of his videos and know much about eMacs then this one had me on the floor: https://youtu.be/urcL86UpqZc https://youtu.be/urcL86UpqZc
- ornornor 3y agoYep. I’m changing careers. Used to love what I do. Not anymore.
- jauntywundrkind 3y agoThis was really fun. I dunno if t3/t4 are based in anything specific but most of this is surprisingly sharp, while also being ridiculous. What surprises me most is that we have tried so many things, except most apps are a handful of bundles, and even more wildly, almost all work happens on the main thread still! React's vdom has given us a very nice & performant Immediate Rendering (vs Retained Rendering) view, and we've dabbled with unidirectional data flow, signals, whatever graphql is, and other abstractions, but the core "where and how does work happen" model hasn't been much iterated on. Now we are very busy figuring out React Server Components and doing other page rehydration works, which indeed can shift much of the work out of main thread. But the client has been somewhat stuck, somewhat patterned into monolithic main thread patterns forever, and few have tried to push beyond that. Even with wasm happening, it still seems like few are using web workers to divide up where the work happens, which feels like it could be such a giant win for keeping the page crisp & responsive, for thickening the client effectively.
- deleted 3y ago[deleted]
- ccorcos 3y agoI 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 https://create.t3.gg t4: https://t4stack.com https://t4stack.com
- shepherdjerred 3y agoWow. I thought he purposefully chose completely nondescript names as a critique of the ecosystem.
- abledon 3y agoonly downside is its pumping "quinoa coin" at end, and when camera glances at the interview candidates notes
- sambazi 3y agoah thanks! must have missed that joke