> "hands-on coding skills are atrophying to some degree" It really depends on how you define "coding", right? Throughout my career coding meant many different

> "hands-on coding skills are atrophying to some degree" It really depends on how you define "coding", right? Throughout my career coding meant many different things. In the beginning, coding was really Assembly. Then it became C. Then C++/OOP. Then Java/C# and managed memory languages. Then Python etc. These languages aren't the same thing with different syntax. The details that matter in the act of "coding" changed dramatically. It really went from "bit thinking" in the assembly era to stitching open source libraries in the Python era. Many would excel in one paradigm but not the other. Coding with AI requires a different set of skills. I see the proper command of AIs through prompts and human-made specs as hand coding as much as building line-by-line micro algorithms in Assembly. I think the noise in this discussion comes from putting vibe coding and AI-assisted coding in the same bucket. I'd argue that pure vibe coding is perhaps the one thing that doesn't resemble traditional coding as much. But the AI coding approach where people gradually build applications through the accumulation of components and layers built with heavy AI assistance is hand coding. I can see that relying on AI assistance for too long could atrophy the skill of manual line-by-line mental model transcription, but I never really cared too much for this skill. Once I have the right data structures and algorithms in my head, actually entering the if, else, class, struct, for, etc statements are a giant annoyance.