Follow Single Responsibility Principle & You are Home!

Here is an interview with Ajitesh Shukla who has been very passionate about coding all these years and have helped many software developers to write better code by getting them understand few basic coding principles. Read on to find out about his experience and expertise around coding.

• Tell us something about yourself, in brief
• My name is Ajitesh Kumar and I have got an experience of around 14 years working in different technologies such as Java, PHP etc. I am currently working on projects related with software quality governance, BonitaSoft, enterprise architecture, ATG etc.
• Tell us about your coding experience, in brief.
• I have been coding in different languages including but not limited to Java, Spring framework, ATG, BonitaSoft, PHP, Javascript, HTML/CSS, Android etc.
• Any Eureka moments that turned you into a better software developer
• Few years back, I came across this principle named as Single Responsibility Principle which really sorted many of issues I had while doing the coding.
• Suggestions to lay down a great software design
• Understand the software requirements, group the similar requirements together, and create a module around that group. This would help you have high level functional modules. Then, take each function in the module and create an interface and an implementation (component) for that function adhering single responsibility principle.
• Thumb rules you would suggest for writing software code of great quality
• Keep SOLID principle handy and it will sort 80% of coding issues (code smells). Especially, try and follow single responsibility principle (SRP). Its extremely powerful one.
• Tell us about importance of writing unit tests for a given piece of software?
• To me, unit tests help me write a better code with lesser code smells including long method, long classes etc. This is because, in order to achieve greater test coverage, it is recommended to write small unit of code adhering to SRP. This way, I end up writing components that do just one thing and do it well. It also helps me to design better.
• How much important is quality assurance/testing of code? How you dealt with testers?
• I believe in “Test Early, Test Often”. This is why I collaborate with testers right from the stage of requirements gathering to the pahse of design & development.
• Your favorite books, videos, web pages you would want to recommend for fellow developers
• I like to log on youtube to watch videos on different technical topics. GoogleTechTalk youtube channel is my one of my favorites.
• Any advices for newbies just starting on coding
• Follow Single Responsibility Principle and you would be better of 80% of issues related with coding.
• Your blog or Website URL
• http://www.vitalflux.com