JAOO 2007: Bob Martin - Life in the Universe, Beautiful Code and Programming Discipline

Sign in to queue

The Discussion

  • User profile image
    Chadk
    Ah at last. Jaoo videos.

    Robert Martin did a fantastic key note, looking forward to see this video, after i have seen the one with kresten Smiley
  • User profile image
    raymond
  • User profile image
    Chadk
    Isnt his name Robert Martin?

    Good interview tho Smiley
  • User profile image
    Charles
    Chadk wrote:
    Isnt his name Robert Martin?

    Good interview tho


    That's his full name, yes. People call him Bob, which is a common knickname for Robert.
    C
  • User profile image
    jsampsonPC
    Nice video. Might I suggest one of those fancy wind-cancellation mics for outdoor interviews though? Smiley
  • User profile image
    JChung2006
    I'm sorry, but "write code that doesn't suck" is worthless advice.  Better advice would be "how to convince the folks who pay for code that beautiful code is worth paying for."
  • User profile image
    DannyJ
    Great interview - Totally agree with the need to write nice and clean code, less time debugging, less time figuring out what the heck some else's class/module is supposed to do, etc... Although I agree that in reality it doesn't always happen as bosses don't appreciate the shear amount of effort that goes into a software project - they just want it done as quickly as possible just so they can make money / look good in front of their boss etc...

    One thing I like to do is look at all the software projects I've done in the past and group together all of the common functionality and then create nice clean class wrappers that handle the functionality that all of the previous solutions used.
  • User profile image
    Bernal
    Responding to some of the comments here...

    Writing clean code doesn't have to mean that you spend a lot of time writing and re-writing code to make it clean. The idea that deadlines and budgets mean you have to forego clean code is wrong. If you take the time to learn "how" to write clean code and you practice doing it, when crunch time comes you'll be able to write clean code as fast as you might write sloppy code. The catch is that most programmers don't practice the "art of coding" with the goal of creating something clean and elegent and instead only code when "on-the-clock" and under pressure to finish what they're working on.

Add Your 2 Cents