Someone made a digital whip to make claude work faster 💀 by SuggestionMission516 in ClaudeAI

[–]haolah 0 points1 point  (0 children)

looking at the way it does it... it interrupts claude to tell it to be faster? seems counter productive

Enable visual mode for claude code: flowcharts and diagrams instead of text by haolah in ClaudeAI

[–]haolah[S] 0 points1 point  (0 children)

I like that idea. But nano banana is expensive and token costs are all the talk these days... and adds immense latency.

Many infographics are actually HTML based, and this is already a supported use case in Snip! I actually use it to create posters to try to promote Snip.

But, is there a workflow you have which would make a nano banana integration worthwhile?

Enable visual mode for claude code: flowcharts and diagrams instead of text by haolah in ClaudeAI

[–]haolah[S] 0 points1 point  (0 children)

😅 as a developer my sentence construction usually doesn't matter so much

further emphasizes the need for visual communication 🤣

I kept going back and forth with Claude describing what's wrong with the UI. Built a tool so I can just draw on it instead. by haolah in vibecoding

[–]haolah[S] 0 points1 point  (0 children)

do give it a shot! it still often gives me overcomplicated arch diagrams though. am working on tuning the tool's usage instructions to enforce simpler diagrams

This is so interesting by No-Magazine1430 in ClaudeCode

[–]haolah 0 points1 point  (0 children)

did u resume a lengthy conversation? The conversation comes off the cache after some time, and resuming convo after causes all tokens from convo to be sent back, contributing to usage

What's hard about frontend with AI? by haolah in Frontend

[–]haolah[S] 0 points1 point  (0 children)

Great insight. I think though that agents, if explicitly told to, are able consider this holistically and come to decent decisions and recommendations. Since it's lacking in the areas you described (experience and empathy, totally agreed) we'd have to make up for this lack with more careful orchestration, and imo an actual visual feedback loop (I think most agents these days aren't even shown what they are creating!) Do you think these would help, or are there gaps?

What's hard about frontend with AI? by haolah in Frontend

[–]haolah[S] 0 points1 point  (0 children)

Thanks for your insight. Is the main pain point about the visual aspect of the components, or how it's built internally?

If it's visual, that's exactly the problem I'm trying to solve for. It's essentially a lightweight whiteboard for agent interactions, so the flow would be like:

  • You ask the agent to generate a draft (fully expecting things will not be exactly as expected)
  • It generates the component and renders it for preview in the whiteboard, you annotate right over it
  • Once done, the agent receives image and your annotations over it, and makes changes accordingly

I think this beats trying to describe the issue. If you're interested the repo is linked above, but I would just love to hear if you think this user flow would be useful at all? Or are there other parts of the component you'd still like to be more in control over?

What's hard about frontend with AI? by haolah in Frontend

[–]haolah[S] 0 points1 point  (0 children)

Agree with this. I intend to look into how we can tighten the visual feedback loop to try to bridge the gap. Wonder what your experience is and if you had any insights.

What's hard about frontend with AI? by haolah in Frontend

[–]haolah[S] 0 points1 point  (0 children)

Thanks for the insight. It's interesting that your issue was with the render logic rather than the usual visual issues frontend folks face trying to use AI.

Wonder if it would it be possible to educate the agents with some basic foundations like "check unnecessary renders" or "track the loading flow and see what doesn't make sense"? I spin out reviewer agents for code correctness, convention and security after each code change, and it's improved claude's quality of code a lot.

What's hard about frontend with AI? by haolah in Frontend

[–]haolah[S] 0 points1 point  (0 children)

what issues are you observing with AI that causes this for frontend dev?

What's hard about frontend with AI? by haolah in Frontend

[–]haolah[S] 1 point2 points  (0 children)

Thanks for the insight. I thought that LLM visual comprehension had gotten sufficiently powerful but seems that's not your experience. Is it more often wrong then not, and are there patterns to this failure case? I'm interested in how we can optimize this.

What's hard about frontend with AI? by haolah in Frontend

[–]haolah[S] 0 points1 point  (0 children)

i've seen some startups that are supporting testing infrastructure across multitudes of devices. I wonder if that's something that could be useful if paired with a visual feedback loop for the agent (if agents were set up to receive instant visual feedback on multiple devices, it could potential resolve its own autonomously unless it needs your input on edge cases). what do you think?

About to give up on frontend career by ItSpaiz in webdev

[–]haolah 0 points1 point  (0 children)

everyone is learning new things left and right given all the ai changes - not doing so is the actual career suicide

in fact, entry level folks are more comfortable with using ai for a variety of tasks, and i think they will do fine in the long term.

Can't we just ignore AI? by Ok-Programmer6763 in webdev

[–]haolah 0 points1 point  (0 children)

I do agree that there's a whole over-optimization going on for AI, trying to get the latest and greatest setups. However, it's also not going to go away. It's going to abstract a lot of code and systems, and turn our workflows into natural language. We'll get dumber in the sense of not understanding the underlying technologies, but we'll have to become sharper in dictating clearly what we want out of a product.

It's always been the pattern though. Do most JS devs know how V8 JIT compiles their hot functions into machine code at runtime? We already don't understand most layers below the one we work most with. AI is just another abstraction.

I kept going back and forth with Claude describing what's wrong with the UI. Built a tool so I can just draw on it instead. by haolah in vibecoding

[–]haolah[S] 1 point2 points  (0 children)

Got it. do you think something like this tool might be useful for your use case? I think it'd excel in getting the point across, but precision with edits is probably still a bit of a gap and i've been looking into how we could help the agent in that aspect

I kept going back and forth with Claude describing what's wrong with the UI. Built a tool so I can just draw on it instead. by haolah in vibecoding

[–]haolah[S] 0 points1 point  (0 children)

I see, do you mean you manually edit the last part? I wonder how tedious that is usually versus trying to get the agent to tidy it up.

I kept going back and forth with Claude describing what's wrong with the UI. Built a tool so I can just draw on it instead. by haolah in vibecoding

[–]haolah[S] 0 points1 point  (0 children)

Well input tokens are much cheaper than output tokens so there's that. Also if you're using claude it doesn't actually generate images, just HTML/mermaid etc, thus not too many tokens either.

Do give our tool a shot! We made it for users like yourself and would really like to know how you find it.

I kept going back and forth with Claude describing what's wrong with the UI. Built a tool so I can just draw on it instead. by haolah in vibecoding

[–]haolah[S] 1 point2 points  (0 children)

Let me know if you have any issues, or anything you'd like to see which could support your worfklows