jryio

Hi Greg it's you!

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..

Thanks! Glad you enjoyed it ~ there's flow state in many things, music, crafts, climbing... But I miss the flow state in programming

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.

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.

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

Send me an email I'd love to make one

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.

If you "drain" something the subject of the verb is what is being drained not where it is draining to.

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...