Blog
105 posts, newest first. Page 5 of 11.
Deprecation started 1 July 2026 and the issuer dies 1 July 2027. Nothing breaks in between, which is the problem. The issuer is not a documented field on the service connection, so finding every affected one means grepping the raw REST response.
Amazon SES is the $0.10 per thousand everyone quotes. From 21 July 2026, new accounts start on a plan that charges $0.16, and the cheap number is something you opt into. Meanwhile the break-even against a managed provider is roughly ten times higher than the usual advice says.
TypeScript 7.0 went GA on 8 July 2026 and type-checks VS Code in 10.6 seconds instead of 125.7. It also ships no compiler API until 7.1, and typescript-eslint's peer range still stops at 6.x. The upgrade is an install-both, not a swap.
Run the two rate cards against each other and Lambda costs 2.15 times Fargate for the same CPU and memory, so it stays cheaper until the function is busy nearly half the time. Lambda Managed Instances lands within 1% of Fargate, which is not where the announcement pointed.
Node 20 stopped getting patches on 30 April 2026. GitHub Actions forced every action onto Node 24 seven weeks later. AWS Lambda pushed its enforcement out to March 2027. Neither date is the one that was announced last year.
I ran the same threaded workload on 3.14 and 3.14t on a 10-core laptop: 1.00x versus 3.53x on four threads. The interesting part is the two things that silently take that away, and neither of them is Python.
One bills agent-seconds, one bills AI credits at roughly 6.5 per investigation, two bill seats, and one will not tell you. The word agent got stretched across five product shapes, and the meter is the fastest way to work out which one you are looking at.
Formula correctness, messy-data cleaning, and what leaves your tenant. Which spreadsheet AI to reach for depends mostly on where your data already lives.
Mem0 bills add and retrieval requests, Zep bills credits, Letta bills active agents and seconds of tool execution, Cognee bills tokens ingested. All four are Apache-2.0, so the meter matters more than the feature list.
Picking a Postgres pooler is mostly picking a pooling mode and living with what it breaks. Five options, what each one is actually for, and the setting that stopped being a footgun.