I am currently working with the EA on their check for flooding team. I have been tasked to look at the 5 day river level charts with a view to add more historical data. This meant increasing the amount of data showed on the chart so users could compare the current river levels with the previous week, month or year. In order to proceed with some user research I needed to create a prototype of the r
In March 2024, Google replaced First Input Delay with Interaction to Next Paint as an official Core Web Vital. FID is gone. INP is what matters now — and most React apps that were passing before are failing under the new standard without anyone realizing it. FID measured how long the browser took to respond to the very first user interaction on a page. Click a button, FID measures the delay before
A defaced website is a curious problem. It's loud — anyone visiting the page can see something is wrong. But it's also quiet from a server's perspective: HTTP returns 200, your uptime monitor is happy, your TLS cert hasn't moved, and the CMS logs show a "successful" content update from a legitimate-looking session. The signal is on the rendered page, not in the metrics. I run a site at hi3ris.blue
As a developer, you deal with text casing constantly - button labels, nav items, page titles, error messages, documentation headings. And at some point, someone on your team will ask: Here's the definitive answer. // Title Case — most words capitalized "The Best Free Tools for Writers and Developers" // Sentence case — only first word + proper nouns "The best free tools for writers and developer
You just ran a dependency scan and the report shows 133 vulnerabilities. 34 are Critical. 68 are High. The dashboard is red, the backlog is exploding, and every item looks urgent. The engineering team asks the obvious question: where do we start? This is where vulnerability remediation prioritization matters. Without a clear framework, teams either panic and chase the loudest CVE, or they ignore t
When a financial services team decides to move data to the cloud, the conversation usually starts with infrastructure. Which cloud provider. What the cost model looks like. Whether to go lift-and-shift or re-architect from the ground up. Those are real decisions. But they are not the hard part. The hard part is walking into a room with your compliance team six months into the migration and being a
We've been there. JSON Schema gets hard to write as soon as your payload is non-trivial. Conditional logic, cross-field rules, business invariants, and at some point we stop writing contracts at all. We go code-first, generate the schema from annotations, and end up with 200 lines very few understand, and error messages referencing paths like #/properties/items/allOf/0/then/Then that map to nothin
GitHub Copilot is more than just an AI coding assistant; it's a productivity superpower for many developers, promising to streamline workflows and accelerate delivery. Yet, as a recent GitHub Community discussion vividly illustrates, the path to actually subscribing to this powerful tool can sometimes be a frustrating maze of unexpected billing hurdles and unresponsive support. At devActivity, we