K3 is as expensive as Sonnet, not great at writing English, is handing IP back to the Chinese, and once open source will be difficult to run at scale without the compute that OpenAI and Anthropic have largely grabbed.
Sorry, how again is this the end of the frontier labs?
Tomorrow is the 15th anniversary of the first day of the Recurse Center.
My cofounders and I did YC all the way back in the Summer of 2010, with the initial idea of building "OkCupid for jobs." That idea quickly fizzled, and we spent the better part of a year pivoting between other ideas that also failed.
Finally, we made something that we wanted ourselves: a self-directed programming retreat, where people built fun projects, contributed to open source, and helped each other become better programmers.
After running two small batches, we launched on HN[1] and got an incredible reception.
That post on HN helped us reach beyond our personal networks and meet programmers from around the world, many of whom have since become friends. HN brought us the majority of people who came to our next few batches, and in the years since, HN has remained our #2 source of applicants (after word of mouth).
Alas, pg's comment[2] on HN when we launched turned out to be prescient: Running free programming retreats isn't a billion-dollar business, but it's still a worthwhile thing to do, and has positively impacted over 3,000 people so far. And 15 years on I still wake up every day excited to keep working on it.
So, thanks HN, for helping make the Recurse Center possible, and for helping me find my life's work.
[2] "This sounds like a crazy plan for a startup, I realize, but this is the right sort of crazy. In fact, the way the Hackruiters think about Hacker School is a lot like the way we initially thought about YC: if it doesn't make money, it will at least have been a benevolent thing to do."
Yes i think an agent trading on polymarket, or running some sort of high frequency trading fund, or something like that, has a lot of potential, i'd love to see someone try that
i'm not sure yet what agents would make sense, it will be interesting to watch and see if someone tries a polymarket bot, or what other use cases people may try it with
What a throwback. I remember reading this guy's build of the "Flying Nimbus" [1]--an early version of the Onewheel--back in 2015. In fact, the Flying Nimbus and the Onewheel were both released in 2014, but it appears they were produced independently, one again demonstrating the curious phenomenon of Multiple Discovery [2].
> But even at 0.12c, we are looking at 400 years to get there. And we'd be zooming by at 12% the speed of light. If we want to slow down a bit that'd add hundreds of billions to the cost.
That’s the really hard part. If it’s almost science fiction to accelerate to 0.12c, it’s certainly much more difficult to slow down. At that speed we’d travel and pass this small system in mere minutes.
As a software engineer, what can we do to help with anthropogenic emissions? I want to know how I can use my critical thinking to protect the future for us.
IMO if we look at Lisps today the question looks more like: SBCL, Chez Scheme, Racket or Clojure.
Common Lisp and Racket are Lisp-2s but honestly, the namespace thing seems like a minor difference compared to all the other features that differentiate them.
Thanks for the openness. I got bit by this one and was, frankly, pretty surprised.
The funny thing about user-facing interaction mechanics is that everyone is part of some minority, and everyone comes with their own sense of what "natural" or "transparent" is. With something this impactful, communicated clarity of behavior will important. Your feature is also doing double-duty, serving as a last net against prompt-injection attacks by giving the user the final say.
(Also, BTW, folks outside of Anthropic are unlikely to be as tooled-up for long-running unsupervised Claude jaunts as you guys. The cost of wild success is wide adoption.)
One thing I'll suggest is that the mechanics of permissions and asking are presently pretty hacker/nerd friendly but simultaneously too-scary and not-scary-enough for non-coders.
Examples:
- Wild-cards on always approve is awesome, but, with prefixes like timeout and nohup, the "thing" that is getting done is buried and largely unexplained to the user.
- Auto is actually kind of a sweet spot (sometimes goes off into the weeds), but the designers and PM's I've been working with might as well YOLO. They have no idea if they're breaking things, but they gravitate between plan and auto mode.
- Fewer permission prompts is great, but it comes after a user has slogged through generation of a data-set to work against, like battle scars for paper cuts. It's the thermostat problem. The signal comes when the user is uncomfortable. And it's a way to learn me, but not me now.
I've had good fortune with Opus 4.8 and Fable just telling the system what phase of my life it's in. Things like "I'm going to go make dinner... Go profile the matrix or configurations and build the dataset for the next two hours while I'm away" have a pretty good hit rate. On the flip side "keep me in the loop and bring me your results before making structural changes" also articulates well with Fable. It will tread more carefully.
And these approaches are the ones we'd use with someone transitioning from SDE1 to SDE2. A little more autonomy, and the grounding in the bigger picture. Can we eventually translate to perfectly judging what the user wants in the moment based on incomplete signal?
No, but I'm glad you're trying. Keep the interaction model clear to your broad set of users, and we'll come along for the ride.
Ive dealt with this error at AWS. It’s a unit error. In my case we _meant_ to charge like 5¢/GB, but missed the unit (GB), and then the billing system defaults to bytes. 5¢ per Byte of data transferred meant some customers were seeing MM bills within hours. Got paged by support around 2am, had it fixed and amendments issues by 3-4am, apology emails shortly after.
Services emit metering values that arent directly tied to prices. Every SKU/line item is defined in a “pricing plan”, with a unit type, regions, and price per unit. The metering records are joined to a pricing plan based on account id, region, sku, etc. mess up the unit type in the pricing plan and the metering data conversion doesnt work, and you get crazy bills.
One interesting thing in the paper that I didn't think of, is that our breathing mechanism is tied to CO2 levels. And therefore, higher CO2 levels (not atmospheric high, but artificially high during studies), can trigger panic attacks and general stress. A slow suffocation hallucination, kind of. Even when there's still sufficient oxygen, your body doesn't "measure" oxygen!
> I recommend putting fingers on keyboard and just trying to find your way through the solution instead of complaining about how impossible life is.
I recommend you stop making stuff up online. We're 10 layers deep into this thread and you still can't explain how any of this works in a coherent way.
If any of this is real, why don't you attach a link from the node documention or an article that explains this technique that allows node to serve type stripped imports over http.
I'm not asking for a link to the http stack, I'm asking you to explain how you run node app that consumes your typescript source code and serves it over http without a bundler.
Hmm, I've had for the car for 20 years (it's even older). Where I originally lived the roads were always smooth + paved well (also elevation was basically flat). Now that I'm in a city with actual hills (along with snow plows that ruin the roads), that's when the problems occurred. Seriously never seen so many potholes before in my life!
Not a cattle grid, but wouldn't have thought of the pothole angle without it.
The original comment is talking about a related phenomena from Richard Feynman's own thought experiment. The article itself is talking about how the brain pays attention to 2 other people speaking at them; its not the same thing. Article focused on monitoring and listening, the comment is talking about one's own brain trying to complete 2 simultaneous tasks consciously.
My memory is that once you begin using the alternate screen, you need to turn on mouse reporting, and then you lose native copy. Different terminal emulators also act totally differently when in this state.
Probably not actually. Transferring one kilobyte across a network link has such a low value that the billing costs of aggregating it cost more than the revenue.
So instead you take a probabilistic approach - charge the user for a megabyte of data transfer 0.1% of the time, and bill nothing 99.9% of the time.
Now the typical cost is the same, the users bill is probably accurate to the cent, but you have divided the number of billing records by 1000.
The analogy being made from piracy to copyright infringement is more about living entirely outside the rule of law and less about the obvious fact that stealing is one of the main things that pirates do. The analogy was first made in reference to unauthorized book publishers, which is pretty close to modern usage (although it used to refer only to the producers of the unauthorized copies, not the consumers). But there's also things like "pirate radio" (unauthorized broadcasts, not necessarily of copyrighted material, and not even necessarily illegal at the source of the broadcast) and "pirate taxis" (simply unlicensed taxi services)
