Requirements change and so does your code. Want to make the changes less painful ? Then this talk is for you.

The talk is about application of Uncle Bob's S.O.L.I.D principles.  The talk highlights benefits of these design principles through concrete code samples and real world applications.

We will refactor out a badly designed code handpicked from a production application using Uncle Bob's S.O.L.I.D design principles. It also includes practical application of 4 simple design rules by Kent Beck.



Outline/Structure of the Talk

0-10mins: Design Basics

  • What is Design ?
  • What is Dependency Management ?
  • Symptoms of a Badly designed code ?

10-30: S.O.L.I.D Design Principles

  • Explain all S.O.L.I.D Design principles with code examples in Java.
  • Indicators for finding bad designed code

30-35: 4 Rules for simple design

  • Kent Beck's 4 simple design rules
  • Application of rules in the code

35-45: Q&A


Learning Outcome

  • Object Oriented principles and their application in code, focusing on SOLID
  • Simple rules of great design ( Kent Becks 4 simple rules )
  • Refactoring techniques to refactor out a badly designed code
  • Getting Abstractions right
  • Help write code which is less fragile and flexible to change


Target Audience


schedule Submitted 4 years ago

Public Feedback

comment Suggest improvements to the Speaker
  • Balaji.M
    By Balaji.M  ~  3 years ago
    reply Reply

    Hi Rajeev,

    I guess still you are interested in presenting in the conference, since the topic is interesting we think this talk would have some learning for the participants. As mentioned by Ellen, please can you upload the videos.

    Best Regards


  • Ellen Grove
    By Ellen Grove  ~  4 years ago
    reply Reply

    Hi Rajeev!

    This looks like an interesting topic.  Can you give me some sense of your speaking experience (perhaps a video? links to previous presentations?).  If not, perhaps you could record a couple of minutes of video explaining why you're passionate about this topic in order to give the reviewers a sense of your presentation style?