i love the mkdir example, so i’m going to exercise that muscle and see where it goes
and yeah ^r works, though i often type a few chars and ^p till i get the match. history-search-backward in your inputrc, iirc
edit: on a computer now :) my `if emacs` block, allowing arrows or ^n/^p to run through history. so for e.g., type "tar" and now as you shift through history with :binding:, it only shows history that began with "tar"
I'd improve it by counting top level comments next to items but that would slow it down. Still need to make some slight changes like closing sidebar by re-clicking orange (beyond just right-clicking sidebar.)
right, you're using the tool for the job. author was reaching for reliability, re: OTP/beam. now we don't know if they actually needed it, but, you're saying the same thing to me
It was the BEAM process/actor model that fit much better for managing agents, and then there was the out-of-the-box live UI with Phoenix/LiveView that was really appealing. I had started the project in Typescript/Node (because that's my company's primary stack choice), but it hit a plateau in reliably managing multiple independent long-lived agent processes (not really what Node is designed for). I could have used an even more boring tech like Go with more robust process management, but Elixir and Phoenix also came with a lot out of the box. It's no surprise that OpenAI's reference project for agent orchestration (https://github.com/openai/symphony) is also written in Elixir.
i see one person saying it is now cheap to support the new hotness, which previously would have been its own project, and another saying it has become cheap again to do things the boring-yet-reliable way that maybe didn’t used to scale so great.
that's fair. probably i attached more weight to the opening line: "We're in an interesting time where my framework/stack choice is now much less dictated by existing engineer expertise and more about fundamental capabilities in the framework and stack themselves."
assuming author wouldn't choose X _just because_ it is the new hotness
The button on the homepage is hardcoded to this book, which I find extremely strange. Why not choose a random book, and why pick such a confusing quote?
I got through an entire day yesterday in massively oversized gym shorts, by simply forming a standard loop, and wrapping it _twice_. That extra friction (the second wrap) has worked for years on shoes, boots, and, very large shorts
I will not be learning a fancy knot because I have no need
Totally absolutely agree with this. The second wrap or second turn totally solved my problem of slipping knots in shorts and shoes. Game over. Chapter closed for me.
they're right, we're wrong. look, if you got XXXL shorts on a medium waist and tie an _excellent_ standard knot, and you are very active for a while? those shorts are gonna loosen up for sure
this knot rules, i'm glad i went back and tried it :)
https://www.rmca.org/Articles/recipes1.htm
reply