For a register machine, C can be pretty beautiful.
It's funny you talk about parsing command line options. Plan 9 solved that problem well with the arg(2) macros. [1]
In fact, Plan 9 in general is a premier example of really clean and elegant ANSI C-compatible code. [2]
[1] http://man.cat-v.org/plan_9/2/arg
[2] e.g. https://github.com/0intro/plan9/blob/master/sys/src/libndb/n...
Even in crusty pre-ANSI C, it's very elegant stuff.
(Then I look at the Bourne shell sources and weep. It's like the author of that was in denial of everything that made C a decent language and wanted desperately to be doing something else)
It's another sense of beauty, the one of talking almost directy to the machine, with few abstractions, and few wastage.
If a programmer uses a language poorly it can be the programmer but in a lot of cases it can also be the language, that has poorly thought out, conflicting, etc constructs.
There is a field called PL research (part of Computer Science) and researchers can all agree on several problems that C (and what would have been a better design).
Some of the problems are so obvious that the creators of C admitted them too. Some have been corrected in later revisions (C99 etc).
The tool can be the source of your issue if its not made correctly.
"Pure wire-mesh electric blanket -- no insulation whatsoever! Only $20 dollars. Will raise the heat with sparks of electricity, plug directly into your 110v outlets!".
Sure, works as advertised. But it's ill concived and will fry anybody trying to use it, either because he wants to or because he is forced to (by his boss or needing to deal with legacy code in the case of a programmer).
The example is contrived to showcase the point, but the gist is: "works as advertised" doesn't mean much with regards to quality or well thought-out architecture.