By the end of this post, a pull request that breaks your data will fail in GitHub before anyone can merge it.
Most data quality checks run after the data lands. But often, what broke it was a code change approved an hour earlier. So let's check it right there, in the pull request, with three pieces:
People ask it as a yes or no. It isn't one. Not because nobody knows the answer, but because "job" is the wrong unit to ask about.
Almost nobody does one thing at work. You do a bundle of tasks, and AI hits each one differently. Some are already mostly automatable. Some are decades out. A few will actually get easier in a way that makes you more valuable, not less. Average all of that i...
You asked something. The answer came back polished. Later you found out it was wrong. A statistic that doesn't exist. A citation to a paper nobody wrote. A confident summary of a document that says the opposite.
The frustrating part isn't the mistake. It's that nothing in the reply looked like a mistake. No hedge. No wobble. No visible seam. That gap is the thing worth understa...
Partial, Required, and DeepPartial in 2026: Which Utility Type Actually Fits Your Use Case
This article was written with the assistance of AI, under human supervision and review.
Most TypeScript utility type problems stem from teams treating Partial<T>, Requ...
I build a tool that schedules social posts. This week I added four new places to publish: WordPress, dev.to, Hashnode and Lemmy. Then I had each adapter reviewed by someone who did not write it. The most useful findings were all the same kind of bug: the code said "published" when it had only proven "the server answered".
Here are four ways that happens.
I've been sitting on this project for a while, I haven't shared it until now. While learning about networking and on one of my massive side tangents, I thought it would be really cool to have a detailed breakdown of what the data is doing at what stage in the process. No, not another OSI Model post, but the Wi-Fi 7 NIC exclusively. I wanted to know, "Wha...