Hello everyone, I know this may sound stupid but I am tired of React. I have been working with React for more than a year now and I am still looking for a job in the market but after building a couple of projects with React I personally think its over engineered. Why do I need to always use a third party library to build something that works? And why is Next.js a defacto standard now. Im learning Next.js right now but I don’t see any use of it unless you are using SSR which a lot of us dont. Next causes more confusion than solving problems like why do I have think if my component is on client or server? I am trying to explore angular or vue but the ratio of jobs out there are unbalanced.

I've been through many web dev interviews, and as a founding engineer, have also interviewed at least a dozen people. The whole process is completely broken.

Getting interviewed myself: Why do I need to explain what happens when you type "google.com" into a browser? I've been asked this exact question at least 3 times. Yeah sure it shows you understand networking, but how does knowing the exact process ever helped me debug a React component with a bunch of extra rerenders and race conditions? My friends are getting it worse. They are either getting asked LeetCode questions that have never showed up on the job in their 20 years in the industry, or getting assigned take-home assignments that take 15 hours.

Interviewing others: I'm convinced more than half the candidates I interviewed were using AI to answer our preliminary questionnaire. And during the interviews, many are likely using AI tools to cheat. At the time Cluely wasn't out yet (thank God), but I've heard people are using it a lot for cheating on interviews now. They'd give some perfect answers, but then when asked to explain why they wrote code a certain way in a project they did, they would completely blank out.

But even when they weren't cheating, I had trouble figuring out what to ask them. The actual work they'd be doing is stuff like fixing weird CSS issues across browsers, or building out a small feature using an external library.

We had some success offering a 2-week trial period to the best candidates, where they work alongside the team on simple tasks for 2 weeks, but this took a lot of time (and money) for our team to conduct.

How has your experience been for web dev interviews? How can the problems be fixed? If you are hiring, have you found anything that has worked and resulted in quality hires?

I always felt like my work laptop (even with decent specs) was way slower than a MacBook, especially when coding or running dev tools. After using a MacBook M1 for a bit, I really wanted that experience for my day-to-day work but my company only provides Windows laptops.

I’d was curious about Linux and my superior was using it.. So I decided to dual-boot Linux Mint on my work laptop and WOW. The difference is night and day. Everything just feels snappier and smoother, and for dev work, it's a lot closer to the MacBook experience than it is from the same laptop with Windows.

After just a week, I don’t want to go back to Windows for web development. If I had known this sooner, I could’ve saved so much time.

If you're in the same boat and your curious, give Linux a shot.

Any similar experience ?

For me it would be cookies especially tracking cookies.

How about you?

Edit: The consensus is in (from this thread)! The biggest pain for us devs is... Javascript https://www.reddit.com/r/webdev/s/npjZ7cAOFs - Now WHERE is it the biggest pain?

I currently have an issue where select menu items on Edge are heavy left aligned, only on Edge.

I got PTSD from the old days of IE

Whenever you are in a hole, just take a breath and be thankful you don't have to fix rare quirks of IE8 anymore

I used to work as a frontend engineer at this scaleup on an Angular frontend. Classic SPA, shipped to web and mobile and had a REST backend that was written in typescript. When I asked if it was possible to become more cross functional and work on the backend as well, I was in shock when they told me they built there entire backend in Next.js. No, not node.js, not nest.js, actual Next.js as in vercel react frontend ssr framework. And crazy thing was, they did not even have a backoffice admin panel running with that next app. Do more companies actually do this?

FYI, I have quit that job for the better.

Hey everyone,

A while back, I saw a post somewhere that said "Sinkedin - a LinkedIn but for posting failures". My brain thought it was a brilliant idea, so I spent my free time building it.

And now, it's live! sinkedin.app

Sinkedin is exactly what it sounds like. A place to post your work screw-ups, career embarrassments, and failures. It also has option to post things anonymously.

A few warnings:

1. The UI: I am not a designer. I tried my best, but please bear with the UI. If you have good taste and it physically hurts you to look at my site, I invite you to make it better. The GitHub repo is here: https://github.com/Preet-Sojitra/sinkedin
2. The Performance: The entire thing is running on free-tier services. It's held together with hope and duct tape. So if it's a bit slow, that's the... uh... "feature" of being a budget project. Go easy on it!

Would love to get your feedback, bug reports, or even just see you post your first failure on there!

For me, !important. It's the CSS equivalent of flipping the table because specificity lost the argument.

What's yours? Which CSS feature makes you sigh deeply and contemplate backend work?

Hey everyone,

I’ve finally shipped all the features you’ve been asking for. If there’s anything else that would make your Reddit life easier or more fun, just let me know!

Features:

1. Feed post deduplication
   • Detection modes
     • Hash – best for memes and static images (≈ 90 % accuracy)
     • Similar – for photos/illustrations only (≈ 99 % accuracy; not ideal for memes). Adjustable similarity threshold
   • Scope – apply entire site or profile page only.
   • Quick on/off toggle
2. Bulk-save viewed media
   • Save images, GIFs, RedGIFs and videos as a single ZIP
   • Edit the download list before saving
   • *(This one nearly broke me—browser security restrictions are brutal 😅)
3. Inline playback for cross-posted videos even when there’s no visible play button
4. Support for old reddit
   • Added infinite scroll

Grab the update from the Chrome Web Store or Firefox Add-ons, give it a spin, and let me know what you think!

Chrome: https://chromewebstore.google.com/detail/reddit-bro/hjpcclcicecepbgndkjadaojdabheccn

Firefox: https://addons.mozilla.org/en-US/firefox/addon/reddit-bro/

I've been reading the spec to try and understand sticky positioning, because despite my 15 years of web dev experience, I've never really understood how it works... but I'm not embarrassed to admit it. Can someone help me understand why this example doesn't act like a sticky element: https://codepen.io/g105b/pen/bNdXYGG

I have to keep the site-nav element within the header because... well, the site nav is part of the header. Semantics.

The way I understand it is that, because the site-nav is contained within a header, the header itself is the scrollable container, so the site-nav is sticky within that, and because the header doesn't scroll, site-nav will never be sticky. That makes sense, but then if I change the header element to custom-header it works as I expect it to.

So I have two questions:

1) If I can use <custom-header> instead of <header>, what CSS properties could I apply to header to make it work? 2) Why? Just why? My little brain can't figure out what's happening, and just when I think I understand it, the change of behaviour with a custom element seems really inconsistent.

I made it to the "signing the contract" stage on a job application but couldn't sign it because their was a clause that allowed the company to claim ownership of ANYTHING (including side projects produced in the evenings and weekends outside of work hours) I built while employed with them.

Both the CTO and recruiter claimed this was a perfectly normal contract, that I was looking too deep into it, and that no one else had objected to this in the last 7 years and that I should sign it.

But to me this was extremely unfair as a contract is supposed to protect the interest of both parties - and I work on a lot of stuff on the side that is as important to me as there code is to them.

I said the contract was to ambiguous and could only really accept something along the lines of "all work produced on your time is yours and all work produced on my time is mine" which they wouldn't accept.

Which basically ended the job application.

This sounds completely unreasonable to me.. am I right in thinking this or is this a standard part of any contract in the UK and I should have just signed it?

How are log analysis websites designed to scale to serve such massive user base? Eg- Warcraftlogs, serving millions of users, each log file have 10-20 million lines of log events, and the website does it within a minute.

As a developer and a gamer, it has always impressed me how Warcraftlogs website (or any such log analysis websites) scales so well.

A basic raw log txt file on an average is around 250-300 MB big, compressed to around 20 MB, uploading & parsing all the log events building analysis all within a 30-40 seconds. While I was able to do this in around a minute, but then a critical feature blocked me. Warcraftlogs allows user to select a time-range and does the analysis of this timerange instantly, in my project I was not storing all the log events to be able to do this, just summizing and storing it.

So I thought of changing the architecture of my application to save all the log events and do the analysis on demand. Sure it works, but question is how do I scale this? Imagine 100 concurrent users accessing 80 log reports, what kind of architecture or design principles would help me to scale such requirements?

I'm still a learning developer, go gentle on me.

TIA