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