<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://binhsu.github.io/</id><title>Bin's Lab</title><subtitle>Hands-on engineering experiments and field notes.</subtitle> <updated>2026-07-09T19:27:35+02:00</updated> <author> <name>Pin-Feng (Bin) Hsu</name> <uri>https://binhsu.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://binhsu.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://binhsu.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Pin-Feng (Bin) Hsu </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Five AI red flags that mean run away</title><link href="https://binhsu.github.io/five-ai-red-flags/" rel="alternate" type="text/html" title="Five AI red flags that mean run away" /><published>2026-07-09T14:00:00+02:00</published> <updated>2026-07-09T14:00:00+02:00</updated> <id>https://binhsu.github.io/five-ai-red-flags/</id> <content type="text/html" src="https://binhsu.github.io/five-ai-red-flags/" /> <author> <name>Pin-Feng (Bin) Hsu</name> </author> <summary>Self-declared AI-first companies reveal themselves in single sentences. Five signals that separate real adoption from theater, one probe question each — and the closing question that fires past all five.</summary> </entry> <entry><title>Validating a platform for $3: a frugal validation pyramid for solo platform engineers</title><link href="https://binhsu.github.io/validating-a-platform-for-3-dollars/" rel="alternate" type="text/html" title="Validating a platform for $3: a frugal validation pyramid for solo platform engineers" /><published>2026-07-06T11:00:00+02:00</published> <updated>2026-07-06T11:00:00+02:00</updated> <id>https://binhsu.github.io/validating-a-platform-for-3-dollars/</id> <content type="text/html" src="https://binhsu.github.io/validating-a-platform-for-3-dollars/" /> <author> <name>Pin-Feng (Bin) Hsu</name> </author> <summary>No employer footing the bill, no shared sandbox with a leave-it-running culture — every hour a control plane stays up is my money. That constraint quietly made my platform worse, until I inverted who owns what.</summary> </entry> <entry><title>Running k3s on Apple's container runtime — HA clusters, one micro-VM per node</title><link href="https://binhsu.github.io/k3s-clusters-apple-container-k3ac/" rel="alternate" type="text/html" title="Running k3s on Apple&amp;apos;s container runtime — HA clusters, one micro-VM per node" /><published>2026-06-28T14:00:00+02:00</published> <updated>2026-07-09T09:55:21+02:00</updated> <id>https://binhsu.github.io/k3s-clusters-apple-container-k3ac/</id> <content type="text/html" src="https://binhsu.github.io/k3s-clusters-apple-container-k3ac/" /> <author> <name>Pin-Feng (Bin) Hsu</name> </author> <summary>Every local-dev Kubernetes tutorial puts all nodes on a shared kernel. Apple's container runtime breaks that assumption — one micro-VM per node, real DHCP IPs, no Docker daemon. The interesting part came when I tried to make the control plane highly available.</summary> </entry> <entry><title>Platform metrics are four promises, not a list to memorize</title><link href="https://binhsu.github.io/platform-metrics-four-promises/" rel="alternate" type="text/html" title="Platform metrics are four promises, not a list to memorize" /><published>2026-06-19T11:00:00+02:00</published> <updated>2026-07-09T09:55:21+02:00</updated> <id>https://binhsu.github.io/platform-metrics-four-promises/</id> <content type="text/html" src="https://binhsu.github.io/platform-metrics-four-promises/" /> <author> <name>Pin-Feng (Bin) Hsu</name> </author> <summary>Every platform-engineering interview eventually asks how you measure the platform. The weak answer recites DORA. The strong one knows the metrics group into four promises a platform makes — and that most teams only keep two of them. The full reference table, and the one family almost everyone forgets.</summary> </entry> <entry><title>Knative, ECS, and the cognitive load that won't disappear</title><link href="https://binhsu.github.io/knative-ecs-cognitive-load/" rel="alternate" type="text/html" title="Knative, ECS, and the cognitive load that won&amp;apos;t disappear" /><published>2026-06-19T07:00:00+02:00</published> <updated>2026-07-09T09:55:21+02:00</updated> <id>https://binhsu.github.io/knative-ecs-cognitive-load/</id> <content type="text/html" src="https://binhsu.github.io/knative-ecs-cognitive-load/" /> <author> <name>Pin-Feng (Bin) Hsu</name> </author> <summary>ECS and Cloud Run feel effortless because someone else runs the substrate. Knative can match that developer experience — but self-host it and the load doesn't vanish, it moves to your platform team. A look at where the simplicity actually comes from.</summary> </entry> </feed>
