Paige Niedringhaus

Things Paige Says on Podcasts

Staff software engineer with a frontend focus, previously a digital marketer, and author of The newline Guide to Modernizing an Enterprise React App. Co-hosts the Front-End Fire podcast and both hosts and guests on PodRocket, LogRocket's web development show. Writes and speaks on React, frontend architecture and open source sustainability, and covers weekly developer news including AI coding tools, npm supply chain issues and CSS anchor positioning on her podcasts.

Where to Find Them

Paige Niedringhaus hosts and writes Front-End Fire and hosts PodRocket .

Recently: “170: Tech Is Still Hiring... Just Not You” on Front-End Fire (November 2026); “169: How the Heck Do We Hire Developers in 2026?” on Front-End Fire (November 2026); “168: Are Dev Conferences Dying?” on Front-End Fire (November 2026); “167: AI is Making Code Reviews Worse” on Front-End Fire (October 2026); “166: The AI Clone Wars Continue” on Front-End Fire (October 2026); “165: Open Source Was Fun While It Lasted” on Front-End Fire (October 2026).

What They Said

“Five or 10 years ago it made total sense to be a specialist. But now, if you can successfully prompt an agent to be an expert in whatever language or framework or stack you're using, you can work front to back a lot easier than it ever was before. We call it thin vertical slices: everything from the database through the API through to the UI, one person working on one feature.” — Paige Niedringhaus, Front-End Fire

A co-host had said he'd barely call himself a front-end engineer anymore. Paige describes how her team now works, with one person owning a feature end to end.

Front-End Fire · 2026-11-16 Permalink → Listen →
Front-End Fire Around 08:10 into the episode
Jack Herrington

…has always been one where I've been like, if I have kids that come to me and ask me about feature or whatnot, and they're slightly technical, it's like software security is actually a good one to get into because it's just we do everything on software and it's becoming increasingly vulnerable.

TJ VanToll

…come up with one of these more generic terms, someone who's technical that's familiar with the AI tools. And I think there's a lot of other companies in that same position. They don't need a mobile person. They just need general people who know how to use the AI tools and are technically competent.

Paige Niedringhaus

Yeah, like five or 10 years ago, it made total sense to be a specialist and be really, really good at either front end or back end or a particular framework or an area of interest. But now, like you said, if you can successfully prompt an agent to be an expert in whatever language or framework or stack you're using, you can work front to back a lot easier than it ever was before to be across the whole stack. And that's really what a lot of companies and I mean, my team at Allspice are doing is like, we call it thin vertical slices, and it's moving, it's using everything from the database through the API through to the UI. And that's like one person working on one feature, but security and all that. Exactly, all the way through to infrastructure. Yeah,

TJ VanToll

you and their

Jack Herrington

own personal pizza box team.

Paige Niedringhaus

Exactly. Well,

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“Don't share your session with me. I do not want to read that. I'm not going to read that. It's just the honest truth. I don't read all of my Claude sessions myself, so I'm not going to read somebody else's.” — Paige Niedringhaus, Front-End Fire

The hosts were discussing how code review works when agents write most of the code, including a proposal that reviewers be given the AI session behind a change. Niedringhaus says her team instead commits plan files where the agent records what it actually did, and keeps PR descriptions short.

Front-End Fire · 2026-10-26 Permalink → Listen →
Front-End Fire Around 09:50 into the episode
Paige Niedringhaus

…just want to look at the code or smoke test it, whatever, then you can just read the PR description that is short and succinct and something that is small. Yeah, but it is there for posterity. It's there for future agent sessions. Like the agents can look at it all they want, learn things from it.

TJ Van Toll

…you. I mean, if you solve this, let us know in the YouTube comments or on our Discord because we're always curious what other people are doing. Because I don't think anybody really knows. And the best we can do now is just talk about it and share stories, share what's working for us, share what's

Paige Niedringhaus

not. Yeah, but don't share your session with me. I do not want to read that. I'm not going to read that. It's just the honest truth. I don't read all of my clawed sessions myself, so I'm not going to read somebody else's.

TJ Van Toll

The AI slop is getting out of control. This is the other thing that's bad in our modern era is now you'll get these like AI slop files that somebody else in your company will just send you. And you know, it was just, you just had Claude just mass create this. And then you're just, when you're, when…

Paige Niedringhaus

Yeah. I will say, in defense of the agents, at least this week in particular, there's been some big updates to the Claude desktop app where if I've started on one session and I'm working on something and I need to continue a new session because it's a fresh, you know, it's a related issue or it's…

TJ Van Toll

Yeah, I found that both Codex will start doing this now too, where it'll spawn sub-agents. And it's almost kind of mesmerizing to watch because they'll say like, oh, well, I can help you, but I'm waiting for this sub-agent to report back. It's off doing some research and it's wild.

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“There's a lot more that people are trying to shove in as requirements than there ever was before. And it's because AI is making it possible time-wise, but people are still people at the end of the day and only have a finite amount of time and energy and focus. And that's not really being accounted for in this new era.” — Paige Niedringhaus, Front-End Fire

Niedringhaus says her company is hiring directors who are also expected to write code, hire, manage people and fill in when the team is lean. She is describing how job titles now carry more than they used to.

Front-End Fire · 2026-10-05 Permalink → Listen →
Front-End Fire Around 25:50 into the episode
Speaker 1

Yeah. There's so many things I think of that feel antiquated now, but we still kind of do them because we go through the motions and change is very hard. Yeah. Like hiring process, redefining roles, coming up with all the logistics and bureaucratic changes around that is very hard and it takes time.

Speaker 3

But I think for all that. Oh, sorry.

Speaker 2

Well, kind of piggybacking off of that, I've seen, and you're probably seeing too, we're trying to hire for titles that previously did one thing, except we're now expecting them to do other things. Like we're trying to hire for directors at my company, but we don't want them to just be directors like old school directors. We want them to also be individual contributors who can jump in and write some code and jump out and do some hiring and do some management and some people stuff and then also jump back in and like help out when the team is lean. So it seems like there's a lot more that people are trying to shove in as requirements than there ever was before. And it's because AI is making it possible time-wise, but people are still people at the end of the day and only have a finite amount of time and energy and focus. And that's not really being accounted for in this new era.

Speaker 3

Yeah. We're starting to learn again that code, the velocity of coding was never truly the problem in our systems. Like, you know, you can make a whole lot of features and give them a QA and they're just going to be swamped. You know, what is that going to happen? Yeah. But I think I too, am being…

Speaker 1

All right. Well, from that, speaking of things AI can fix, we have a lot of releases that we want to cover, a lot of bonus leggings. So why don't we get going?

Speaker 2

Yeah.

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

Collections They Appear In