Blog - Konrad Kowalski (rootsher)
posts (112)
- The Layers of HTTP in the Browser: From fetch() to QUIC3/9
Headers and Body: Metadata vs Representation
A body is bytes, not JSON. Headers say how to read it and steer caching, cookies and CORS, even though the application does not fully control them.
- Part I: From Prompts to Agentic SDLC2/9
Context engineering: stop explaining your project to Claude every time
The second upgrade moves stable project rules from the conversation into the repository, documentation and tools, so Claude does not start every session from…
- Deployment Strategies: Why They Exist6/6
Shadow Traffic: Testing Without Responding to the User
Shadow traffic sends a copy of a request to the new version, but the user receives the old version's response. It tests behavior without taking over traffic.
- Recovery from the Ground Up: Rollback, PITR, and Returning After Failure3/5
Whole-Server PITR: Restore Is Only the Beginning
Whole-server PITR does not end when the database is restored. We still need to freeze writes, validate state, switch traffic, and consciously abandon or move…
- Frontend Rendering: from server-side pages to hybrid rendering17/17
Modern rendering is composition
Rendering stopped being a single stage. It is the placement of work across time, space and runtimes, and the framework is a consequence of those decisions.
- Part I: From Prompts to Agentic SDLC1/9
From chat to agent: stop carrying code to AI
The first upgrade in working with an LLM is that the model stops being a consultant in another tab and starts executing the task directly in the repository.
- The Layers of HTTP in the Browser: From fetch() to QUIC2/9
Methods and Status Codes: Semantics, Not Decoration
The method and the status tell the browser and the infrastructure what may be done with a request. That is why retrying a POST is a different decision than…
- Deployment Strategies: Why They Exist5/6
Feature Flags: Deploy Is Not Release
A feature flag lets you deploy code without enabling behavior. It shortens feature rollback, but creates debt if flags are not removed.
- Testing Through Layers: From Code to Infrastructure6/9
Regression Tests and Smoke Tests: The Gate Before Release
A regression test closes a bug that already passed once, while a smoke test checks whether a version is even worth testing further.
- Deployment Strategies: Why They Exist4/6
Targeted Rollout: A/B Tests, Rings, and Segments
Canary splits traffic by percentage. Targeted rollout chooses specific users, rings, or segments, so it answers a different question.