Urgent.News

What's breaking now, across thousands of outlets.

Tech

My writing linter can be defeated by writing more. I measured how much more.

I ran my writing checker over one of my own published posts twice: once on the whole file, once on just the body with the front matter removed. Same post. Same prose. --- WHOLE FILE score 2 · 3 issues · 930 words [tier1-clarity] "features" [em-dash] "15 em dashes in 930 words" [formatting] "4 bold phrases" VERDICT: PASS --- BODY ONLY score 3 · 3 issues · 746 words [tier1-clarity] "features"…

I ran my writing checker on a published post twice: first on the entire file, then on just the body with the front matter removed. The scores were the same, but the verdict crossed a publish gate only on the body. Stripping the front matter contributed words and dashes to the denominator, allowing the post to pass the gate. The tool measures two factors: set-based word-level tests and density-based em-dash and bold tests.

The density tests can be driven down by adding non-objective text, while the set-based tests are unaffected by repetition. The checker combines these two factors into a single score, but they should be scored separately. The front matter, titles, and descriptions are metadata not to be averaged with the main body. Splitting the score into two scalar values, one for each family, would prevent padding from inflating the denominator and provide a more accurate assessment.

The current system produces a misleading score that is trusted for the wrong reason, leading to a flawed publishing gate.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Self-hosting break-even: $23/month of SaaS, a $170 mini PC, about 9 months

Replacing $23/month in SaaS subscriptions (Google One 2TB + 1Password + Plex Pass) with a $170 mini PC drawing 15W idle breaks even in about 9 months.

  • Replacing $23/month SaaS with $170 mini PC yields 9-month break-even
  • Payback depends on what services are replaced, not on $10/month storage
  • Electricity costs and hardware choice significantly affect break-even timeline

How long do you keep a published claim provisional?

I retracted a benchmark this week. Two weeks ago I published a timing figure, described it as a fixed cost, and built an argument on it.

  • Author faces decision on retaining provisional claim validity.
  • Four instances of correcting published figures due to various issues.
  • Author suggests treating numbers as provisional with changelog.

Adding a NOT NULL Column to a Large PostgreSQL Table: Constant Default, Backfill or NOT VALID

Disclosure: I build Schemity , a desktop ERD tool - this post is from our blog and uses it for the examples. TL;DR: On PostgreSQL 11 and later, ADD COLUMN ...

  • Adding a NOT NULL column with constant default (e.g., NOW()) is fast in PostgreSQL 11+.
  • For per-row computed values, add column as nullable, backfill in batches, then set NOT NULL.
  • PostgreSQL 12+ allows NOT VALID constraint to skip full table scan during backfill.

More from Thursday 1 October →