Systems | Development | Analytics | API | Testing

Owning the Agentic SDLC: How NodeSource Reclaimed Control of AI Development

TL;DR: When AI-assisted development moved from autocomplete to agentic workflows, the bottleneck for our engineering velocity stopped being the model and started being the vendor. Owning our own orchestration layer, running the same upstream agent stack across multiple developer surfaces, wrapping every change in a version-controlled spec, and treating the agent calls themselves as first-class telemetry is what made spec-driven development practical for us at NodeSource.

SQL-Shaped Intent: The Engineering Behind AgentQL

Our CEO recently wrote reaffirming an architectural decision ThoughtSpot made when LLMs first emerged: we do not use LLMs to directly generate SQL. My team has spent the better part of a year building AgentQL: a capability that doubles down on our decision. So let me explain what we actually built, why it doesn't just honor that architectural decision but depends on it, and the engineering choices underneath.

Data Cleansing: The Complete Guide (Process, Techniques, Examples)

Data cleansing sits at the heart of every reliable data pipeline. Yet despite being essential to trusted analytics and decision-making, cleaning data remains one of the most time-consuming and undervalued steps in modern data workflows. With poor data quality creating significant operational challenges, getting data cleansing right has never been more critical.

Role-Based Access Control (RBAC), Explained for Data Teams

Data teams face an impossible challenge: democratize data access across the organization while maintaining security controls and meeting regulatory requirements. Without a structured approach, engineering teams spend 15-25% of their time handling access requests instead of building data products. Role-Based Access Control (RBAC) transforms this operational chaos into a manageable system but only when implemented correctly.

8 Best Salesforce Data Cleansing Tools in 2026

Salesforce serves as the operational backbone for sales, marketing, and customer service teams worldwide. When that foundation contains duplicate records, incomplete fields, or outdated information, the consequences cascade throughout the entire organization. Sales teams waste hours chasing leads that already exist in another record. Marketing campaigns target contacts who left their companies months ago.

Test generation got free. Test governance didn't.

Over the past twelve months, something has shifted in how software teams think about quality. Claude Code, Cursor, and Playwright agents have made it genuinely easy to generate functional tests without deep automation expertise. The impact is showing up across two very different kinds of teams: Both paths lead to the same place: tests accumulate without governance, you get coverage without traceability, and there’s automation debt no one owns. But coverage numbers and quality are not the same thing.

Regression Testing in Agile: Test Every Sprint Without Slowing Down

Regression testing in agile happens inside every sprint, alongside the stories being built. Targeted tests run on each pull request, the full suite runs before sprint review and every release, and hotfixes get a check of their own. The whole team shares the work while one tester curates the suite, and it stays fast when tests are chosen by what changed. Every sprint ships new code, and some of it quietly breaks features that shipped months ago.

A Beginner's Guide to Turning Old Photos Into Videos

Somewhere on a hard drive or in a shoebox, there are photographs that matter to you - a grandparent on a doorstep, a holiday nobody documented properly, a childhood pet. They get scanned, admired for a moment, and filed away again. Motion changes how those images land, because movement restores something a still frame flattens: presence. This tutorial assumes no editing experience. You will learn what photo animation actually does, how to prepare an archive image, and how to finish a short, respectful memory clip in a single sitting.
Sponsored Post

Two confident fixes missed this production bug

Every new signup posts a message to our Slack. The format is dull and reliable: Overnight this week one arrived like this: That trailing nothing was the entire incident. No error logs, no alerts. A returning user had signed up, our signup service had attached them to a tenant we deprovisioned back in December, and the only symptom in the whole company was a Slack message that ran out of words. Their company's email domain still pointed at the dead tenant, so instead of a fresh workspace they landed in a corpse: domain mapping still live, cloud infrastructure long gone. I'm on call this week, so I pulled the thread.