Just to clarify, I google a lot while coding, but one thing I learnt from my engineering degree is that is there is no ‘best’ solution.
Just to clarify, I google a lot while coding, but one thing I learnt from my engineering degree is that is there is no ‘best’ solution.
Yes.
I “vibe code” anything that is throwaway. If it’s throwaway code I don’t care about the quality, I just want the end result.
For everything else, I don’t vibe code.
There are definitely people who use AI as a crutch for their lack of technical skills. It’s the same folks who used to try to get coworkers to “help” and slowly built their tickets by cycling through teammates.
But like, does that happen often for you, that you need a piece of code that’s gonna be thrown away?
I always feel like if code exists, it’s not gonna be thrown away, so it’s a good idea to make it maintainable. But I do probably have somewhat of a bias…
Yes, because of the stuff I’m currently working on.
I’m trying to improve the Devex at the place I’m working, and there is a lot of need to change stuff on 10000+ repos or pipelines in order to standardize things…
Same here. It’s surprisingly easy to get quick results with a few prompts for one-time scripts without putting any effort in.