481–490 of 819 posts
So I guess I should just give up on my dream of having a useful AI assistant for day to day "human" tasks. We're just hell bent on replacing humans in jobs.
nature beckons its creatures to become whatever they must become to be useful in the greater living ecosystem (the loop)
when you can't be useful in the loop you get flushed out of existence
humans who can't be useful will also thus be buffered out of existence
Earlier quoted context omitted.
I too use Stitch, seems like not many have heard of it. Stitch also asks good questions, do you have any examples of both side by side with the same prompt or idea?
Really annoying but I can't figure out how to share a link from Claude Design? It seems to only allow you to share the design with other people on your account? It'll let me export all the HTML and assets, but that's a bit rough to have to download it all and upload it to a host somewhere just to send it to a client for review or something. On Stitch you can just grab a link to the design.
* Massive token usage, some small tasks burned through $50 of credits and did not offer $50 of value.
* Terrible at logo work. Comically bad. This is something that is "hard" so it could add great value if it could deliver.
* Repeatedly forgot prior feedback - when iterating it would re-implement prior iterations after being told why we didn't want that result which made for a very frustrating UX.
* Prone to adding visual clutter - kept adding extra elements that look "pretty" but add no value to the user.
* Seems better at "pretty" vs user focused / UX.
* Did not do a good job at using my existing design / UI library
* REALLY wanted to start from scratch. Could not be coaxed into designing part of an application, it wanted to redesign the whole thing.
I'm not sure if I'm holding it wrong, but at these usage rates, I can hardly see this being useful for designers in their daily work. In two prompts using the Max 20x plan, it consumed 11% of my weekly limit for Claude Design, which is separate from your normal limits. A day of work would exhaust over four weeks of usage. Is this meant for intermittent use only? Lately I've been getting the feeling that Anthropic is…
Earlier quoted context omitted.
I find it a lot more useful to dive into bugs involving multiple layers and versions of 3rd party dependencies. Deep issues where when I see the answer I completely understand what it did to find it and what the problem was (so in essence I wouldn't of learned anything diving deep into the issue), but it was able to do so in a much more efficient fashion than me referencing code across multiple commits on github, doc…
Indeed, many if not most bugs are intellectually dull. They're just lodged within a layered morass of cruft and require a lot of effort to unearth. It is rarely intellectually stimulating, and when it is as a matter of methodology, it is often uninteresting as a matter of acquired knowledge. The real fun of programming is when it becomes a vector for modeling something, communicating that model to others, and talking…
> It's annoying when a distracting and unessential detail derails this conversation
there is no such details.
The model (the program) and the simulation (the process) are intrinsically linked as the latter is what gives the former its semantic. The simulation apparatus may be noisy (when it’s own model blends into our own), but corrective and transformative models exists (abstraction).
> No one argues that we should throw away type checking,…
That’s not a good comparison. Type checking helps with cognitive load in verifying correctness, but it does increase it, when you’re not sure of the final shape of the solution. It’s a bit like Pen vs Pencil in drawing. Pen is more durable and cleaner, while Pencil feels more adventurous.
As long as you can pattern match to get a solution, LLM can help you, but that does requires having encountered the pattern before to describe it. It can remove tediousness, but any creative usage is problematic as it has no restraints.
If you look at Figmas stock price, it started falling right at 11 AM as this news was released. Anyways, this is 100% a shot at Figma, but also catching Lovable in the crossfire. If anybody from Anthropic is reading this, if you keep developing this with features in Figma and other design tools, you'll have a major hit on your hands.
The folks at Wall Street do not understand this does not replace Figma. Figma is targeted towards designers who create thoughtful design systems and cohesive UIs and who don't code, while this is targeted towards vibe coders who can't design. Two different circles that intersect to some level. But like you said, if anthropic adds the tools in Figma, only then they can can take customers from Figma IMO.
> The folks at Wall Street do not understand
On Notes on the Synthesis of Form, Alexander defines design as the rationalization of the forces that define a problem. You’ll won’t find a better definition. But people tend to think design is the synthesis and its results. This misunderstanding of the role of design and the designer is responsible for all the unfit designs we encounter on a daily basis. Anyone equipped with a synthesis tool and feeling empowered to…
Most people just want something that looks nice. I understand it’s deeper to someone really into it, but the rest of us are fine with it.
If you look at Figmas stock price, it started falling right at 11 AM as this news was released. Anyways, this is 100% a shot at Figma, but also catching Lovable in the crossfire. If anybody from Anthropic is reading this, if you keep developing this with features in Figma and other design tools, you'll have a major hit on your hands.
Is this really that big of a moat for Figma to cross though? They would have a much easier time integrating AI than the other way around
Earlier quoted context omitted.
I assure you, working with LLMs is intellectually challenging, and becomes more so as the technology matures.
I find it intellectually exhausting to describe to a machine what I want, when I could build something better in the same amount of time, and it isn't for lack of understanding how the LLM works. It takes a lot of cajoling to get an LLM to produce a result I want to use. It takes no cajoling for me to do it myself. The only time "AI" helps is in domains that I am unfamiliar with, and even then it's more miss than hit…
I don’t even bother. Most of my use cases have been when I’m sure I’ve done the same type of work before (tests, crud query,…). I describe the structure of the code and let it replicate the pattern.
For any fundamental alteration, I bring out my vim/emacs-fu. But after a while, you start to have good abstractions, and you spend your time more on thinking than on coding (most solutions are a few lines of codes).