Anthropic redeployed Claude Fable 5 on July 1, 2026, after a three-week suspension. The model went dark on June 12 when US export controls kicked in without warning.
Claude Sonnet 5: Model Agentic Pertama yang Bisa Coding dan Tool Use Setara Opus
Claude Sonnet 5 baru saja dirilis Anthropic dengan klaim ambisius: ini adalah model Sonnet paling agentic yang pernah ada. Bisa membuat rencana, menggunakan tools seperti browser dan terminal, serta berjalan secara otonom di level yang beberapa bulan lalu hanya bisa dilakukan model besar dan mahal. Yang menarik, Sonnet 5 ini performanya mendekati Opus 4.8 — … Read more
TLS 1.3 Features. What Changed From TLS 1.2. And Why It Matters
TLS 1.3 shipped in 2018 as RFC 8446. It is the biggest overhaul of the TLS protocol since SSL 3.0 in 1996. Five years after release, TLS 1.3 now protects over 70 percent of HTTPS connections. The upgrade is not incremental. It changes how the handshake works. It removes broken cipher suites. It mandates forward secrecy. And it makes the protocol faster.
This post covers what TLS 1.3 adds. What it removes. And why the changes matter for anyone running a server or building a client.
SSL Is Dead. TLS Runs The Web. Here Is What Actually Encrypts Your Traffic
Every HTTPS connection on the modern web uses TLS. Not SSL. The padlock icon in browsers still says SSL. Hosting providers sell SSL certificates. Devops teams talk about SSL termination. But SSL has been dead since 2015. What actually protects traffic is TLS 1.2 or TLS 1.3.
This distinction matters. SSL and TLS are not the same protocol. They have different security properties. Different handshake flows. Different cipher suites. One of them has known vulnerabilities that attackers can exploit.
60 Percent of My API Calls Were Cached. I Turned It Off.
60 Percent of My API Calls Were Cached. I Turned It Off.
It is Tuesday afternoon. I am looking at my Grafana dashboard. The cache hit rate says 60 percent. Six out of ten API requests are being served from Redis, not the database.
By every metric I learned, this should be a win. Cache hits are fast. Database queries are slow. The math is simple.
But my p95 latency went up 40 milliseconds after I added caching.
Not down. Up.
I spent three days chasing this. I added more cache. I tuned TTLs. I pre-warmed the cache with likely queries. Nothing helped. The more I cached, the slower things got.
Then I found the bug. It wasn’t in the cache layer. It wasn’t in the database. It was in my assumptions about what caching actually does.
Weekly Roundup #27 — AI Agents, RAG, and What Worked
This week: AI agent workflows, RAG architecture, and the real 80/20 of coding with AI. 9 posts, top insights, and what is next.