buffalobuffalo

Also worth taking a look at is the mimo harness. It's a fork of opencode with some new modes added for long horizon tasks. One of the better open harnesses out there at the moment.

If you are spending time on all text forums like this, you are likely a person whose skill set skews towards the verbalization of abstract concepts. This is also the exact skill set needed to use LLMs well. If you are able to articulate exactly what you want in a concise prompt, little else is needed.

I think we tend to overlook the fact that LLMs have tilted the scales heavily in favor of those with good verbal skills. A huge portion of the population (including a portion of highly skilled software engineers) is not great at doing this. For them, harness skills still act as a kind of scaffolding; they support automated work on a project in cases where insufficient details is given in the prompt.

Or a factory chicken. Do you have any idea how many more factory chicken lives have come and gone as opposed to human lives?

You forgot to mention the part where, to use any of the PWA features, you now have to get the user to close safari, and re-open the page via the icon now on the homescreen. Not exactly easy UI.

No, the fundamental problem is ios. There are a bunch of features that ios locks down so that you are essentially forced to use apps. Want to send push notifications? You need an app. Want to be able to wake your app up in the background to do stuff intermittently? You need an app. Want to get your app on the home screen? Once again, you need an app. And before anyone says you can do this with PWAs, yes, that's true. But the steps required from your users in order to get a PWA running on ios are so cumbersome (by design) that nobody even bothers. And since ios has something like 60% of market share in the US, we're stuck with apps.

If that's a concern, an easy alternative is using companies like novita or fireworks.ai to run open source chinese models. They are incredibly price competitive, have strict data retention policies, and in general are quite fast. Also, you don't get used to a model and suddenly get rug pulled when the provider decide to upgrade.

I mean, that works for you since you're retiring. But for people still working in the industry, you adapt or die. As it's always been.

The fact of the matter is, a person working with a bunch of agents is a lot more productive than just a person. It makes research faster. It makes experimentation faster. It makes output cleaner. And this is true across many disciplines, not just tech.

Also, it is a skill. Yes, anyone can chat with an LLM. But understanding the optimal work flow for what to delegate and what to do yourself is difficult. Understanding the need for precision in the language used, and learning how to elegantly phrase things that were previously just abstract thoughts is absolutely a talent that can be refined.

If i had to guess, I'd say we'll probably see major breakthroughs across multiple disciplines within the next decade, largely because researchers and engineers can cover much more ground individually now, freed from the slow moving coordination mechanisms that team dynamics require. Pretty good for "spicy autocomplete" as you put it.

I use these a lot. My favorite use case is templates, especially ones that were not initially planned in the architecture.

Let's say i have some entity like an "organization" that has data that spans several different tables. I want to use that organization as a "parent" in such a way where i can clone them to create new "child" organizations structured the same way they are. I also want to periodically be able to pull changes from the parent organization down into the child organization.

If the primary keys for all tables involved are UUIDs, I can accomplish this very easily by mapping all IDs in the relevant tables `id => uuid5(id, childOrgId)`. This can be done to all join tables, foreign keys, etc. The end result is a perfect "child" clone of the organization with all data relations still in place. This data can be refreshed from the parent organization any time simply by repeating the process.

While not on the same level as these guys, I've done some similar stuff using Claude. This is a classic synergy example, where the output of human + LLM is far greater than just the human or just the LLM working on a problem. My experience has been that the LLM lacks fine grained judgement when it comes to allocating resources, or choosing a direction to work in. But once a direction is pointed out, it can do a deep exploration of that possibility space. Left alone, it would probably just go off on a tangent. But with someone holding the leash and pointing out areas to explore, it is a very useful partner.

There are two big advantages to using a 3rd party system.

1) There are a lot of cases where aggregated user data, even if anonymized, allows for insights that you can't get using just your own data.

2) The software is really just a stand in for a process. A way of doing something, like record keeping or tax filing, etc. A lot of times it makes sense to follow an already established process rather than creating your own. You are less likely to encounter unexpected pitfalls that way.

I don't see how you can overcome those just by having an AI that can build simple crud apps at will.

So nobody will ever start another successful software project? People will, what, just stop creating software? I understand people's apprehension because of the pace of change, but this is just silly.

Blockchain only has 2 legitimate uses (from an economic standpoint) as far as I can tell.

1) Bitcoin figured out how to create artificial scarcity, and got enough buy-in that the scarcity actually became valuable.

2)Some privacy coins serve an actual economic niche for illegal activity.

Then there's a long list of snake oil uses, and competition with payment providers doesn't even crack the top 20 of those. Modern day tulip mania.

I don't know if a bunch of sloppy jQuery modules were ever really a viable option for an SPA. People tried to do it, sure, but I'd say the SPA era really started with backbone.js

It's still the best RDB schema creation/migration tool I know of. It has a crazy number of plugins to handle all sorts of unusual field types and indexing. I usually add django to any project I'm doing that involves an RDB just to handle migrations. As long as you avoid any runtime use of the ORM it's golden.

I kinda consider it a P!=nP type thing. If I need to write a simple function, it will almost always take me more time to implement it than it will to verify if an implementation of it suits my needs. There are exceptions, but overall when coding with LLMs this seems to hold true. Asking the LLM to write the function then checking it's work is a time saver.