- Running your domain on HTTPS for free
-
I used CloudFlare ten years ago. It was great then, and still is. Of course, with Let’s Encrypt, free HTTPs is less a benefit, but worry-less HTTPs still is–don’t bother with the mess of cert renewal.
- Dynamic Tool Updates in Spring AI’s Model Context Protocol
-
This blog post explores how Spring AI implements dynamic tool updates in MCP, providing flexibility and extensibility to AI-powered applications.
- Kubernetes v1.33: Image Volumes Graduate to Beta
-
I expected this feature for a long time. I never understood why it wasn’t done already long before: it seems immutable infrastructure isn’t that in demand.
- Communicating in Types
-
The XML bashing at the beginning made me want to stop watching, but the rest of the talk is interesting nonetheless.
Deploying Wasm binaries in WildFly and exposing them as MCP tools
+ video::oEvjWW7MBWM[youtube,width=840,height=473]
- Function calling using LLMs
-
Most articles on MCP try to tell you what it is. The approach taken by the author is to build a shopping assistant that calls an API "by hand" and show you how you can benefit from MCP from there.
- Architectural Decision Record
-
An Architectural Decision (AD) is a justified design choice that addresses a functional or non-functional requirement that is architecturally significant. An Architecturally Significant Requirement (ASR) is a requirement that has a measurable effect on the architecture and quality of a software and/or hardware system. An Architectural Decision Record (ADR) captures a single AD and its rationale; Put it simply, ADR can help you understand the reasons for a chosen architectural decision, along with its trade-offs and consequences. The collection of ADRs created and maintained in a project constitute its decision log. All these are within the topic of Architectural Knowledge Management (AKM), but ADR usage can be extended to design and other decisions (“any decision record”).
You can’t label yourself as an architect if you don’t use ADR in your company.
- Why Big Tech Is Quietly Abandoning Golang
-
- Go’s Simplicity Doesn’t Scale with Complexity
- Error Handling Is a Nightmare at Scale
- Concurrency Is Great — Until It’s Dangerous
- Performance Bottlenecks in Critical Systems
- Developer Ergonomics Matter at Scale
- The Rise of Rust, TypeScript, and WASM
- Internal Migrations Speak Louder Than Words
I tried to learn Go, but stopped because of the error handling part. Seriously, who could defend this approach?
- Using Social Drivers to Improve Software Engineering Team Performance
-
To understand what drives a team to keep performing at a high level, look at their technical and social drivers, Matusov suggested. Technical metrics (like velocity or quality) focus on the efficiency and quality of the output, while social factors (like psychological safety and autonomy) reflect the environment and culture that enable or hinder that output, she added.
- Redis Lost. Or Did They?
-
Interesting take, worth the thought.
- DevOps Roadmap
-
It’s funny that I did a lot of these things before the term DevOps was invented, and even worse, before it was used in a very different way that it was intended to.
- Where Are All the APIs You Consume?
-
Technology changes, but the fundamental issues are there forever. When SOAP was peaking, and REST was confined to an elite circle, we had the same problem: how do you make your service discoverable to the world?
- Platform Engineering: Evolution or Rebranding?
-
The post doesn’t take a hard stance, but at least raises some good points.
- Programming Myths We Desperately Need to Retire
-
- To be relevant, you need the latest
- You should aim for maximum intellectual perfection
- Uncle Bob – Christ of Programming World
- Let’s optimise for performance
- Let’s optimise for scale
- AI is coming to replace programmers
This one particularly rings a bell:
Most products never reach the scale you’re "preparing" for. And even if they do, you’ll have time—and budget—to refactor later.