@yiningkarlli@mastodon.gamedev.place
2026-04-03 07:30 UTC
Replies (3)
-
@yiningkarlli@mastodon.gamedev.place 2026-04-03 07:41
Like you can get pretty far with a graphing calculator and bad math skills, but at some point you will hit a brick wall. You can already see this in pure "I never look at the code" type vibecoding projects: beyond some scale, they tend to just kind of implode and the vibecoder doesn't know how to prompt their way out of it. (6/5)
-
@mosmann@norden.social 2026-04-03 07:41
@yiningkarlli I would disagree. I think all these complicated stuff where AI can help a lot shouldn't be there. It should be easy to use library X or framework Y. That this is not the case is a big problem. With AI we can ignore it much further.
-
@Groleo@mathstodon.xyz 2026-04-03 08:02
@yiningkarlli but the graphing calculator output was reliable all the time, you didn't had to check it for correctness. my guess is that's why it was allowed only after the methods were assimilated/internalized.