|
|
|
|
|
by gombosg
121 days ago
|
|
Love your approach and that you actually have "before vs. after" numbers to back it up! I personally also use AI in a similar way, strongly guiding it instead of vibe-coding. It reduces frustration because it surely "types" faster and better than me, including figuring out some syntax nuances. But often I jump in and do some parts by myself. Either "starting" something (creating a directory, file, method etc.) to let the LLM fill in the "boring" parts, or "finishing" something by me filling in the "important" parts (like business logic etc.). I think it's way easier to retain authorship and codebase understanding this way, and it's more fun as well (for me). But in the industry right now there is a heavy push for "vibe coding". |
|