HNHacker News
TopNewBestAskShowJobs

coffeecoders

899 karma · joined June 2, 2025

Full-stack engineer (North America, Pacific time) with deep production experience in RabbitMQ and Kafka at scale.

When not writing code, I'm either breadboarding electronics or hiking in the mountains.

Email: ntemail (at) protonmail.com

submissionscomments
coffeecoders··on Ask HN: What are you working on? (Jan 2026)
Nice, Linear is a perfect target for this mindset.

The REST client went surprisingly smoothly once I committed to keeping it boring.

I'm building Mac apps in Xcode, and I keep multiple small apps in a single Xcode project with a few shared libraries (basic UI components, buttons, layout helpers, etc. to keep all my apps similar).

The REST client is literally just another target + essentially one extra file on top of that. No workspaces, no collections, no sync, no plugins. Just method, URL, headers, body, hit send, show response. Requests are saved and loaded as plain local JSON.

What surprised me is how little code is actually required once you strip away "product features".

coffeecoders··on Ask HN: What are you working on? (Jan 2026)
I’ve been vibe-coding replacements for the tools I actually use every day. So far: a Notepad, a REST client, a snipping tool, a local gallery and lightweight notes for iPhone.

The motivation isn't novelty. It's control. I don't need ads, onboarding flows and popups, AI sidebars, bloated menus, unnecessary network calls , etc. A notepad should never touch the network. A REST client shouldn’t ship analytics or auto update itself mid-request.

No plugin system. No extensibility story. Just plain/simple software.

As I build these, I have been realizing how much cognitive overhead we’ve normalized in exchange for very little utility.

coffeecoders··on Apple releases open-source model that instantly turns 2D photos into 3D views
I feel like being in a time loop. Every time a big company releases a model, we debate the definition of open source instead of asking what actually matters. Apple clearly wants the upside of academic credibility without giving away commercial optionality, which isn't unsurprising.

Additionally, we might need better categories. With software, flow is clear (source, build and binary) but with AI/ML, the actual source is an unshippable mix of data, infra and time, and weights can be both product and artifacts.

coffeecoders··on Ask HN: What are your predictions for 2026?
My prediction: 2026 looks normal.

AI stays the top story but in a boring way as novelty wears off and models get cheaper and faster (maybe even more embedded). No AGI moment. LLMs start feeling like databases or cloud compute.

No SpaceX or OpenAI IPO moment. Capital markets quietly reward the boring winners instead. S&P 500 grinds out another double digit year, mostly because earnings keep up and alternatives still look worse. Tech discourse stays apocalyptic, but balance sheets don't.

If you mute politics and social media noise, 2026 probably looks like one of those years that we later remember as "stable" in retrospect.

Bonus: Bitcoin sees both 50k and 150k.

coffeecoders··on Coursera to combine with Udemy
I've realized over time that I personally cannot learn from video at all. Even "great" lectures don't stick. Text does!

Being able to skim, jump around, re-read a paragraph or pause on a single sentence is how understanding actually forms for me.

What’s interesting is that LLMs lean hard into this strength of text, they make it interactive, searchable, and contextual.

To me, most of these platforms have optimized video for engagement. Its essentially "press play and hope it sticks".

coffeecoders··on Pricing Changes for GitHub Actions
Charging by minute might push people toward shorter, noisier and more fragmented pipelines. It feels more like a lever to discourage selfhosting over time.

It's not outrageous money today, but it's a clear signal about where they want CI to live.

coffeecoders··on Thin desires are eating life
Us software engineers assume value comes from serving more people, faster, with less friction. But many of the things that actually make life feel coherent such as learning a craft, maintaining friendships and building tools for one person, only work because they’re slow and specific.

Tech doesn't give us the wrong desires but the easier versions of the right ones, and those end up hollow.

coffeecoders··on How I block all online ads
I have an Apple TV and I’ve been running iSponsorBlockTV [1] on my Synology box for a while. It auto-skips the sponsored segments and with Youtube premium, it gives me a clean, ad-free setup.

I can’t stand those in-video intros or sponsored promos, where I’m suddenly pitched a random VPN or productivity app.

[1]. https://github.com/dmunozv04/iSponsorBlockTV

coffeecoders··on Launch HN: Phind 3 (YC S22) – Every answer is a mini-app
This is good. It’s fascinating how it spins up interactive pages instantly. Some of the mini-apps actually feel useful, but others break in ways you wouldn’t expect.

I’m curious to see how it evolves with more complex, multi-step queries.

coffeecoders··on RCE Vulnerability in React and Next.js
Not quite. This isn’t saying React or Next.js are fundamentally insecure in general.

The problem is this specific "call whatever server code the client asks" pattern. Traditional APIs with defined endpoints don’t have that issue.

coffeecoders··on RCE Vulnerability in React and Next.js
This vulnerability is basically the worst-case version of what people have been warning about since RSC/server actions were introduced.

The server was deserializing untrusted input from the client directly into module+export name lookups, and then invoking whatever the client asked for (without verifying that metadata.name was an own property).

    return moduleExports[metadata.name]

We can patch hasOwnProperty and tighten the deserializer, but there is deeper issue. React never really acknowledged that it was building an RPC layer. If you look at actual RPC frameworks like gPRC or even old school SOAP, they all start with schemas, explicit service definitions and a bunch of tooling to prevent boundary confusion. React went the opposite way: the API surface is whatever your bundler can see, and the endpoint is whatever the client asks for.

My guess is this won't be the last time we see security fallout from that design choice. Not because React is sloppy, but because it’s trying to solve a problem category that traditionally requires explicitness, not magic.

coffeecoders··on Ask HN: Who wants to be hired? (December 2025)
Location: Vancouver, BC, Canada

Remote: Yes (preferred)

Willing to relocate: No

Role (Current): Senior Full-Stack Engineer, Bay area.

Resume/CV: Available on request

Email: ntemail (at) protonmail.com

Technologies & Expertise:

- 10+ YOE in TypeScript, JavaScript, Node.js

- High-throughput messaging & event systems - Kafka, RabbitMQ, AWS SQS/SNS, EventBridge

- PostgreSQL (including Citus, Timescale), Redis, OpenSearch/Elasticsearch

- RAG systems (LlamaIndex, LangChain, custom vector stores), Fine-tuning & interence (Llama 3, Phi-3)

- Vector DBs: Pinecone, PGVector

Currently looking for Senior/Staff Full-Stack or LLM Engineer roles.

coffeecoders··on A new AI winter is coming?
I am of a belief that upcoming winter will look more like normalization than collapse.

The reason is hype deflation and technical stagnation don't have to arrive together. Once people stop promising AGI by Christmas and clamp down on infinite growth + infinite GPU spend, things will start to look more normal.

At this point, it feels more like the financing story was the shaky part not the tech or the workflows. LLMs’ve changed workflows in a way that’s very hard to unwind now.

coffeecoders··on People keep flocking to Linux, not just to escape Windows
I don't know who said it, but it fits the current Windows vs Linux moment perfectly. "Most people don’t want control. They want optionally having control."

Windows gives you the worst of both worlds. It restricts the control over the things that matter, and dumps unnecessary knobs on everything else.

Linux flipped that. It stays out of your way, lets you change what you actually care about, and never fights you for ownership of your own computer.

Linux won/is winning because it quietly became the place where your computer feels like yours again.

coffeecoders··on Show HN: Boing
Funny thing: this feels "realistic" because it’s not perfect physics. A perfectly simulated Hooke's law spring actually looks fake and too stiff. But if you let the animation wobble a bit more and slow down the damping, our brain reads it as weight and squishiness.

It’s basically controlled sloppiness.

coffeecoders··on Show HN: Explore what the browser exposes about you
No, visiting a URL does not automatically expose your exact latitude and longitude.

I just get approximate location from your public IP address via an external IP geolocation API (ipapi.co), which usually gives city-level accuracy.

coffeecoders··on Show HN: Explore what the browser exposes about you
Thanks! The Unique Fingerprint ID is basically a hash of all the collected fingerprint fields. [1]

The Canvas Deep Fingerprint Hash is higher entropy and includes baseline shapes, emoji rendering, winding rules etc. [2]. It’s meant to capture subtle rendering differences between systems.

1. https://github.com/neberej/exposedbydefault/blob/main/src/mo...

2. https://github.com/neberej/exposedbydefault/blob/main/src/mo...

coffeecoders··on Show HN: Explore what the browser exposes about you
Yeah, I made the mistake of including all features, even ones that change on every refresh like canvas or audio.

The fingerprint should really only use stable features that don’t fluctuate between reloads. That way it’s consistent for the same device.

coffeecoders··on Show HN: Explore what the browser exposes about you
You're 100% right. The raw fingerprint dumps alone are not actually useful unless you can compare them to a population.

And creating that comparison is far harder than people think. To answer "How unique am I?" I need a large, representative dataset of fingerprints collected over time and ideally weighted by how often real websites use each feature. That would require running an backend and database.

It’s something I’d like to build eventually, but only in a privacy-preserving, opt-in way that aligns with the spirit of the project.

coffeecoders··on Tell HN: Want a better HN? Visit /newest
If we all rely on others to skim /newest, the whole curation system collapses. Maybe the homepage should surface a couple random fresh posts too?
coffeecoders··on AI CEO – Replace your boss before they replace you
Interesting approach, but I mean more in the sense of a multi-agent sandbox than workflow automation. Your project feels like wrapping a bunch of LLMs into "agents" with fixed cadences, it is a neat product idea, even if it mostly ends up orchestrating API calls and cron jobs.

The thing I’m curious about is the emergent behavior, letting multiple LLMs interact freely in a simulated organization to see how coordination, bottlenecks, and miscommunication naturally arise.

Cool project regardless!

coffeecoders··on AI CEO – Replace your boss before they replace you
How hard would it be to run a simulator with multiple LLMs. Say, one as the boss and a few as employees. Just let them talk, coordinate, and "work"? Could be the fastest way to test what actually happens when you try to automate management.
coffeecoders··on We're losing our voice to LLMs
Yes. That particular content-farm business model (rewrite 10 articles -> add SEO slop -> profit) is effectively dead now that the marginal cost is zero.

I’m not mourning it.

coffeecoders··on We're losing our voice to LLMs
I’m not sure I agree with this sentiment. You can type something "by hand" and still have almost no voice in it if the incentives push you to flatten it out.

A lot of us spent years optimizing for clarity, SEO, professionalism etc. But that did shape how we wrote, maybe even more than our natural cadence. The result wasn’t voice, it was everyone converging on the safe and optimized template.

coffeecoders··on We're losing our voice to LLMs
I actually think we’re overestimating how much of "losing our voice" is caused by LLMs. Even before LLMs, we were doing the same tweet-sized takes, the same medium-style blog posts and the same corporate tone.

Ironically, LLMs might end up forcing us back toward more distinct voices because sameness has become the default background.

coffeecoders··on MIT study finds AI can replace 11.7% of U.S. workforce
I think the real story isn’t that AI will replace 11.7% of workers. It is that we are about to discover that far more than 11.7% of the work we do was never actually work in the first place.

Workflows that were untouchable will now be overhauled and the productivity gains just raises the throughput ceiling.

coffeecoders··on Show HN: Explore what the browser exposes about you
Hi HN,

I’ve been experimenting with ways to reduce my browser fingerprint and exploring techniques to anonymize fingerprint data.

So I built this.

This is kind of like a lighter, more thorough version of CreepJS but entirely client side. I don’t maintain massive lists of time zones or do server-side comparisons to calculate uniqueness. Instead, it automatically surfaces everything a browser exposes, explaining each item in detail.

coffeecoders··on Gemini 3
Feels like the same consolidation cycle we saw with mobile apps and browsers are playing out here. The winners aren’t necessarily those with the best models, but those who already control the surface where people live their digital lives.

Google injects AI Overviews directly into search, X pushes Grok into the feed, Apple wraps "intelligence" into Maps and on-device workflows, and Microsoft is quietly doing the same with Copilot across Windows and Office.

Open models and startups can innovate, but the platforms can immediately put their AI in front of billions of users without asking anyone to change behavior (not even typing a new URL).

coffeecoders··on Israeli-founded app preloaded on Samsung phones is attracting controversy
I bought an Ipad yesterday. The setup was almost the same, except all the bloat was from Apple itself. Numbers, GarageBand, iMovie, Keynote, Pages, Clips… even the Tips app felt like bloatware.

Wild how every ecosystem has its own "preloaded surprise pack."

coffeecoders··on AI World Clocks
LLMs are terrible for out-of-distribution (OOD) tasks. You should use chain of thought suppression and give constaints explictly.

My prompt to Grok:

---

Follow these rules exactly:

- There are 13 hours, labeled 1–13.

- There are 13 ticks.

- The center of each number is at angle: index * (360/13)

- Do not infer anything else.

- Do not apply knowledge of normal clocks.

Use the following variables:

HOUR_COUNT = 13

ANGLE_PER_HOUR = 360 / 13 // 27.692307°

Use index i ∈ [0..12] for hour marks:

angle_i = i * ANGLE_PER_HOUR

I want html/css (single file) of a 13-hour analog clock.

---

Output from grok.

https://jsfiddle.net/y9zukcnx/1/

← PreviousPage 2 of 5Next →