Permalink: 20260302114304

Found at “Breaking Free” on 2026-03-02T11:43:04+01:00.

In the new report Breaking Free: Pathways to a fair technological future, the Norwegian Consumer Council has delved into enshittification and how to resist it.

Permalink: 20260227105515

Found at “Reflections on the Future of Software Engineering Retreat” on 2026-02-27T10:55:15+01:00.

At a fundamental level, we need to both evolve our understanding of what engineering work actually entails and rethink how we measure value. Developers could never consistently code for eight solid hours a day without getting exhausted: even if AI takes over code generation, the move to working on a handful of concurrent problems with AI and the necessary context that requires isn’t sustainable or conducive to good work. It’s not really about just writing code; frequent design and architecture work can lead to significant decision fatigue.

Permalink: 20260225154544

Found at “paint: a timeline” on 2026-02-25T15:45:44+01:00.

This timeline is the result of researching the origins of digital paint and draw software, and the tools that were developed to allow for hand manipulation (versus plotter drawn) drawing and painting - the mouse, light pen & drawing tablet.

Andy Warhol and the Amiga. During the launch of the Amiga, in 1985, Andy Warhol used ProPaint to create a digitized image of Debbie Harry.

Permalink: 20260225102258

Found at “Choose your losses” on 2026-02-25T10:22:58+01:00.

Most career advice is generic. “Be a great communicator”. “Always deliver on time”. When I’m reviewing applications as a hiring manager, I’ve seen all of the generic traits by the fifth or sixth application.

Instead of saying the same as everyone else, build a specific combination of traits that sets you apart.

Permalink: 20260225100315

Found at “Writing code is cheap now - Agentic Engineering Patterns - Simon Willison’s Weblog” on 2026-02-25T10:03:15+01:00.

Delivering new code has dropped in price to almost free… but delivering good code remains significantly more expensive than that.

Permalink: 20260222122030

Found at “The History of Xerox” on 2026-02-22T12:20:30+01:00.

PARC began operation on the 1st of July in 1970. Goldman then chose George Pake to be PARC’s first director, and he split PARC into three units: the Systems Science Laboratory (SSL) under Bill Gunning, the Computer Science Laboratory (CSL), and the General Science Laboratory (GSL) under Pake himself. Pake, in turn, chose Robert Taylor, former deputy director of ARPA’s information processing techniques office who’d shepherded the creation of ARPANET, to run the CSL until someone else could be found.

Permalink: 20260204154216

Found at “Introducing Deno Sandbox” on 2026-02-04T15:42:16+01:00.

This isn’t the traditional “run untrusted plugins” problem. It’s deeper: LLM-generated code, calling external APIs with real credentials, without human review. Sandboxing the compute isn’t enough. You need to control network egress and protect secrets from exfiltration.

Permalink: 20260203164042

The job of the artist is to expose themselves to as many things as possible to learn everything that came before and feel what resonates here and what resonates there.—Zio Ziegler

Permalink: 20260202155019

You know that there is this version.

And that that’s the version for now.

And that’s when you leave the bubble.

And you leave the piece.

And you let it be.—Katrien van der Schueren

Permalink: 20260130150041

Found at “Beat the Invisible Man: Unforced errors in API design | Redocly” on 2026-01-30T15:00:41+01:00.

Interesting approach by Adam Altman from Redocly. The concept of “unforced errors” is quite interesting.

In API design and documentation, unforced errors look like this:

• an endpoint that behaves differently than described
• a parameter marked optional that’s actually required
• error responses that aren’t documented or actionable
• examples that don’t compile, don’t run, or don’t match reality
• concepts explained, but not when or why to use them

None of these require a competitor. None require scale. None require bad actors.

Near the end of the article, Adam asks if the API works as expected, without surprises. That immediately made me think of my API Hierarchy of Needs (2013), where its second layer (“Functionality”) asks something similar.

Permalink: 20260129101256

Found at “OpenRPC Documentation - Making JSON-RPC Intuitive and Accessible” on 2026-01-29T10:12:56+01:00.

OpenRPC is an Apache-licensed, open standard for describing JSON-RPC APIs—think OpenAPI/Swagger for JSON-RPC. We provide a comprehensive toolkit that simplifies development, testing, validation, and documentation for JSON-RPC APIs.

Permalink: 20260127153749

Found at “hacking clawdbot and eating lobster souls” on 2026-01-27T15:37:49+01:00.

So what can you actually do with Clawdbot Control access?

Read access gets you the complete configuration, which includes every credential the agent uses: API keys, bot tokens, OAuth secrets, signing keys.

You can pull the full conversation history across every integrated platform, meaning months of private messages and file attachments, everything the agent has seen. That alone would be worth the effort for most attackers.

Permalink: 20260127105108

Found at “Unrolling the Codex agent loop” on 2026-01-27T10:51:08+01:00.

You might be asking yourself, “Wait, isn’t the agent loop quadratic in terms of the amount of JSON sent to the Responses API over the course of the conversation?” And you would be right. While the Responses API does support an optional previous_response_id⁠ parameter to mitigate this issue, Codex does not use it today, primarily to keep requests fully stateless and to support Zero Data Retention (ZDR) configurations.

Permalink: 20260120135924

I finally see a concrete focus on improving the way entrepreneurs work in the European Union. Having a single set of rules for the company lifecycle throughout Europe has been needed for a long time.

Found at “Special Address by the President von der Leyen: World Economic Forum” on 2026-01-20T13:59:24+01:00.

The ultimate aim is to create a new, truly European company structure. We call it EU Inc., with a single and simple set of rules that will apply seamlessly all over our Union. So that business can operate across Member States much more easily. Our entrepreneurs, the innovative companies, will be able to register a company in any Member State within 48 hours – fully online. They will enjoy the same capital regime all across the EU. Ultimately, we need a system where companies can do business and raise financing seamlessly across Europe – just as easily as in uniform markets like the US or China. If we get this right – and if we move fast enough – this will not only help EU companies grow. But it will attract investment from across the world.—Ursula von der Leyen, World Economic Forum 2026

Permalink: 20260109130324

Something I’ve been noticing more and more is the way many so-called “tech opinion-makers” keep changing their position on social media. They lack consistency. They keep complaining about life difficulties. They focus their communication on themselves and not on the needs of their audiences. Why this happens is something I can’t understand. However, it seems to attract followers; otherwise, those “influencers” would have already evaporated.

Permalink: 20260108154455

Found at “At Delmonico’s, New York” on 2026-01-08T15:44:55+01:00.

The psychiatrists invited Andy Warhol to entertain them. He brought along The Velvet Underground plus Nico (…) I think the psychiatrists decided to invite Andy in order to gain a better understanding of the underground culture of their clients who were often the alienated children of the rich.

Permalink: 20251229144419

Defining API personas is a crucial step in designing and developing APIs (Pedro 2023). API personas help programs understand the needs, preferences, and behaviors of target users and consumers. Personas ensure developers are creating APIs that meet their specific requirements and testing and validating API functionality across each persona’s use cases.—Application Programming Interface (API) Technical Guidance, Office of the Under Secretary of Defense for Research and Engineering, April 2025

I accidentally found this 120-page report about API Technical Guidance (PDF), published by the U.S. Under Secretary of Defense for Research and Engineering in April 2025. It cites me on content related to API design.

Permalink: 20251203113153

“Outputs have no inherent quality. If we want to make sure that what we’re delivering is a good thing, it has to be independent of the act of delivering it. We have to have a different assessment tool for quality to know that we’ve succeeded. And we have to add that in explicitly."—Jared Spool, What Makes Experience, Product, and Corporate Visions Different, December 2025

Permalink: 20251201175545

Found at “Welcome to Jana’s playroom” on 2025-12-01T17:55:45+01:00.

Well. When I get taller, I can just move the desk up higher can’t I? I won’t need anything else. I can keep it all until I grow up and go to university. I won’t need to get other shelves or a new desk my whole life!

Vitsoe 606 shelving system in action. Books are grouped by language and subject. Some in Catalan, which Jana is learning. Others in English and Sinhala. Stickers, crayons, cuddly toys and schoolbooks are neatly arranged by Jana.

Dieter Rams designed the Vitsoe 606 universal shelving system in 1960, when he was 28. The company has been manufacturing and selling the system ever since. The idea is fabulous. A system that you can use to hang any kind of shelf, table-top, or drawer. It grows with you. And, its quality makes it outlive you.

Permalink: 20251127235550

Found at “LLM APIs are a Synchronization Problem” on 2025-11-27T23:55:50+01:00.

There’s been plenty of talk about unifying message-based APIs, especially in the wake of MCP (Model Context Protocol). But if we ever standardize anything, it should start from how these models actually behave, not from the surface conventions we’ve inherited.

Permalink: 20251120114537

Found at “jentic-public-apis/OAK.md at main · jentic/jentic-public-apis” on 2025-11-20T11:45:37+01:00.

Agents depend on APIs as much as AI. Chatbots chat, but agents act, and they act through APIs: checking calendars, booking flights, analyzing data, reconciling accounts, and controlling smart buildings. To realize this potential, we must build a common knowledge foundation that empowers AI to interact with the world’s APIs reliably and without artificial barriers or unnecessary intermediaries.

Permalink: 20251118160200

Found at “gram/ts-framework/functions at main · speakeasy-api/gram” on 2025-11-18T16:02:00+01:00.

Gram Functions are small pieces of code that represent LLM tools. They are deployed to Gram and are then exposed to LLMs via MCP servers.

Permalink: 20251117163347

Found at “The Rise of Vibes-Based Marketing” on 2025-11-17T16:33:47+01:00.

Marketing used to be about storytelling. Then it became signalling. Now it’s more like atmosphere. It’s emotional infrastructure — ambient, affective, and hard to fake.

Permalink: 20251117103418

They are playing a game. They are playing at not playing a game. If I show them I see they are, I shall break the rules and they will punish me. I must play their game, of not seeing I see the game.—R. D. Laing, Knots

Permalink: 20251111150527

Found at “mock documentation” on 2025-11-11T15:05:27+01:00.

mock is an API utility - it lets you:

• define API routes easily through API configuration files or through command-line parameters.
• use shells scripts as response handlers. Or any other type of program can act as response handlers.
• test your API - make assertions on whether an endpoint was requested.

Permalink: 20251107095948

Simulating an API often requires some logic code. People don’t want to write that code, and they prefer to invest their time implementing the API, not working on a simulation.

One of the challenges with API prototyping with simulations is the time it takes between writing the simulation logic code and seeing it working. My hypothesis is that unless the prototyping is done in an interactive session, people won’t want to spend their time writing simulation code.

Permalink: 20251106150955

Should API operation responses always include references to parent resources? I think so.

Imagine you have the getStoreEmployees operation, which gets all the employees who work in a specific store. The operation is available via an HTTP GET to /stores/{storeId}/employees/{employeeId}. The response includes employee information such as the name, role, and salary. In my opinion, it should also include a reference to the store where the employee works. It can be a full HATEOAS-style or, to simplify things, it can be a shallow reference including only the store’s ID.

Here are some advantages of this approach:

• Contextual clarity: If a resource only makes sense within the scope of a parent (such as the one between employees and stores), then reflecting that parent in the representation makes the relationship explicit and clear for clients.
• Self-descriptive representations: One of the key REST constraints (originating from Roy Fielding’s work) is that messages should be self-descriptive. Embedding parent references adds metadata about relationships.
• Navigation and linking: The parent ID facilitates linking, caching, and client logic (e.g., “which store does this employee belong to?”) without relying purely on the request URI.
• Endpoint structure: If your endpoint is /stores/{storeId}/employees/{employeeId}, it makes sense for the response to also carry storeId so that clients that drop the URI or process the payload standalone still have full context.

Permalink: 20251105112231

What do people understand when they read “API specification?” I feel most people think it refers to the API description document. Most people simply call the API description the spec. In that case, what do they call the type of specification, e.g., OpenAPI, AsyncAPI? We should call it a format.

Here are the two definitions that matter:

• API specification: a formal, structured document that describes how an API works, what it can do, how to use it, and what developers should expect from it.
• API format: how the API itself is documented or modeled, including its structure, endpoints, data types, and authentication. Popular API formats include OpenAPI, AsyncAPI, GraphQL SDL, and Protocol Buffers.

Permalink: 20251105095815

Found at “Why I’m joining Hookdeck” on 2025-11-05T09:58:15+01:00.

Fran Méndez is joining Hookdeck.

By joining Hookdeck to lead Outpost, I’m not changing my mission. I’m accelerating it. I get to take all the theory we’ve been discussing at AsyncAPI and apply it to a real-world product that solves a massive developer pain point.

Permalink: 20251104165550

Found at “Why Jentic Has Joined the OpenAPI Initiative” on 2025-11-04T16:55:50+01:00.

In recent months Jentic joined the OpenAPI Initiative (OAI). The move is deliberate. Our strategy is to bring enterprise API landscapes into the AI age, and to enable agents to reliably and securely use an organization’s capabilities. This requires a standards bedrock that both developers and agents can rely on without guesswork, and this is something that OAI’s standards provide.