Counterargument: I can learn things at record speed (for me) because I can learn things in the order that makes sense to me. I find it much more motivating to start with: “why is AI bad at playing video games?”, than to start with “what is the chain rule?”
I will certainly need to learn about the chain rule eventually, but I find that I get lost in the details (and unmotivated to continue) without an end goal that is interesting to me.
AI loves to make vibe charts (sometimes with lots of extra steps), but that’s part of the process. It is nontrivial to wrangle LLMs through larger projects, and people need to learn that too
So this repo popped up in my newsfeed: https://github.com/necat101/Chronos-CLGCM
This isn't the first instance when I saw something like that, and it looks like a new trend, as the glamour of being an AI researcher with a high-paying job has started to affect ordinary people. It feels like a lottery ticket that you can win with vibe-coding.
How can we approach these situations in a good manner and help those people with constructive feedback?
As long as it does not land on my desk for reviewing I don’t mind.
It’s also a good test for the LLM promise that they can do PhD level research. This means we will should be seeing something novel that works from these folks.
It's not unpossible to vibe code (I hate that term) good software, or well designed software, but if you don't come from a UX or software background, you can generally tell when you look at their product documentation.
Lots of Emojis, too many emojis. Lots of flow charts. Too many flow charts.
Counterargument: I can learn things at record speed (for me) because I can learn things in the order that makes sense to me. I find it much more motivating to start with: “why is AI bad at playing video games?”, than to start with “what is the chain rule?”
I will certainly need to learn about the chain rule eventually, but I find that I get lost in the details (and unmotivated to continue) without an end goal that is interesting to me.
AI loves to make vibe charts (sometimes with lots of extra steps), but that’s part of the process. It is nontrivial to wrangle LLMs through larger projects, and people need to learn that too
So this repo popped up in my newsfeed: https://github.com/necat101/Chronos-CLGCM This isn't the first instance when I saw something like that, and it looks like a new trend, as the glamour of being an AI researcher with a high-paying job has started to affect ordinary people. It feels like a lottery ticket that you can win with vibe-coding.
How can we approach these situations in a good manner and help those people with constructive feedback?
As long as it does not land on my desk for reviewing I don’t mind.
It’s also a good test for the LLM promise that they can do PhD level research. This means we will should be seeing something novel that works from these folks.
It's not unpossible to vibe code (I hate that term) good software, or well designed software, but if you don't come from a UX or software background, you can generally tell when you look at their product documentation.
Lots of Emojis, too many emojis. Lots of flow charts. Too many flow charts.
[dead]