HackerLangs
トップ新着トレンドコメント過去質問紹介求人

jryio

1,664 カルマ登録 11 年前
Founder - Sancho Studio (https://sancho.studio)

[email protected].

Prev. Security @ Zoom, Keybase before that, Braintree, MIT Media Lab.

If you're in NYC I'll buy you a bagel and let's have an interesting conversation (jry.io/bagel)

投稿

Can LLMs create lasting flashcards from readers' highlights?

memory-machines.com
1 ポイント·投稿者 jryio·先月·0 コメント

Use Boring Languages with LLMs

jry.io
4 ポイント·投稿者 jryio·2 か月前·0 コメント

Extracting experiments from materials science literature

radical-ai.com
1 ポイント·投稿者 jryio·2 か月前·0 コメント

Can LLMs create lasting flashcards from readers' highlights?

memory-machines.com
1 ポイント·投稿者 jryio·2 か月前·0 コメント

Anthropic's Argument for Mythos SWE-bench improvement contains a fatal error

philosophicalhacker.com
2 ポイント·投稿者 jryio·2 か月前·0 コメント

Show HN: Obscura – V8-powered headless browser for scraping and AI agents

github.com
15 ポイント·投稿者 jryio·3 か月前·0 コメント

GitHub Ace - an Experimental Collaboraite Agentic Coding Environment

maggieappleton.com
6 ポイント·投稿者 jryio·3 か月前·0 コメント

Is All Software Converging

jry.io
3 ポイント·投稿者 jryio·3 か月前·0 コメント

Embarrassingly Simple Self-Distillation Improves Code Generation

arxiv.org
4 ポイント·投稿者 jryio·3 か月前·3 コメント

You are not your job

jry.io
382 ポイント·投稿者 jryio·4 か月前·408 コメント

Assign tasks to Claude Cowork from anywhere

support.claude.com
3 ポイント·投稿者 jryio·4 か月前·0 コメント

Language model teams as distributed systems

arxiv.org
104 ポイント·投稿者 jryio·4 か月前·46 コメント

Fantasy, Build AI agents with Golang by Charm

github.com
3 ポイント·投稿者 jryio·8 か月前·0 コメント

Replacing a $3000/mo Heroku bill with a $55/mo server

disco.cloud
813 ポイント·投稿者 jryio·9 か月前·556 コメント

コメント

jryio
·先月·議論
Designing flow state is really interesting. I've never been lucky enough to build with the intention of having other people enter flow.

8000 hours of Dota 2 had many hours of flow state as the player however..
jryio
·先月·議論
Thanks! Glad you enjoyed it ~ there's flow state in many things, music, crafts, climbing... But I miss the flow state in programming
jryio
·先月·議論
I would do the same for my children ~ However children have a special ability to revolt against any arbitrary constraints provided by parents, community, society. It differs person to person of course.
jryio
·先月·議論
This is a play on words from this (excellent) NYTimes Opinion piece by Jasmine Sun [1] titled "Silicon Valley is bracing for the permanent underclass"

[1]": https://www.nytimes.com/2026/04/30/opinion/ai-labor-work-for...

(Gift article)
jryio
·2 か月前·議論
Correct, even though Ruby the language exists and predates Rails. What -- 80%+ of all Ruby code is Rails? Effectively the largest consumer and producer of the language which I think is a net benefit to your point.

Correct in that Ruby never had a schism and is still massively productive and wideley deployed (e.g. Shopify + Stripe alone represent billions/trillions of dollars through Ruby hotpaths).

Python's general lack of success in this domain is telling and embodies whats I was trying to communicate in the article -- languages with low entropy in syntax, features, ecosystem, and toolchain compound slowly.
jryio
·2 か月前·議論
Author here, wasn't expecting this piece of writing to show up on HN.

The specifics of Python were chosen only due to the language ecosystem being fragmented and inconsistent while Python remains an essential learning, research, and now ML programming language (it was my first language and I still love it).

My thoughts on LLM generated code have changed immensely in the last 9 months as I've taken on teams and projects through my consulting work [1] as a fractional CTO. Python remains a difficult, flakey, and inconsistent programming language for complex production systems. Most other programming languages suffer from fragmented toolchains and ecosystems: JavaScript (famously), PHP, and even C/C++ to a degree.

Languages with a single way to do things benefit the most: Ruby, Rust, Swift (even). Low entropy is the way to go and convention > configuration seems to pay off with LLMs.

Mean cost of management is more important than specific edge examples "X company run on Y language". I think that 'boring' languages with rock-solid compilers, toolchains, testing frameworks, and package managers make for high return on engineering time and production maintenance.

[1]: sancho.studio
jryio
·2 か月前·議論
Send me an email I'd love to make one
jryio
·2 か月前·議論
If you haven't already, read the book "The Second Kind of Impossible" by Paul Steinhardt

https://www.goodreads.com/book/show/35297608-the-second-kind...

It's a riveting account of years of research to discover Quasicrytals from theory, to experiments, to literally hunting in a meteor field in eastern Russia!
jryio
·2 か月前·議論
I am also saying the same thing. They are commenting that the flight of human capital was coming from abroad and is no longer.

However that's not what brain drain means. You would say "Iran had a brain drain in the 70s" not "America was brain draining Iran" makes no sense.
jryio
·2 か月前·議論
If you "drain" something the subject of the verb is what is being drained not where it is draining to.
jryio
·2 か月前·議論
A brain drain means the intelligent population emigrates to other countries.

The narrative and data do not support Americans going abroad.

I think you're referring to a lack of competitive education for those coming outside of America and choosing Europe / China to study.

https://en.wikipedia.org/wiki/Human_capital_flight
jryio
·2 か月前·議論
I run a s business (small if you compare it to tech companies).

I can tell you the drag is between your own tools and the real world (which is very messy and inconsistent): taxes, compliance, payroll, amendments, share structures, etc.

Within my island, my books are in order, invoices and time keeping is fully automated, calendars and sales pipelines are connected.

I'm sure there are many businesses whose inner islands are not as orderly. The zillion tools out there all try to bring equanimity to the chaos and yet here we still are with fresh books, quickbooks, and xero...
jryio
·2 か月前·議論
I'm glad we went to space, truly. Racing the USSR might have been the wrong reason but it got us there. We've benefited immensely as a species from exploring the solar system and looking deep into the universe.

I'm not certain that racing China in AI is the right reason but it might get us... somewhere.
jryio
·2 か月前·議論
Who remembers the Newgrounds games making fun of Bush during the Iraq war?
jryio
·2 か月前·議論
In higher dimensional vector space, yes it can.

Dimensionality gets bizarre in 1000-D space. Similarity and orthogonality express themselves in strange ways and each dimension codes different semantic meaning.

Therefore, if the training data is highly consistent you are by definition reducing some complexity and/or encoding better similarity.

In Go the statement

    result, err := Storage.write(...)

Is almost always going to be followed by

    if err != nil { ... }
In a highly dynamic language you may not get

   try { Storage.write() } catch (error) { ... }
Unless explicitly asked for.
jryio
·2 か月前·議論
Previously in my life as an IC, I wrote a lot of Golang. I worked on the larger end to end encrypted video calling service.

I hated it. I was dreaming of Rust the entire time to release me from the hell of if err != nil dozens of time per day.

After hours with LLMs I've changed my tune. There have been 5 clients of mine (who have excellent engineering teams) but cannot get coherent results out of LLMs using python or Typescript.

I arrived back at Golang being a frustratingly simple, consistent, and low-thrash programming language which inadvertently made itself well represented in the training corpus [1].

My concession is that if you are going to write a median program (reading/writing files, network, db, etc.)...

Pick Golang especially if you've never used it. LLMs are extremely good at it, frustratingly so.

[1] https://jry.io/writing/use-boring-languages-with-llms/
jryio
·2 か月前·議論
I wrote about the meta thesis of programming languages in the training data here

https://jry.io/writing/use-boring-languages-with-llms/
jryio
·2 か月前·議論
I wrote about this here [1]

The big idea with LLMs is consistent references in the training corpus produced cheddar output by the language model during inference.

Go is an amazing language for language models because it's actually quite boring predictable while packing a lot of powerful distractions with a world class tool chain supported by Google and strong std library as well.

As a programmer I actually hated writing Go... and wanted to write Rust; but using coding agents makes me appreciate writing Go more.

I can get consistent results out while having concurrency cross compilation and predictability.

https://jry.io/writing/ai-makes-golang-one-of-the-best-langu...
jryio
·2 か月前·議論
Don't mistake age for durability. A new cast iron pan is durable. The point isn't in providence but in practice. Durable tools (new or old) show themselves immediately.
jryio
·2 か月前·議論
Reminds me of Zed's setting { "disable_ai": true } [1]

Glad it's an option be it for regulatory compliance, security, privacy, or any combination of the three.

[1]: https://zed.dev/blog/disable-ai-features