Page 2 — yceffort (English)

20 POSTS

Page 2

◆ Kubernetes for Frontend Developers · Part 4
#kubernetes#devops#debugging
How Do Pods Terminate? Measuring the Causes and Fixes of Deploy-Time Errors
Even a deploy that changes not a single line of code leaks errors. This is a measured record of tagging every failure that leaks during rolling deploys by type and timestamp, performing an autopsy on four causes, and stacking prescriptions one layer at a time until the count reaches zero. Includes the actual Next.js shutdown code, hostage draining, and the real CrashLoopBackOff timetable. Part 4 of the Kubernetes for frontend developers series.
2026-08-08Updated 2026-08-0920 min read
◆ Kubernetes for Frontend Developers · Part 3
#kubernetes#networking#devops
How Does Traffic Reach My Pod? From ClusterIP to port-forward
A Service's ClusterIP is an IP attached to no machine, yet curl reaches it. iptables rules and conntrack, EndpointSlice, cluster DNS and ndots, Gateway, and port-forward: a record of opening up the entire path a request takes to a pod, directly in a kind cluster. Part 3 of the Kubernetes for frontend developers series.
2026-08-0627 min read
◆ Kubernetes for Frontend Developers · Part 2
#kubernetes#docker#devops
How My Next.js App Becomes a Pod: A Record of Opening Up Containers and Pods
The same Next.js app produced one 1.72GB image and one 208MB image. This post traces the missing 1.5GB back through the layers, and verifies with PIDs and cgroup files that a container is an isolated process. The second post of the Kubernetes for frontend developers series.
2026-08-05Updated 2026-08-0919 min read
◆ Kubernetes for Frontend Developers · Part 1
#kubernetes#devops
A Kubernetes Concept Map for Frontend Developers: From Pods to Autoscalers
The Kubernetes vocabulary and structure that frontend developers running SSR actually encounter, organized in the order of real work: the overall cluster structure, what makes up a deploy, pod state and resources, the traffic path, and autoscaling. The first post of the series and the reference map for the rest.
2026-08-05Updated 2026-08-0922 min read
◆ Kubernetes for Frontend Developers · Part 6
#memory#nodejs#kubernetes
Why Is Your Node.js Pod That Size? Sizing Measured Firsthand, from NODE_OPTIONS to Pod Count
I added one GC tuning flag to the same workload and peak RSS jumped from 201MB to 593MB, while the live data stayed the same. This post traces back through V8 New Space with direct measurements to show why that result is exactly what should happen, and lays out the three axes frontend developers can use to size a Node.js pod.
2026-08-03Updated 2026-08-0945 min read
#essay#ai#design-patterns
Where Frontend Came From, and Where It Goes After Agents
Why the layers piled up, why we returned to the server, and why the stack survives even after agents. And why the survival of a stack and the value of the people who know it are two separate things
2026-07-2219 min read
◆ Judgment in the AI Era · Part 3
#essay#ai#career
When Was the Last Time You Read Code Seriously?
The friction that made judgment expensive is the same friction that taught it. Why the skill growing most valuable in the AI era is the one being cultivated least
2026-06-2113 min read
◆ Judgment in the AI Era · Part 1
#ai#essay#career
If the Code Meets Spec and the Bugs Get Fixed, Does It Matter That You Can't Read It?
If the spec is satisfied and the bugs get fixed, do you still need to be able to read the code? Understanding doesn't disappear — this essay traces where it moves.
2026-06-1222 min read
◆ Judgment in the AI Era · Part 2
#ai#essay#software-engineering
If AI Erases the Boundaries Between Planning, Development, and Design, What Remains?
The claim that job boundaries are collapsing is only half true. What collapses is production; judgment and responsibility remain.
2026-06-1220 min read
#react#caching
React cache() Deep Dive: Request-Scoped Memoization, Read from the Source
Every odd rule of React's cache() falls straight out of a ~30-line implementation. We trace the dispatcher, getCacheForType, and the WeakMap/Map tree at the source level to see exactly how request-scoped memoization works.
2026-05-30Updated 2026-06-0322 min read
#security#ci-cd#npm
The TanStack npm Supply Chain Attack: Why pull_request_target Is Dangerous
Analysis of the @tanstack/* supply chain incident. The risks of pull_request_target, GitHub Actions cache, and OIDC trusted publishers, and how to defend against them.
2026-05-1624 min read
#oss#ai#essay
Bun rewrite Exposed Something: OSS Could Only Stop External AI
Bun moved roughly 960,000 lines from Zig to Rust in six days using Claude Code. The meaning here is not code quality but OSS governance and resource asymmetry.
2026-05-15Updated 2026-05-1928 min read
#npm#essay#oss
What makes a package you can keep using for years different
A good package has to be user-friendly not just in features, but in dependencies, version bumps, compatibility, and release policy.
2026-05-0920 min read
#bundler#code-review#web-performance
The invisible cost in PR diffs: we are not reviewing the code our users receive
The bundle costs that code review misses, and how to surface them in the PR.
2026-05-0322 min read
◆ Directive Deep Dive · Part 3
#react#nextjs#caching
'use cache' Directive Deep Dive: To the End of Cache Boundaries
Build-time transformations, cache key serialization, ResumeDataCache, cacheHandler, and Cache Components - everything created by a single 'use cache' line
2026-05-01Updated 2026-09-0440 min read
◆ Directive Deep Dive · Part 1
#react#nextjs#bundler
'use client' Directive Deep Dive: To the Edge of Client Boundaries
Module boundaries created by a single line of 'use client', build-time transformations, Flight serialization, and performance implications
2026-05-0133 min read
#ai#career#essay
AI Only Amplifies Me to the Level I Can See
I'm definitely coding faster, but why are my codebase and skills staying the same? Examining the gap between perceived and proven benefits.
2026-04-2017 min read
◆ The State of Next.js · Part 5
#nextjs#essay#serverless
Why We Still Use Next.js
Switching costs stronger than technical superiority
2026-03-23Updated 2026-03-2519 min read
◆ The State of Next.js · Part 4
#nextjs#web-performance#react
Is Next.js Fast Enough?
The uncomfortable truth benchmarks reveal
2026-03-2123 min read
◆ The State of Next.js · Part 3
#oss#react#software-engineering
Whose React Is It?
The questions React Foundation must answer
2026-03-1921 min read