@vanamerongen Repo-level guidelines help, but they don’t solve the review problem. The more code agents generate, the more important it becomes to preserve context and make changes understandable. That’s one of the problems I’m exploring with Relu: https://t.co/UzJaTD5XAp
@svpino This is exactly the question I’m exploring with Relu: what does code review look like when the goal is understanding and verifying a system, not reading every line? https://t.co/UzJaTD5XAp
@rauchg Strongly agree. AI is generating more code, but someone still needs to understand what actually ships. I’m exploring this problem from the code review side with Relu: https://t.co/UzJaTD5XAp Curious what your ideal review workflow looks like today.
@Crocodyle_TV@SpamOfficiel Hi! Pour rendre votre jeu encore plus beau : documentez vous sur l'anti-aliasing ou passez en vectoriel pour éviter les pixels disgracieux.
Choisissez une police plus adaptée. Certains visuels / animations sont joli ils sont gâchées 😅
@Crocodyle_TV sur ton jeu il faudrait que ton dev mettes de l'anti-aliasing et ou que tu travailles avec ta graphiste pour faire du vectoriel (svg) sur les assets, ça sera plus portable entre mobile, pc et en fonction des tailles d'écran. - dev back-end.
@buildsaascom @shadcn and what about, just saying, using a library, that have versioning, that you can use to, I don't know import component from it ? I am not sure if copy/paste is the way to go, it's as unusual as sending diff patch to an email to fix bug.