Ask HN: What's your daily IDE pain point that AI tools haven't solved?

1 point·namanyayg··9 comments

I've been using VSCode with Copilot and Cursor with their AI features. While they solve code completion well, I'm curious what daily dev workflows still feel broken.

What's a task that takes you 2-3x longer than it should, even with current AI tooling?

View on HN

Making a PR for a repo I don't have write access to. It's annoying to have to manually fork it, set my own repo as a new remote, push to it, and then manually go to Github to start a PR from my fork to the main branch in the original.

i hate interacting with the github website interface, probably need to set up terminal aliases for my common workflows

Probably recording playwright tests. AI could probably help generate nicer selectors?

Interesting, is it the selector specifity that's the only problem or something else as well?

There's definitely other issues, some are just regular bugs, and features that would be nice to have, like the number input flakiness with Vue.

One other time consuming thing is commenting test code, and figuring out what it actually does.

Automatically adding section headers and comments based on what was on the screen might be helpful, but those comments could then get out of sync, so it would have to have pretty good judgement to decide what was worth including.

Configuring correctly for cross compiling (and cross debugging).

What do you mean exactly by cross compiling?

Not the author, but presumably they mean building on a host for a target that isn't the same OS, architecture, and/or libc.

Why is this still so hard when it's pretty common?

It would be amazing if things like the "Use Rust in Python" projects could just generate binaries for every platform without you having to fuss with it.

Reply on news.ycombinator.com