Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Niharika Pujari
Part 2: From Notebook to Endpoint: Understanding the Amazon SageMaker ML Workflow
In Part 1, I wrote about how I started looking at Amazon SageMaker as more than just a place to train machine learning models. The next thing I wanted to understand was simple: How does a model actually go from an experiment to something an application can use? As a software engineer, the workflow felt much more familiar once I compared it to taking code from development to production. Let's walk through it. 1. Start With the Data Every ML model starts with data.
When AI Fails, the Interface Must Still Work: Human-Centered Fault Tolerance for AI Features
By Niharika P. Pujari on October 2, 2026 AI features are moving quickly from optional experiments to everyday product workflows. Users now rely on AI to summarize information, recommend options, generate content, fill in forms, and complete multi-step tasks. The engineering challenge starts when the AI cannot do what we expect. A model may be unavailable, return incomplete output, misunderstand a user's intent, or produce an answer that sounds reasonable but is wrong.
Evaluating AI-Generated Frontend Code: What Should We Actually Test?
AI can now generate a surprising amount of frontend code from a short description. A developer can ask for a form, a table, a modal, a settings page, or a dashboard view and get something that looks usable almost immediately. It may compile, render, and even arrive with a few tests. That is useful, but it also creates a problem: The first version of the UI can look more complete than it really is. Frontend code is often judged too quickly.
The Design System as the Control Plane for AI-Generated UI
AI-assisted development has made it easier to generate frontend code quickly. A developer can ask for a form, a dashboard widget, a settings page, or a modal flow and get a working first draft in seconds. That speed is useful, especially when teams are moving through routine UI work. But speed creates a problem that’s easy to miss at first.
CSS Anchor Positioning: Building Tooltips Without JavaScript Positioning Hacks
Introduction Positioning a tooltip sounds simple. Put a small box next to a button. Done. But anyone who has built one knows that it can quickly turn into: position: absolute calculating coordinates listening for resize events handling scrolling checking whether the tooltip fits on screen and sometimes pulling in an entire positioning library Modern CSS is starting to change that. CSS Anchor Positioning lets us position one element relative to another directly in CSS.
Why observability matters to frontend teams more than they think
Credit: JOKE_PHATRAPONG / Shutterstock For a long time, I thought of observability as something mainly owned by backend, platform or site reliability teams. Frontend engineers built the interface, handled browser behavior and called APIs. When something failed deeper in the system, another team looked at server logs and infrastructure dashboards.
Accessibility Bugs Are Often Architecture Bugs
Accessibility bugs are easy to treat as small frontend mistakes. A form field is missing a label. A button does not have a clear name. A modal opens, but keyboard focus stays behind it. A dropdown works perfectly with a mouse but becomes frustrating with a keyboard. An error message appears visually, but a screen reader user never hears it. When issues like these show up, the usual response is straightforward: create a ticket, fix the screen, run another check, and move on.
The Frontend Verification Gap in AI-Assisted Development
AI-assisted development has made frontend work feel much faster. A developer can ask for a form, a dashboard card, a table, a modal, or a responsive layout and get a decent first version almost immediately. The code may compile. The page may render. At first glance, the UI may look done. But frontend developers know that “it looks done” and “it works well” aren’t the same thing. A generated form might show validation errors visually but fail to announce them to a screen reader.
Frontend Architecture Is Not Just Folder Structure
Frontend architecture is one of those phrases that sounds bigger than it feels in day-to-day development. When teams talk about it, the conversation often starts with folders. Should components go inside shared?Should pages live underfeatures?Should services be grouped by domain?Should we usecomponents, containers, views, modules, or something else? shared features components containers views modules These questions matter, but they are not the full story.
5 Angular Features Developers Should Actually Pay Attention to in 2026
Introduction Angular has changed a lot over the past few releases. Between Signals, standalone components, modern template syntax, and rendering improvements, Angular feels very different from the Angular many of us learned a few years ago. Some features are incremental. Others genuinely change how we build applications. Signals are probably the biggest shift in Angular’s mental model in years.
Part 1: Understanding Amazon SageMaker
My first impression of SageMaker When I first came across Amazon SageMaker, I assumed it was one of those AWS services that made more sense to data scientists than to software engineers. I had seen the name many times, but I still did not have a clear answer to one basic question: What is SageMaker actually for? At first, I thought of it as simply "the AWS machine learning service." But that description felt too broad to be useful.
Angular's New Template Control Flow (@if, @for, @switch) - A Cleaner Way to Write Angular Templates
Introduction Angular has evolved significantly over the last few releases. One of the most noticeable improvements in modern Angular is the new template control flow syntax.
Accessibility: Building Inclusive Experiences | A Lens on Basic A11y Testing
Introduction Accessibility testing can feel intimidating at first. Between WCAG guidelines, assistive technologies, and tooling, it’s easy to think you need to be an expert before you can meaningfully contribute. After watching and reading Basic Accessibility Testing by Glen Walker (via Equalize Digital), one thing became very clear: you don’t need to know everything to start making a real impact.
How I cleared my AWS Certified Solutions Architect Associate exam in 30 Days?
I am a Lead Software Engineer, working for about 8 years now. I decided to give my self some challenge for my professional development so I chose to level up my knowledge about AWS. I had previously got from AWS Cloud practitioner certification in 2021 but if you are new to cloud, then the foundational certification is the way to go! The first thing I would suggest is to set a date for your exam: The best motivation to start preparing for the AWS certified exam is to Schedule the exam.
Accessibility: Building Inclusive Experiences | A Lens on Branding and Design
Introduction In a world where digital experiences shape how we work, play, shop, learn, and communicate, accessibility isn’t a passing trend - it’s a core requirement of good engineering and thoughtful design. Accessibility ensures that digital products and services can be used by everyone, regardless of ability, device, or context. Despite its impact, accessibility is still too often treated as an after-thought addressed late in the process or reduced to a compliance checkbox.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Niharika
Contact Niharika, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack