Simplify pipelines with new BigQuery identity columns
New BigQuery identity columns let you define columns that automatically generate sequential 64-bit integer values to manage’ unique identifiers.
Systems | Development | Analytics | API | Testing
Modern Software Development For Today's Systems & Applications
Beyond Playwright: Building a Central Test Hub with Selenium, Cypress, and Katalon
Most QA teams do not use one automation framework. They use two or three. Selenium handles the legacy suite and cross-browser regression. Playwright covers the newer end-to-end flows. Cypress runs the frontend component tests that developers wrote. Maybe there is an Appium layer for mobile. Each framework was adopted for a good reason. Each solves a real problem. But the result is fragmented visibility. Test results live in separate CI jobs. Reporting requires pulling data from multiple sources.
Raw WebSockets for AI streaming: when patching stops paying off
Raw WebSockets drop connections, lose track of canceled responses, and don't natively reach a second device. If your AI streaming feature has been in production for a while, you've probably already built a fix for at least one of these and found another one waiting. Reconnection, cancellation, multi-device delivery, and crash detection are the four problems raw WebSockets leave for you to solve, and each is its own piece of infrastructure to build. Solve one, and the other three remain unsolved.
AI in Claims Processing: What's Actually Working in 2026
AI claims processing applies predictive models, machine learning, computer vision, and generative AI across claims workflows. These technologies analyse documents, images, policy terms, historical records, and structured claim data. Insurers use AI for document extraction, claim triage, fraud detection, damage assessment, and adjuster assistance. Predictive models classify claims, estimate severity, and identify cases requiring specialist review.
Why Companies Stay on EOL Node.js - Even When They Know the Risk
Legacy Node.js is rarely an awareness problem. It is a risk, cost, and uncertainty problem. Last week, we looked at a striking signal in the official Node.js download data in Node.js Downloads Surge in 2026 as Node.js 24 Takes the Lead. Node.js 24 had become the most downloaded Node.js release, a strong indication that modernization across the ecosystem is accelerating. But something else stood out.
Best BI Tools for Non-Technical Teams in 2026
Nine tools compared on the criteria that matter when your team reads dashboards instead of building them.
10 Load Testing Strategies to Optimize E-Commerce Website Performance in 2026
E-commerce platforms face unique performance challenges. Traffic patterns are volatile, with sudden surges during flash sales, promotions, or holidays. Relying on generic load testing – such as steady user simulations or basic server throughput checks – misses the mark. If your tests don’t mirror real shopping scenarios, you risk missing critical issues that can lead to lost revenue and damaged brand reputation during peak events.
Best Hosting for Odoo: Backups, Uptime and Disaster Recovery
Almost every Odoo host advertises backups. Very few will tell you when a restore was last tested, and those are completely different claims. The gap between them is where agencies get hurt. A backup that exists but has never been restored is not a backup. It is a file, and you find out which one it is on the worst possible day. Cloudpepper is Odoo hosting with automated backups and monitoring built for agencies running client systems, and on this particular criterion it is the strongest option available, for a structural reason covered in point seven below.
Test Behavior, Not Choreography
The spy from post 4 is a sharp tool. Once a test can record every interaction, it is tempting to assert on all of them. The result looks thorough, but it is usually a transcript rather than a useful specification. This post takes a test written that way, makes a change that no customer could possibly notice, and watches the test fail anyway. This is part 5 of a ten-part series. The code is in Java, Node.js, Go and Python.
Make Failure Boring with Mocks
Every codebase has a failure path nobody has run. Not through laziness, but because reproducing it requires a backend dependency to misbehave on cue. In the package notifier, the carrier must refuse, stall, or return nonsense at the exact moment the test runs. So the retry logic ships unverified and everyone hopes. The seam from post 2 already gives the test control. A seam is a place where you can change what code does without editing that code.