kyeb

Joined 8 years ago

Karma
487
Submissions
38
Member since
Jul 14
building https://falconer.com

prev @ stripe prev @ MIT

[ my public key: https://keybase.io/kyeb; my proof: https://keybase.io/kyeb/sigs/kQgCa7Rj7IwZS0NcgYCyKyyL5MtQ8fii5qfRTnaa_Ns ]

View on Hacker News

Recent submissions

Comment · 9 months ago
(disclaimer: I work at Falconer)

you would think so! but that's only optimal if the model already has all the information in recent context to make an optimally-informed decision.

in practice, this is a neat context engineering trick, where the different LLM calls in the "courtroom" have different context and can contribute independent bits of reasoning to the overall "case"

Comment · 1 year ago
Comment · 1 year ago
- Learn their default layout first, then iterate on your personal preferences. I similarly tried a bunch at first, but realized switching layouts constantly was making it impossible to build up the new muscle memory.

- Spend time practicing away from important coding tasks (e.g. gaming, writing, a side project, a one-off script, etc.). Being able to learn in a forgiving environment, outside of deadlines, gives you the space to allow mistakes and time to correct them

Comment · 1 year ago
I find one modifier plus a home-row key to be much more comfortable than reaching several rows up for an F-key.

The author's whole point here is that QMK (or ZMK, which I use) lets you customize it to exactly your own needs!

Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
Comment · 2 years ago
What makes you say it's a "left-wing culture war item"? I've gotten the impression opposition to using AI-generated content like this typically comes from artists who might have been paid for similar content in the past
Comment · 3 years ago
The calls per server is probably not the difficult part - this is the type of scale where you start hitting much, much harder problems, e.g.:

- Load balancing across regions [0] without significant latency overhead

- Service-to-service mesh/discovery that scales with less than O(# of servers)

- Reliable processing (retries without causing retry storms, optimistic hedging)

- Coordinating error handling and observability

All without the engineers actually writing the functions needing to know anything about the system (which requires airtight reliability, abstractions, observability).

I don't mean to comment on whether this is impressive or not, just pointing out that per-server throughput would never be the difficult part of reaching this scale.

[0] And apparently for this system, load balancing across time, which is at least a mildly interesting way of thinking about it

Comment · 3 years ago
It sounds like this is about direct carbon cature, not carbon offsets.
Comment · 3 years ago
It would have solved it completely for my family - we just ate cereal or a bagel in the morning for breakfast, no coordination necessary.
Comment · 3 years ago
I'd be super interested to see an analysis using exactly the same methodology as this performed on various other cities (SF, NYC, LA, maybe some European cities like Amsterdam or Cologne) for comparison. I would bet Seattle is near the top for the US in walkability (probably behind NYC only)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton