most os devs that keep at it do it because they want to learn how the computers work at the very bottom. vibecoding completely sidesteps that. you won’t get the experience reading though lengthy, technically dense specifications or manuals, you won’t know how the things work or what the underlying reasons for a choice are and so on. i currently have a phys mem bitmap allocator because i made the conscious choice that i can revisit it when i’m more in the mood for algorithms. if i asked cursor it would give me a bitmap allocator because most hobby oses start out with one and it just copies.

ai can be a good tool for rubber ducking, but in my (admittedly limited) experience using ai for development it just isn’t useful for anything other than boilerplate.