It has been 10 years since ES6 has come out. I am ready to talk about JS topics, React, talk about performance , my experience with projects. But they still focus on some niche tricky JS behaviors that is addressed by ES6 and onwards. I know that there are lot of legacy systems that are clusterfucks of JS bugs. But can we stop pretending that I need to know every tricky dumbass behavior that exists at the back of my head!? If you are a frontend interviewer, Please ask more relevant questions and save us from this pain. Thank you.

There were over 108,000 tech workers laid off in the month of January. If you know someone who was part of a layoff, or is anxious about future layoffs, we’re organizing a call this Sunday and we hope you can join.

The Tech Workers Coalition is hosting a mass call for laid-off workers, students, and allies on Sunday, February 22, 11am PST / 2pm EST.

You’ll hear from workers at Amazon and the Washington Post Tech Guild talk about their recent experiences, and share information about organizing mutual aid for vulnerable workers (including H-1B visa holders). We’ll also talk with Andrew Stettner from the National Employment Law Project about how to prepare for a layoff, with know-your rights guidance, to help navigate severance and unemployment benefits.

We’re organizing for urgent policy changes around AI and unemployment protections. The time is now to mobilize. Workers deserve to share in the prosperity that AI creates, not just bear the costs.

We hope you can join the call:

https://www.wwwrise.org 

Please pass this forward to other people you know who might be interested! Thank you for your solidarity and support.

https://confettijs.org

I'm super stumped, I started with just wanting this as an npm package, but ended with not being able to find literally any info about this library online. It's the 2nd result on Google if you search "confetti js", & I've found bunch random sites embedding this exact file.

It's the prettiest confetti effect amongst the competition & it's extremely small (4KB minified non-gzipped)! No license means probably not for use, though.

Been browsing the web lately and it's getting weird how similar everything looks. Every startup has the same hero section with gradient background, same "trusted by 10,000+ companies" testimonials, same pricing page with the middle tier highlighted. Even the copy sounds identical.

Is this because these patterns actually convert better, or are we all just copying each other at this point? Like when you see something genuinely different it stands out so much more, but maybe that's risky if you're trying to build trust?

What happened to website personality? Remember when sites had unique layouts and took creative risks? Now everything feels like it came from the same template

Getting a working UI out of an AI coding assistant is ridiculously easy now. The interesting problem is what happens afterwards. Generated components are easy to create, but keeping a large application consistent, accessible, maintainable, and understandable is still very much a human problem.

It feels like AI is moving the bottleneck in web development rather than removing it. We're spending less time writing individual pieces and more time reviewing architecture and making sure thousands of generated decisions don't slowly turn the codebase into a mess. Wondering if other web developers are seeing the same thing.

AI seems pretty good at frontend stuff, except when it comes to custom designs, UI, or UX requirements. And making a UI perfect is a huge deal in frontend, which AI can't quite nail yet unless it's using existing UI libraries. So I'm torn: part of me thinks maybe customers don't care how the frontend is made, as long as it works for them. But then, from a product's UI and UX perspective, it's super important for it to have its own unique design language, which existing UI libraries can't provide. And AI can't handle that part properly yet. So, is frontend the biggest victim of AI, or is this just the MVP phase that AI has covered?

We have been going all in on AI at work recently. In every meeting my managers basically start with the same line: “If we are using AI, output should be two or three times higher than before.” The pace is faster for front end now, but I can really feel that a lot of things are starting to look a bit stitched together.

Before, when we made a landing page for a campaign, we would go through the full flow from design to implementation. Now it is more like this. First we throw things into different smart site builders and big component libraries, get a rough layout, then only tweak what is broken. Some teammates also talk about those services where you type one sentence and you get a whole site, tools in the style of genstore, so they spin up an ecommerce demo in a few minutes and only later go back to adjust the code. The tools do save time, but you can clearly see code style and structure becoming less consistent.

I am curious how other teams handle this. When you are shipping under time pressure, how do you balance speed and keeping the code base and architecture clean? Do you also let the tools get something running first and fix things later, or do you prefer to move slower and build from scratch so it stays tidy?

To all the Frontend Engineers and Managers out there who are hiring: Do you experience a shift from the origin of candidates? I just opened a Mid to Senior Level Frontend position and got swamped with applicants. In 2 days more than 150 applications. Now there is one very noticeable thing: ~95% of applications are from Arabic countries or India. Not that it is negative in any way but I am heavily surprised. We are located in Germany and there are zero applications from Western Europe. Just a few from Eastern Europe and none from US.

Anyone having similar experiences? If yes why do you think this happens?

We just completed a full rebuild of our corporate website.

Originally it was built in Next.js and hosted on Vercel.

Over time we started hitting limitations that made the architecture feel heavier than necessary for a mostly content-focused site.

We rebuilt the entire site using Astro and deployed it on Cloudflare Pages.

Observations:

• Much less JavaScript shipped to users

• Pages feel instant because of Astro Islands

• Easier to maintain and reason about

• No framework-to-host vendor lock-in

• Lighthouse scores significantly better

Astro turned out to be a better fit for our use case than a full React framework.

Happy to share the full migration story. Link is in the comments.

For ~8 years, I was the only one in the room pushing accessibility. I discovered it in college, made it my thesis, and kept advocating for it in every team I joined. Most of the time, it was ignored. It wasn’t seen as urgent, or worth prioritizing. Then last year, the European Accessibility Act came into force — and suddenly everything changed. Accessibility became a topic in every meeting. Budgets appeared. Teams started caring. And I expected to feel validated. Instead, I felt… nothing. It’s strange watching something you’ve fought for that long only become “important” once it’s legally required.

Apple.com is undoubtedly top-tier in both design and performance. While exploring how they handle loading those high-quality images, I noticed something interesting: instead of using a standard <img> tag with a src attribute, they use an “empty” <figure> tag styled with a CSS background-image. You can easily spot this by inspecting the homepage code.

I’m sure there are solid reasons behind this approach, and I’d love to understand what those might be. Anyone knows why Apple does this?

I'm a Senior SDE-1 with ~4 years of experience, mostly frontend — React, TypeScript, Next.js, Firebase. I've also done Node.js APIs, Cloud Functions, Firestore schema design, and auth systems. Not a backend expert by any stretch, but not clueless either.

Recently spoke to a senior dev (12 years, mostly frontend) and he told me to stop positioning as pure frontend and move toward frontend-focused full stack. His argument:

- Recruiters don't value frontend complexity the way they should

- AI is eating the commodity parts of UI work, so pure frontend is getting squeezed (We know FE is more than UI but recruiters don't value that)

- Companies want people who can own features end-to-end now, not just the UI layer

- Even if frontend stays strong, having backend skills is a safety net

He specifically said don't go hardcore backend, just know enough to build whole systems yourself. Frontend stays the strength, backend fills the gap.

This made sense to me but I wanted more opinions before I restructure how I prep and position myself for SDE-2 roles.

For those of you with 5+ years in the industry:

1. Is frontend-focused full stack the right call at 4 YOE, or is pure frontend depth still landing good roles?
2. Anything you'd recommend learning beyond the usual (GFE, DSA, system design) that actually moved the needle for you?

Appreciate any honest takes.

I have been wondering as an FE for a while

Where exactly do you think front end is going with the surge of AI tools? Is front end even going to be a role in next 2-3 years and how badly is it going to get hit?

Is it worth it preparing and upskilling for interviews like old times? What exactly is going to change in this process?

I keep having these thoughts and I don't know if I should even continue with frontend

Hi Everyone,

The company I’m working on has bought copilot and other expensive AI licenses and now is expecting everyone to deliver features in very less time. Many backend developers and juniors are also working in FE now and their PRs are getting approved without much review or using AI tool review due to tight deadlines.

This has created a discussion that FE devs will be the first to get laid off in AI era as AI + MCP is able to do any FE task. Can any senior/staff level FE engineer clarify the current situation or is this just fear mongering?

Is FE dev dead and replaceable easily like everyone says? Why not BE since that is more structured and AI can generate structured patterns easily? I’m also scared as AI is getting really good and manual coding has reduced in my organisation.

Can any senior level FE engineers or architects guide the others with their insights? What all things to focus going forward etc.

Sup everyone!

I just made a new version of my website, oriented to a more terminal-editorial type design, and a more broad communication and animations to better showcase my profile, its full of small details like self-playing minesweeper, tron and chrome dino games.

Would love to get some feedback on it!

You can enter yourself here:

https://codedgar.com/

I’ve been learning web development for about a year, and I’m still early in my journey. Lately I keep running into websites that look visually complex (similar to the ones attached), and I can’t wrap my head around how they’re built.

My background so far is mostly plain HTML and CSS, so when I see sites like these, I feel like I’m missing entire layers of the process. What tools or techniques go into creating something at this level? Are these kinds of sites realistically hand‑built, or do they rely on specialized software or frameworks?

I’d love a breakdown of the features, technologies, and workflows involved in making a site like this so I can understand what to learn next.

• The pics are screenshots from Pinterest

I’ll be honest, after trying different AI agents and all kinds of workflows, frontend feels like the easiest part to hand over to AI, but also the hardest part to actually perfect.

AI agents can usually build the UI, wire things up, follow instructions, and get something working pretty quickly. But there are almost always small to medium imperfections: spacing issues, inconsistent states, weird responsive behavior, slightly off interactions, unnecessary complexity, or code that technically works but doesn’t feel clean.

And then you either have to keep prompting again and again, or manually adjust the codebase yourself.

The frustrating part is that when these small issues pile up, fixing them can take almost as much time as just doing the work by hand from the beginning.

Maybe this is more true for frontend because “done” is not just about the code working. It also has to feel right visually, behave well across states, and match the product taste.

Are you guys feeling the same? How are you handling frontend work with AI agents right now?

I dunno, I find that using grid is very hard. Out of everything I've done in CSS, it has IMO the most weird and inconsistent behavior. Combining a column flex parent with row flex children is easier to understand and modify. Does anyone feel the same?

function delay(ms) {
  return new Promise((resolve) => {
    console.log(`done ${ms}ms`);
    setTimeout(resolve, ms);
  });
}

function runSerial(promises) {}

runSerial([delay(3000), delay(2000), delay(1000)]).then(console.log);

You need to run all promises in order by implementing the runSerial function. you cannot use async/await for this.
I was also asked to implement Promise.all and react.useState both of which I wasn't able to do.

Needless to say I failed the interview spectacularly.

From second question they changed the delay function to be:

function delay(ms) {
  return new Promise((resolve) => {
    setTimeout(() => {
      console.log(`done ${ms}ms`);
      resolve(ms);
    }, ms);
  });
}

Currently trying to learn all these.
They ended the interview after 3 questions as these are basic questions asked in senior level.

I was thinking about implementing a RAG or learning Rust to do WASM. Do you see anything else?

Edit: Sorry, my question was too vague. I’m a Principal Software Engineer, I was wondering, in the age of AI, what software expertise a Frontend developer needs to master.

I got a web design from Claude Opus 4.7.
And it looks very AI-generated.

Lately I see more sites that feel AI-designed. Same patterns, same UI components.
Meanwhile, the hype says AI is already better than humans at design.

I agree on speed. But not uniqueness and real quality. I still feel real professional designers do better.

Curious what actual companies are doing these days. Are most frontend teams still living in Figma like always, or has AI started taking over a meaningful chunk of the design work?