As the kids say: 👀 ”This repository provides Authorization support for Spring AI integrations with the Model Context Protocol (MCP). It covers both MCP Clients, MCP Servers, and Spring Authorization Server.” 🔗 spring-ai-community/mcp-security: Spring Security Configuration for MCP

‘JFrog Fly is the company’s agentic developer platform and an MCP server that works with multiple IDEs, including VS Code and Cursor. Integrated with GitHub and observability, Fly provides a chat interface that allows users to query, promote, and roll back existing releases based on specifics of the code (e.g., “Which features were added to this release?” or “Deploy the release that added styling to the user field”). Fly includes an audacious reimagining of the software development process, making versioning automatic and version names obsolete.

Move fast and leak things. 🔗 Senate report accuses DOGE of flouting law, oversight

The AI as a junior engineer theory. 🔗 The AI coding trap

Generate and execute code in Claude’s web app, also pull from GitHub and package managers. What else can you have it do and install in the containers(?) it’s running? 🔗 Claude Sonnet 4.5 is probably the “best coding model in the world” (at least for now)

Ben Thompson recently noted that these prices are spiking, and the AI companies are about to get blamed for it. 🔗 How AI Data Centers Are Sending Your Power Bill Soaring

Others doing D&D with AI. Looks more structured than what I piddle around with. 🔗 The D&D Blueprint: How Role-Playing Engines Can Guide Next-Gen AI

The poor semicolon. 🔗 AI loves an em dash — writers in the US, on the other hand, aren’t so keen

Programmer aesthetics: “your engineering taste is composed of the set of engineering values you find most important.” // And: “most bad taste comes from inflexibility. I will always distrust engineers who justify decisions by saying ‘it’s best practice.’ No engineering decision is ‘best practice’ in all contexts! You have to make the right decision for the specific problem you’re facing.” 🔗 What is “good taste” in software engineering?

They advocate for using JSON (with comments) over YAML: “Generating json as a better yaml Often the choice of format is not ours to make, and an application only accepts yaml. Not all is lost though, because yaml is a superset of json, so any tool that can produce json can be used to generate a yaml document.” 🔗 The yaml document from hell