# Can we get more tweaks to LLM policy? > Source: > Published: 2026-08-15 12:52:43+00:00 [g41797](https://ziggit.dev/u/g41797) 1 See below several quotes from latest llm showcases It’s hard to beleive that after such discloses we will see discussions like: - how to use cheep subscription for my hobby zig project - how i can cross-check code using different llm - how to organize development of large zig project using llm - … Development with llm assistance is fight I have been coding since 1977, so I will win But I have no clue how to explain/help juniors learn programming in AI era Saying “don’t use AI” is not enough May be we need ‘additional tweaks’ ? 1 Like This resonates with me. I started in 87 but still I win. It’s harder to use ai (to produce quality) but alot faster. 1 Like Maybe make a whole `llm/ai` category where showcases can be posted and questions can be discussed, while keep the possibility to simply ignore the `llm` stuff category for those who don’t want to read about it. Since, if I remember it correctly, this possibility of filtering llm stuff out of someone’s view, was the original reason for introducing these tags. 2 Likes [g41797](https://ziggit.dev/u/g41797) 4 Yeah, I just meant maybe a complete own category so there can be discussed other llm topics you mentioned beside showcases. And anyone (like me) who is not very interested in it could mute the whole category 1 Like I totally agree… I also see this: And this People basically start abusing the “LLM disclosure policy” to looking for LLM advisories. Some even with little programming experience. And people with little experience in system programming language and coming from web stack languages are directly asking advisories about using LLM, instead of learning system programming language… I don’t think this meets Zig’s missions… 1 Like [7his](https://ziggit.dev/u/7his) 7 fair but I actually have been learning systems as Morphic grows, Zig also doesnt exactly have the huge ecosystem and decades of examples that C and C++ do, so ive been learning from whatever production approaches actually survive real tests and workloads. Sure, thats not the purist build every layer yourself first route, but the principles dont change just because an agent helped write the code. Memory still has to be correct, syscalls still have to behave, and real software still has to run, frankly i’d like to think whatever this project gets right or wrong, people can learn and the language itself can grow in terms of knowledge! There is nothing worse than a blank page, maybe nothing better, but when languages like rust exist we risk falling behind simply from lack of application, the goal for me, no matter the end state of this project is for zig as a language to grow and learn, and for assumptions and language issues to be brought out! Also, I don’t really appreciate the claims of my experience the post implies. I’m not sure what point my post is being used to argue, but I don’t have a problem with the policy as it’s currently stated. 2 Likes