> Why do you feel like C is so fundamental that every developer must know it regardless of what they work on? I never said so. I was answering specifically to

> Why do you feel like C is so fundamental that every developer must know it regardless of what they work on? I never said so. I was answering specifically to "If I want to be a product/creative developer how does learning C specifically help me?" Since you didn't mention what you do, I was talking about "product" and the definition you have, and if you want to build "product" there is a whole "product" industry, that is bigger than you think, that requires C. If you do web development you can completely skip it if you want, but C is a nice tool to have around to understand why there is a bottleneck in Redis, Sqlite, a driver or a stack. Maybe find a workaround or a fix, but waiting for someone else to fix it is also valid if you don't want to fiddle with C. It happens all the time: high level developer points finger and says "there is something wrong with the filesystem, my app crashes". They cross their arms and wait for me to go in a crazy debug session so I can explain them later why their app is slow and/or crashes.