Haskell 💜 Vibes / Jappie

I see a lot of polarization about this in programming forums (including this one), so I find it necessary to add some nuance.

There’s a whole spectrum of activities between “hands-off vibecoding” and toiling on every keypress.

As @ApothecaLabs shared, you can use LLMs to refactor sections of your code. Or you could use it as a high-level design partner when you’re out of ideas for a gnarly integration. You can generate a design document, study and modify that, generate code from it, review it and repeat until satisfied. There’s converging evidence that LLMs can be a useful accessibility tool, or a “prism” for viewing ideas from different angles before committing to a single one. To say that all of this is a net negative for the craft is disingenous.

I’m experimenting a lot in the past few months with all of these approaches. It’s very hard to predict what you can or cannot do with LLMs because their output is completely contextual : it literally depends on 1. coding harness, 2. system prompt, 3. your codebase, 4. your request’s wording.

Personally, I share @Jappie 's confusion and excitement; what are the work, and the profession writ large turning into?