I think this celebration degrades the value of intelligibility of code, either by another human of an agent like a checker, in terms of beautifilness it looses to attractive solutions like Algol-like familiy of languages, the value is in succinteness, and I perceive due VLSI developments this is relevant only to microsystems, like embedded market, but as the number of devices that govern our lifes depend on those products we must make sure we make the right choices to program a device so if anything happens and then you have a crash that kills a passanger, you are able to tell what war with exact detail the issue and who was responsible of that piece of code, if not this is not engineering and just bad art
I think the IOCCC is a clear case of C programmers' envy of APL programmers, who get to write obfuscated code all the time in what is widely regarded as a write-only language. In APL, you can write a prime number generator in 17 characters -- some of them pretty peculiar -- or generate Pick Six lottery numbers in 10 characters.
I like to write clear, easy-to-maintain code most of the time. When I need a write-only thrill, my language of choice is sed.
Yeah, we always thought their argument before management wised up was whenever anyone complained about the code being unreadable that they would counter that it meant the complainers were not geniuses like their programmers that could understand it.
After my team cleaned up the code, one of the vice presidents had to call us to ask how to logout. In the previous seven years of development, it had never stayed up long enough for him to need to do that.
Gee, Max, I thought the reference to beer and bacon would have you as the very first to sign up! I'm completely disqualified in any case, as I gave up trying to master C syntax back in the mid-'80s. I can read it, but no way can I write any C code!
A company I worked for had finally brought in-house the software that some consultants had written. We used to joke that all the developers there were regular contributors to the C Obfuscation Awards. Most of the code was unreadable. The first thing you were taught was "Names mean nothing", just because the subroutine was named "Print", does not mean it would ever get around to doing any. My favorite piece of code I had to unravel was named "DoSomething" with parameters A, B, C, D, E, F, G, H and no comments in the alphabet soup that followed. Subroutines would do 10 different things, but would be called because they were only interested in 2 of them, and hoped the other 8 did not have any adverse effects. A colleague and I traced one subroutine down 25 levels of calling such garbage and never hit bottom. By then we had absolutely no idea what the intent of the function was at all.
Sorry for the rant, but some people see this as being "clever" when they are coding.
Hi Yog, what's one of the Outer Gods doing here on EETimes. The last I heard, you were described as: "congeries of iridescent globes, yet stupendous in its malign suggestiveness" -- and this was from someone who liked you.
I was going to say one can only hope that time has tempered your disposition ... howrever, reading your comment, I fear this is not so.
Personally, I think that anything that makes people think is a good idea -- and this type of thing certainly makes you think. Actually, when you do come to think about it, doing something badly when you know how to do it well is pretty difficult, like a brilliant singer trying to sound like someone who can't sing ... it's not as easy as it sounds (no pun intended).
Similarly, it's easy to write bad code if you don't have a clue (like me), but writing truly bad code when you are a good programmer takes some effort -- we're not talking about ordinary bad code here -- we're talking about code that would cause another good programmer to cringe at its awfulness.
Drones are, in essence, flying autonomous vehicles. Pros and cons surrounding drones today might well foreshadow the debate over the development of self-driving cars. In the context of a strongly regulated aviation industry, "self-flying" drones pose a fresh challenge. How safe is it to fly drones in different environments? Should drones be required for visual line of sight – as are piloted airplanes? Join EE Times' Junko Yoshida as she moderates a panel of drone experts.