Re:I won't be vibe coding anymore: a noob's perspective
by kmac_ on Wednesday April 23, 2025 @01:34PM
(#43774575)
I'm using AI for grepping, analyzing flow, finding cross-project dependencies, etc. It provides a significant speedup. But the generated code is mediocre at best. Changes look like patches on fabric, not woven threads. AI generates too much redundant code.
[ Parent
| on HN ]
Re:I won't be vibe coding anymore: a noob's perspective
by normie3000 on Wednesday April 23, 2025 @01:40PM
(#43774651)
How do you use AI to grep?
Re:I won't be vibe coding anymore: a noob's perspective
by kmac_ on Wednesday April 23, 2025 @02:19PM
(#43775071)
Grepping is an oversimplification: I ask for specific use cases, for listing all code paths that perform some action, etc. It works really well.
Re:I won't be vibe coding anymore: a noob's perspective
by aeonik on Wednesday April 23, 2025 @02:23PM
(#43775109)
How though? Do you setup RAG for this? Large context window? What do you use?
Re:I won't be vibe coding anymore: a noob's perspective
by kmac_ on Wednesday April 23, 2025 @02:59PM
(#43775511)
I started with Repomix as an MCP server plus system prompt to reduce the scope to single packages. However, it still consumed too many tokens (and polluted the context with useless information). I used Gemini, context size wasn't an issue, but it was too expensive. Now I just use Cursor, it has built-in indexing with embeddings (I assume).
Re:I won't be vibe coding anymore: a noob's perspective
by jey on Wednesday April 23, 2025 @03:05PM
(#43775580)
Try Claude Code. Itβs perfect for this type of use case.
Re:I won't be vibe coding anymore: a noob's perspective
by DrFalkyn on Wednesday April 23, 2025 @02:01PM
(#43774865)
Maybe for translating a natural language query into a regular expression that can be ingested by grep.
Re:I won't be vibe coding anymore: a noob's perspective
by DonHopkins on Wednesday April 23, 2025 @03:21PM
(#43775739)
Oh god no. Then you have three problems: ai, regular expressions, and your original problem.
Re:I won't be vibe coding anymore: a noob's perspective
by captainkrtek on Wednesday April 23, 2025 @05:12PM
(#43776671)
One other use-case I've found effective for it is assisting with API development and defining API specs. For example, I've uploaded API definitions in YAML and previously provided instructions about the API standards I want to impose and to ensure consistency as I build new things, this saves some degree of effort between writing -> linting -> fixing -> linting again if I have it just validate and fix any minor inconsistencies.