Serverless Cloud Architecture Is Failing Modern AI Agents
As AI agents pushed into production, it became clear the serverless approach could not support them. Agents violate the assumptions that made serverless attractive.
How Advanced Autopilots Make Airplanes Safer When Humans Go AWOL
It’s a cliché in movies that whenever an airplane’s pilots are incapacitated, some distraught crew member queries the self-loading freight if any of them know how to fly a plane. For sm…
Schematics Detailing What Looks Like the Mythical PowerBook G5 Have Appeared - 512 Pixels
This coming weekend marks the 20th anniversary of Apple unveiling the first Intel Macs, which included the MacBook Pro that replaced the PowerBook G4.1 It was no secret that Apple couldn’t shoehorn a G5 into a laptop, but very few details are known about that project’s progress. That may have changed. A user by the […]
Google Cloud’s lead engineer for databases discusses the challenges of integrating databases and LLMs, the tools needed to overcome these challenges, and how AI-native databases will help bridge the gap.
Think about all the things that give you global scale online: The Internet The Web Email RSS Cash Credit Now think about what traps you: Every loyalty, membership, and rewards program Every subscri…
Why Didn’t AI “Join the Workforce” in 2025? - Cal Newport
Exactly one year ago, Sam Altman made a bold prediction: “We believe that, in 2025, we may see the first AI agents ‘join the workforce’ ... Read more
Agents didn't kill libraries—they just changed the math
I've been writing software long enough to remember when "don't reinvent the wheel" was gospel. Find a library. Import it. Move on. The assumption was clear: someone else's maintained code beats your one-off implementation every time.
That assumption is breaking down. Not because libraries got worse—they didn't. Because agents
FPGA Dev Kit Unofficially Brings MSX Standard Back
In the 1980s there were an incredible number of personal computers of all shapes, sizes, and operating system types, and there was very little interoperability. Unlike today’s Windows-Mac duo…
A Steam Machine Clone For An Indeterminate But Possibly Low Cost
For various reasons, crypto mining has fallen to the wayside in recent years. Partially because it was never useful other than as a speculative investment and partially because other speculative in…
The Setun Was A Ternary Computer From The USSR In 1958
[Codeolences] tells us about the FORBIDDEN Soviet Computer That Defied Binary Logic. The Setun, the world’s first ternary computer, was developed at Moscow State University in 1958. Its troub…
Although Nissan has been in the doldrums ever since getting purchased by Renault in the early 2000s, it once had a reputation as a car company that was always on the cutting edge of technology. Nis…
It’s Time To Make A Major Change To D-Bus On Linux
Although flying well under the radar of the average Linux user, D-Bus has been an integral part of Linux distributions for nearly two decades and counting. Rather than using faster point-to-point i…
Courtesy of the complex routing and network configurations that Cloudflare uses, their engineers like to push the Linux network stack to its limits and ideally beyond. In a blog article [Chris Bran…
Building A Steam Loco These Days Is Nothing But Hacks
The Pennsylvania Railroad (PRR)’s T1 class is famous for many reasons: being enormous, being a duplex, possibly having beaten Mallard’s speed record while no one was looking… and …
I feel like this has been said before, more than once, but I want to take a moment to note that
most modern languages converged to the error management approach described in Joe Duffy's
The Error Model,
which is a generational shift from the previous consensus on exception handling.
Writing Load Balancer From Scratch In 250 Line of Code
Hey, everyone. It's another weekend, and I was exploring what to build. So I decided to build a simple yet completely functional load balancer. Let's discuss it in this post.
The Tale of Kubernetes Loadbalancer "Service" In The Agnostic World of Clouds
Prologue
One of the key features for the “GlueOps Platform” to work is installing a LoadBalancer, and because we’re using GlueKube to create kubernetes cluster in a cloud agnostic way, getting the LoadBalancer to work isn’t that easy, as each cloud providers requires different setup, especially for providers with no CCM or in an on-prem installation.
The Birth of the LoadBalancer in the Kingdom of Kubernetes
In the realm of cloud-native deployments, a Kubernetes LoadBalancer Service typically interacts with the underlying cloud provider’s infrastructure through a Cloud Controller Manager (CCM). When a Service of type LoadBalancer is declared, the CCM translates this request into a cloud-specific API call, provisioning a load balancer resource (e.g., an AWS ELB, a Google Cloud Load Balancer, or an Azure Load Balancer) in the respective cloud environment. This external load balancer then directs traffic to the Kubernetes worker nodes where the application pods are running.