Having flashbacks on the beach at Da Nang

The Coldest Cold Email: Oracle’s 30,000-Person Layoff Is a Preview of What’s to Come A 6 a.m. message signed “Oracle Leadership” just ended tens of thousands of careers. Here’s what it means — and what to do if you’re next.

I remember when it was a scandal that a company laid people off over Zoom. Now that seems warm and fuzzy compared to the norm today.

Oracle laid off 30K people with a 6AM email with a link to click and accept terms if they wanted severance.

Interesting idea to recycle old content

After years on Samsung, I moved to Pixel for less bloat. I was planning to put GrapheneOS on a new Pixel, but I saw the Nothing 3 and liked the look, the camera does the job but not great.

After years of using Google Pixel phones for their lack of bloat, I found the actual devices a bit meh. The Nothing 3, on the other hand, feels slick and looks great.

Completely agree. A lot of what we see going on over the pond makes Malcolm Tucker look like Sir Humphrey Appleby.

I only login for the puzzles now

Politicians have always practiced doublethink.

I'm not sure whether they're getting better at it or we just don't want to address the obvious contradictions and lies.

He says every line of code will need to have coverage, but also we need to see tests for things the code is not meant to do also, which is where it gets non trivial cause that list of negative tests could be infinite and AI will likely have similar blind spots and failure modes there too

10/ You can solve an enormous number of technical problems by taking a walk

I feel like he’s saying we need to be even more selective about the open source we choose.

“If the creator doesn’t trust the code, why should you?”

Code is now a commodity.

Maintenance and security are luxury goods.

We choose it based on how well we survive when it fails.

Was a very interesting episode. I liked the origins of the pelican on the bike benchmark, his honesty about not trusting his own AI-generated code despite it looking polished, and the fatigue and burnout of iterating fast.

The 2026 State of Software Delivery - CircleCI AI increased development activity by 59% in 2025, but delivery is slowing. Learn why pipelines break under AI scale and how top teams adapt.

The new reality of software delivery

We're writing 59% more code and yet shipping less code than before. Code review, testing, integration, recovery. None of it got faster. The SDLC is choking on volume it was never built for.

circleci.com/resources/20...

I asked you about art, you'd probably give me the skinny on every art book ever written... But I'll bet you can't tell me what it smells like in the Sistine Chapel.

-- Sean Maguire --

Apps give you knowledge.

Software gives you experience.

You can build 100 apps in a day, but won't understand software till you've supported it long enough to watch it break 10 different ways.

Building is cheap now.

You can ideate and fail 10 times before lunch.

But the job was never the tasks.

It's still deciding what's worth building and making it hold up over time.

Instead, we've convinced ourselves that activity is progress.

People are grossly mistaking productivity for value.

An app is a thing that works.

Software is a thing built to last and operate reliably.

Was wide before but In the last 6 months, that ratio has only widened further.

Knowledge, like time, has been democratized. Value hasn't.

Makes sense

Good stuff - SingleFileUpload looks like it stores via a LargeBinary property directly in DB, bypassing @cap-js/attachments entirely.

So it doesn't go through a malware check, Hana is quite a expensive way for storing files

Opus and Sonnet are really good at one shotting BDD style QUnit tests if you have strong types and good JSDoc.

That is the legacy analysis step in the workflow, inlining the meta so the intent of the codebase survives the migration / uplift etc.

The article does not cover legacy analysis and test creation. It covers scaffolding, TypeScript migration, linting, and API docs.

But understanding your legacy code and having a test harness in place is exactly the workflow you need before migrating to TypeScript I would have thought.

GitHub - SAP/open-ux-odata: Enable community collaboration to jointly promote and facilitate best in class framework and tooling capabilities when working with OData services. Enable community collaboration to jointly promote and facilitate best in class framework and tooling capabilities when working with OData services. - SAP/open-ux-odata

github.com/SAP/open-ux-...

for people who haven't come across it yet github.com/SAP/open-ux-... a lot of really good tools and samples in this repo

If you can avoid running a backend to test a frontend in a pipeline those minutes add up and cost real money.

Where I feel it earns its place is when you need predictable HANA like behaviour locally and don't have it. Could also add something in OPA5 testing if you can run automated tests faster with isolated data per test without spinning up a real server, yet to find out if it actually delivers that.

Really see the benefit of the Fiori mockserver now.

CAP annotations like @hierarchy where SQLite and H2 don't behave like HANA, without a local HANA the process is very slow going and full of workarounds.

The email was sent at 7am, I wonder how many people didn't get it cause they were already locked out of email

Cold

Ouch sounds like crypto squatters

ESLint apparently doesn't flag em dashes (—) because it's a code linter, not a spell checker.

5 mins with Opus trying to decide whether a plugin, rule, skill, or prompt is needed. The whiplash hurts.

Update- asked Gemini - it's a line in eslint.config.js. Cool.