On Demand Webinar : How to make your solution ready for production deployment?

Updated: Jan 11, 2021

View presentation

You’ve completed your assignment and developed a solution using the recommended approach.

How do you know if your solution is ready for production grade deployment?

A production deployment is typically one which is tested, documented, internet facing, is secure, easy to use, compatible with devices and browsers, can handle errors smoothly, is cyber resilient and easy to maintain.

In this session, our experts will share our best practices to roll out a production grade solution/code which complies with the above requirements

  1. Best practices to improve code readability, re-usability, extendibility, ease of understanding, and maintainability

  2. Coding conventions


  4. Logs

  5. Asserts

  6. Indentation

  7. Classes/functions

  8. PMD for code quality check

  9. IDE’s to improve the readability

  10. Tools you can use

Find us on LinkedIn, Twitter and Facebook using #themithiway and #areyouready

Questions asked during the webinar

Is there any tool available to check if I am following conventions?

A convention is very much needed for code readability as this helps everyone in the team understand and improve easily. There are some tools such as PMD and Code Checker. For Language specific queries there are books available which provide what convention to use to name a function, class, interface or any variable.

What are the conventions to follow to write code?

Here by conventions we mean, the standard way to write code so that it can be easily adopted by others in the organisation. Conventions could include the class name, the way the class should be defined, the way the function is written, it could be in Camel case or Snake case convention and the variable or object name should clearly define their functions.

Does a long method mean bad code?

One function should have only one responsibility. If a function is for example, a business logic code where multiple things are wrapped under a single functionality, then it is better to break the code, make the function as a wrapper function and call each and every functionality from there. So writing a long code need not necessarily be bad, but how one writes a code should be taken care off.

Can you please explain when I should use design patterns book?

Design pattern is a book where there is an in depth and detailed coverage of how one could design and construct an object and what the relationship between objects should be. How the object should be constructed, carry the responsibility and use patterns so that it can be more easily extended and become more robust. It can be used by both beginners as well as industry veterans to make their programmes more abstract.