Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Beauty Is in the Eye of the Beholder

Beauty Is in the Eye of the Beholder



Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.


Alex Papadimoulis is partner at Inedo and helps drive the direction of Inedo's agile release automation suite, BuildMaster. In his spare time, he's the editor of The Daily WTF, a leading how-not to guide for developing software.

About the conference

QCon is a practitioner-driven conference designed for team leads, architects and project management. The program includes two tutorial days led by over 80 industry experts and authors and three conference days with 18 tracks and over 80 speakers covering a wide variety of relevant and exciting topics in software development today. There is no other event in the US with similar opportunities for learning, networking, and tracking innovation occurring in the enterprise software development community.

Recorded at:

Feb 06, 2012

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Sad but true

    by Gabriel Miró,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I believe there might be more to writing ugly code than what he mentioned, but for an introduction of main problems in trying to fix it in an enterprise environment it is a good presentation.

  • Pairing not that exclusive to programming

    by Danijel Arsenovski,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Regarding presenter’s comments on pair work (programming), after I explained a friend of mine, lawyer by profession, basics of pair programming, he told me that this is exactly what he is doing with his partner. They pair to analyze and define strategy for each new non-trivial case. So I’d say pairing is not at all exclusive to programming, it looks as resource waste from “software production as assembly line” point of view, where software development is overly trivialized as looked upon as simple and almost mechanical activity.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p