AI is for humanity

Interesting reflection from , John Palfrey after attending the AI summit in Delhi:

In Delhi, the big sessions had thousands. And the man who ran the event told me that more than a million people, mostly from India, had passed through the gates of the massive convention center during the week.

This may sound symbolic but I think it is an important symbol: that AI is about and for all humanity. It is not something that is magical and only to be shaped by wizards. It is a technology that is general — it touches everyone on the planet one way or another, already, with implications for nearly every aspect of human life. I’m not hyping it up; I think this is fact at this stage. The Internet was the same way, sort of, but I think AI will prove another step more consequential.



Postmortem from 2028

From The 2028 Global Intelligence Crisis: A Thought Exercise In Financial History, From The Future

What follows is a scenario, not a prediction.

[...]

A competent developer working with Claude Code or Codex could now replicate the core functionality of a mid-market SaaS product in weeks. Not perfectly or with every edge case handled, but well enough that the CIO reviewing a $500k annual renewal started asking the question “what if we just built this ourselves?”

[...]

The interconnected nature of these systems weren’t fully appreciated until this print, either. ServiceNow sold seats. When Fortune 500 clients cut 15% of their workforce, they cancelled 15% of their licenses. The same AI-driven headcount reductions that were boosting margins at their customers were mechanically destroying their own revenue base.


Archive.today CAPTCHA page executes DDoS

Mind blown by this sneakiness 

Wikipedia editors are discussing whether to blacklist Archive.today because the archive site was used to direct a distributed denial of service (DDoS) attack against a blogger who wrote a post in 2023 about the mysterious website’s anonymous maintainer.

Checking on the In a request for comment page on Wikipedia

Over 400,000 pages currently contain over 695,000 links to Archive.today

In January 2026, the maintainers of Archive.today inserted malicious code in order to perform a distributed denial of service attack against a person they were in dispute with. Every time a user encounters the CAPTCHA page, their internet connection is used to attack a certain individual's blog.

Defined tags for this entry: ,

The Governor is Gone

From AI fatigue is real and nobody talks about it

Here's the thing that broke my brain for a while: AI genuinely makes individual tasks faster. That's not a lie. What used to take me 3 hours now takes 45 minutes. Drafting a design doc, scaffolding a new service, writing test cases, researching an unfamiliar API. All faster.

[..]

But my days got harder. Not easier. Harder.

[..]

Before AI, there was a ceiling on how much you could produce in a day. That ceiling was set by typing speed, thinking speed, the time it takes to look things up. It was frustrating sometimes, but it was also a governor. You couldn't work yourself to death because the work itself imposed limits.

AI removed the governor. Now the only limit is your cognitive endurance. And most people don't know their cognitive limits until they've blown past them.

 

Defined tags for this entry: , ,

ops is not a dirty word

From https://charity.wtf/2026/01/19/bring-back-ops-pride-xpost/

What’s wrong with operations? Ops is not a synonym for toil; it literally means “get shit done as efficiently as possible”. Every function has an operational component at scale: business ops, marketing ops, sales ops, product ops, design ops and everything else I could think of to search for, and so far as I can tell, none of them are treated with anything like the disrespect, dismissal and outright contempt that software engineering

Defined tags for this entry: , , , , ,

Using llm to understand large codebases

From Martin Fowler :

One attendee is an SRE for a Very (Very) Large Code Base. He was less worried about people not understanding the code an LLM writes because he already can’t understand the VVLCB he’s responsible for. What he values is that the LLM helps him understand the what the code is doing, and he regularly uses it to navigate to the crucial parts of the code.

There’s a general point here:

Fully trusting the answer an LLM gives you is foolishness, but it’s wise to use an LLM to help navigate the way to the answer.

Defined tags for this entry: , , ,

Page 1 of 61, totaling 427 entries