iamjs

> "but practically speaking [they] are broke"

How do you know this?

They were not claiming a fact, they were posing a hypothetical.

If you haven't watched this talk by Matt Might on Precision Medicine with MiniKanren, you will surely find it inspiring https://www.youtube.com/watch?v=Rt3XyeFHvt4

Reminds me of Borges

Two years ago, I started a new company, and decided at the outset to avoid using any heavy JavaScript SPA framework. We stuck to simple server-rendered html and only use progressive-enhancement style JavaScript.

Our app was fast, and simple, but it also came at a cost: we were limited in our ability to take rich UI elements off the shelf with an npm package. We had to do a lot more work to provide a rich user experience. Everything took longer, and the user experience was worse as a result. We cared, but sometimes you don't have time to carry through.

The company failed, and I don't think react would have saved it. But I can tell you first hand that righteous adherence to "simplicity" didn't help either. It's always a trade-off.

That's interesting. Every evangelical with whom I've spoken seems to be willing to give Israel carte blanche

It's very likely that at some point they had to explicitly tell Claude "don't worry about that and just make an assumption",

Non technical folks vibe coding aren't explicitly telling Claude anything other than "Accept"

The city of Corpus Christi, TX is currently considering options for desalination plants—all of which pump their brine into the shallow water inside the bay or the ship channel.

Not unique to software engineers, but a significant factor is that many technical founders are highly specialized. As a result, they use language from their field, draw on cultural context from their field.

Even in this article:

The marketing playbook for technical founders is just open source logic applied to business.

It's a challenge for us to cross the chasm and meet others in _their_ context. I think that's critical for marketing to be effective.

You would see the same if you hired a medical doctor, or a geologist into a marketing role.

Wow. Never thought I'd see J&J's come up on HN, but as soon as I saw the title, I was intrigued for exactly this reason. I was there too in the early 00's. Small world.

I know the Chernobyl fallout had a pretty significant impact on agricultural in the region, but I don't think I've ever heard about anything similar in New Mexico, Texas, Oklahoma, or Colorado. Why not? Surely there is less agricultural activity on the American West than in Eastern Europe, but is that the only reason?

https://archive.ph/LzM4v

I think the `/remote-control` feature does this, if I understand you correctly.

Might be more effective if this was by postal code instead of by entire country

Cool project! My folks get Cliff Swallows nesting under the eaves above their door in central Texas and they make a huge mess. I wish we could encourage them to nest on the side of the house with some bespoke bricks, but they enjoy the doorway.

This is an unnecessarily rude, dismissive, and low value comment. I loved this game growing up and I think it's fantastic to see this work. I don't find it particularly relevant whether or not a language model was involved.

Sometimes I do this, but sometimes it's just more work than it's worth. I have started to do this a bit more with language models to help reduce the toil, but I yearn for a more rigorous method.

I'm enjoying pasting early 2000's era blog posts in here and learning that they too were LLM slop!

I have long wanted a tool to help split large diffs into smaller semantic changes. When you're working on a feature, for example, and end up refactoring along the way, you may wish to have your refactor reviewed and merged without any new functionality.

I have a volunteer fig tree growing in a container on my patio in the middle of a bunch of onions. I have always heard of people transplanting them from cuttings, presumably because they are difficult to grow from seed. I have no idea how it got there, but I feel fortunate to have been chosen.

This sentiment is quickly becoming the most annoying low-effort comment on HN. If you don't want to read it, don't read it. If something about the writing offends you, then describe it, so we can talk about it.

This is a Markov Chain based generative arpeggiator. It stochastically walks through diatonic chord changes using weights derived from Hook Theory's database of chord change trends in popular music. For each chord, it randomly selects notes from three octaves of arpeggios. It's sort of like an infinite music box.

It's so disappointing that this has become a meme. Lot's of people write with em-dashes. If you want to criticize the _writing_, then do so.

I find that this idea of restricting degrees of freedom is absolutely critical to being productive with agents at scale. Please enlighten us as to why you think this is nonsense

Say I wanted to run the GitHub Action's "self hosted" runner on my own infra, then integrate it with my repo using webhooks (like I would for other CI platforms). What value would I be losing?

I struggled with hand and wrist pain for years from spending too much time at a computer. I did physiotherapy for years and while it helped me manage pain, I was never able to truly build enough strength to get ahead of it until I started bouldering. I took it very slowly—I spent months on very easy problems—but because it was so much fun, I kept going back. Initially, I would only go on Saturday mornings, so I had the full weekend to recover before jumping back into the work week on Monday. After a two or three months of that, I was able to climb anytime I wished. I'm still not a particularly advanced climber, and I typically only go once per week, but I am still slowly progressing, and I absolutely love it.

it could be anything, but virtually everything implements `#to_s`.

Bridging the Gap: Why Not Just Docker Compose?

The draw of a docker-compose-like interface for deployment is so alluring that I have spent the last year or so working on a tool called Defang that takes a compose file and deploys it to the cloud. We don't support Hetzner (yet), but we do support AWS, GCP, and DO. We provision networking, IAM, compute, database, secrets, etc in your cloud account, so you maintain full control, but you also get the ergonomics of compose.

If you are on a PaaS and you want to reduce cost without losing ergonomics and scalability, it might be interesting.

We are building some exciting cloud deployment tools at https://defang.io.

We are making it super easy to manage your deployments through the compose.yaml file you probably already have. The idea is to have a single definition of your application, that you can use locally, and project it into any cloud.

We're a small team based in Vancouver. If you're in town, reach out and come visit: jordan.stephens@defang.io

What are a few of the most interesting things you could possibly say?

At a glance, none of these appear to be meaningfully worse than GPT-4.5