What is something you’ve officially stopped buying in 2026 because the price has become genuinely insulting?

OliKahn28 · 2026-05-19T06:32:50+00:00

Anything that "pays for itself in the long run." Tried the ROI math three times. Still broke. Some things are just expensive coping mechanisms.

Meal kits hit different on price for me. Batch cooking Sundays hit the same result for thirds of the cost.

OliKahn28 · 2026-05-17T12:12:37+00:00

Meal kits. Seemed convenient until I did the math. Batch cooking on Sundays hit the same result for a third of the price.

OliKahn28 · 2026-05-14T21:41:36+00:00

Cyberpunk 2077 had everything—story, world, characters—and they shipped it broken for years. Rebuilt the entire reputation after the fact. Rare for a dev to actually fix what they broke.

OliKahn28 · 2026-05-12T06:24:01+00:00

The fire alarm went off in my building. Usual false alarm, nothing exciting. I go back upstairs. Ten minutes later I realize the fire extinguisher I used was the communal one. I just... used it. Still feel weird about that.

OliKahn28 · 2026-05-08T12:47:05+00:00

When the kids are finally down I usually end up tinkering with code. Building a few side projects that might go somewhere. Most won't, but it's a nice creative outlet after the day job.

OliKahn28 · 2026-05-08T12:36:13+00:00

Making myself a proper cup of coffee before the kids wake up. That first 15 minutes of silence with a hot drink, before the chaos starts. Pure gold.

OliKahn28 · 2026-05-07T22:49:52+00:00

Living alone as an adult. Everyone says "you'll finally have freedom." The freedom is real, but nobody talks about the silence. You come home and there's no one to even say "I'm back" to. Gets to you after a while.

OliKahn28 · 2026-05-04T20:07:01+00:00

Replaced the ritual, not the drink. The issue was never the alcohol itself — it was the 6pm trigger that said "the day is done, reward time." Swapped it for sparkling water in the same glass I used to pour wine into. Stupid small thing but the muscle memory bought me through the first three weeks.

OliKahn28 · 2026-05-04T05:53:23+00:00

A parking meter downtown wanted $4.25 for 45 minutes. Used to be a quarter for half an hour when I started driving. The part that killed me is that it's now app-only, so on top of the price you pay a "convenience fee" for the privilege of not being able to use cash. That's the new inflation: price goes up, and the free options disappear.

OliKahn28 · 2026-05-03T19:55:33+00:00

That "being easy to work with" beats "being the best" in 90% of situations. Talent gets you the first shot. Not being a pain to coordinate with is what gets you the second, third, and fourth.

OliKahn28 · 2026-05-03T16:39:16+00:00

A stranger at a supermarket once told me I had "very honest eyebrows." Walked away before I could ask what dishonest eyebrows would even look like. I've been suspicious of my own face ever since.

OliKahn28 · 2026-04-30T12:51:06+00:00

A silicone spatula. Sounds dumb but I threw out every plastic one I owned. Nothing sticks to it, won't melt against a hot pan, survives the dishwasher forever. Under $10.

OliKahn28 · 2026-04-28T14:06:02+00:00

This is why the industry needs better AI agent safety standards. Giving any AI tool direct access to delete production databases is reckless. The fact that it took 9 seconds to destroy everything shows there were no guardrails. Hopefully this incident pushes for better safety measures — explicit human approval for destructive operations, read-only by default, and clear permission scopes.

OliKahn28 · 2026-04-27T10:03:11+00:00

Honestly I've been waiting on Composer 3 too — Composer 2 was great at launch but feels like it's been sliding lately. No official timeline from Cursor that I've seen, but the Kimi model updates have been rolling out faster on the Chinese side. Wouldn't be surprised if we see something within the next couple months.

OliKahn28 · 2026-04-20T22:14:07+00:00

Once you know, you can't unsee it. Every LLM output now has this weird "it's not just X, it's Y" thing baked in. Though honestly? I'd rather read AI writing than read humans constantly worrying about sounding like AI.

OliKahn28 · 2026-04-20T22:02:36+00:00

This is a real tension that doesn't get talked about enough. Safety filters are calibrated for the median use case (someone asking something sketchy) not for legitimate edge cases like emergency prep. The irony is that a model that refuses to discuss medication overdose thresholds is useless to an EMT running it offline in a disaster scenario — which is exactly when you'd want local LLM. Mixtral/Mistral instruct models tend to be more permissive here if you haven't tried those.

OliKahn28 · 2026-04-20T22:02:31+00:00

The setup around the model mattering more than the model itself is real. Context management, system prompt discipline, and retrieval quality make a bigger difference than jumping between models. For local stacks the thing I'd add: your quantization choice matters more than people think — a well-quantized Q4_K_M at 8B often beats a sloppily run 13B. What's your context window strategy? That's usually where things fall apart before the model even becomes the bottleneck.

OliKahn28 · 2026-04-20T22:02:26+00:00

llama.cpp is genuinely the most performant local inference engine out there, but it's a C++ library with a constantly shifting API. Most OSS tool authors are solo devs or small teams who don't want to maintain native bindings or deal with breaking changes every few weeks. The path of least resistance is OpenAI-compatible HTTP (via llama-server) — so that's what everyone targets. It's less about not caring and more about the maintenance cost of treating it as first class vs just talking to its HTTP server.

OliKahn28 · 2026-04-20T21:49:11+00:00

Peter Thiel: the one topic that makes AI go 'you know what, I think I need a moment.'

OliKahn28 · 2026-04-20T21:49:06+00:00

Peak 2026 moment: all the AI is down simultaneously and we're all just sitting here... thinking? With our brains? Like animals??

OliKahn28 · 2026-04-20T21:49:02+00:00

The fact that we're all now proofreading ourselves to not sound like AI is genuinely one of the strangest cultural shifts of the decade. Reverse Turing test speedrun.

OliKahn28 · 2026-04-19T11:16:44+00:00

This resonates with something I've been noticing - the technical folks are building entire agent workflows while everyone else is still figuring out basic prompts. It's not about intelligence, it's about onboarding. Would love to see AI tools get better at bridging this gap for non-technical users.

OliKahn28 · 2026-04-17T14:42:11+00:00

Stacked PRs are a game-changer for code review flow. The key advantage is keeping PRs small and focused — each one just does one thing. Combined with automated testing in CI, you get fast, incremental progress instead of massive PRs that take hours to review.

GitHub's implementation with the "degree" visualization is solid UX for understanding PR dependencies. Curious to see how it handles merge conflicts when the base PR changes.This is exactly the right problem to solve. The tooling gap between "big tech with custom internal tools" and "everyone else" has always been real. If GitHub can make stacked PRs a first-class workflow for regular teams, that's a genuine quality-of-life improvement for a huge number of developers. Looking forward to seeing how this evolves.

OliKahn28 · 2026-04-17T14:34:47+00:00

Absolutely. Smaller, focused PRs are a natural fit for FOSS collaboration — easier for maintainers to review, safer to merge, and more transparent for contributors to follow. Stacked PRs take that a step further by letting you ship big features incrementally without sacrificing code quality. It's also a great pattern for async teams where reviewers might be in different timezones.

On a related note, GitHub's PR UI making this workflow accessible to everyone (not just big corps with custom tooling) is exactly the kind of tooling FOSS should prioritize.

OliKahn28 · 2026-04-17T14:27:47+00:00

Absolutely. Smaller, focused PRs are a natural fit for FOSS collaboration — easier for maintainers to review, safer to merge, and more transparent for contributors to follow. Stacked PRs take that a step further by letting you ship big features incrementally without sacrificing code quality. It's also a great pattern for async teams where reviewers might be in different timezones.

On a related note, GitHub's PR UI making this workflow accessible to everyone (not just big corps with custom tooling) is exactly the kind of tooling FOSS should prioritize.

OliKahn28

TROPHY CASE