121–130 of 266 posts
I'll be interested to hear stories - down the line - from the participants in the the LLM SEO war [1]. Interesting that tailwind won out decisively in their niche, but still has seen the business ravaged by LLMs. [1] https://paritybits.me/copilot-seo-war/
It's like tailwindcss was purposely designed to be managed my LLM.
Earlier quoted context omitted.
We used to reuse code a lot. But then we got problems like diamond dependency hell. Why did we reuse code a lot? To save on labor. Now we don't have to. So we might roll-your-own more things. But then we'll have a tremendous amount of code duplication, effectively, and bigger tech debt issues, minus the diamond dependency hell issue. It might be better this way; time will tell.
Speaking of rolling your own things, i had claude knock out a trello clone for me in 30 minutes because i was irritated at atlassian. I am already using it for keeping track of personal stuff. I’m not going to make a product out of it or even put it on github. It’s just for me. There are gonna be a lot of single team/single user projects. It is so fast to build working prototypes that it’s not even worth thinking if…
[dead]
I'm not expressing an opinion about that; it's a real question.
Earlier quoted context omitted.
from my understanding Anthropic are now hiring a lot of experts in different who are writing content used to post-train models to make these decisions and they're constantly adjusted by the anthropic team themselves this is why the stacks in the report and what cc suggests closely match latest developer "consensus" your suggestion would degrade user experience and be noticed very quickly
I guess that’s why I’m not seeing anyone trying to build a skills marketplace for agent skills files. The llm api will read in any skills you want to add to context in plain text, and then use your content to help populate their own skills files.
But how to do things in your environment? The conventions your team follow? Super useful but not very shareable.
Whats left over between those extremes does not seem to be big enough to build an ecosystem around.
Final problem, it seems difficult to monetise what is effectively a repo of llm generated text files.
Earlier quoted context omitted.
> Claude Code likely is correct that I should start to use NeonDB and Fly.io which I have never used before and do not know much about I wouldn't be so sure about that. In my experience, agents consistently make awful architectural decisions. Both in code and beyond (even in contexts like: what should I cook for a dinner party?). They leak the most obvious "midwit senior engineer" decisions which I would strike down…
I find they are very concerned about ever pulling the trigger on a change or deleting something. They add features and codepaths that weren't asked for, and then resist removing them because that would break backwards compatibility. In lieu of understanding the whole architecture, they assume that there was intent behind the current choices... which is a good assumption on their training data where a human wrote it,…
// deprecated; use ThingTwo instead
type Thing = ...
// deprecated; use ThingThree instead
type ThingTwo = ...
// deprecated; use...
This is one reason why it blows me away that people actually ship stuff they've never looked at. You can be certain it's riddled with craziest garbage Claude is holing away for eternity
[dead]
I recommend starting projects by first creating a way of doing (architect) and then letting Claude work. It's pretty good at pretending to be you if you give it a good sample of how you do things.
Note: this applies to Opus 4.6. I have not had a useful experience in other models for actual dev work.
[dead]
But what if tailwind has the most tutorials in the training set because it's worth learning, which led to it being fairly ubiquitous and easy to add to the training set? I'm not expressing an opinion about that; it's a real question.
I'm not expressing an opinion about that, I don't do front end dev so I have no opinion, it's a real question.