Prasanna Raghavendra

We as an software community, need to consider every developer to be a developer as everything today is code, be it feature development, test development or infrastructure development or network development. So it is prudent to build teams who take up feature development to cloud development driving value to business and building skills horizontally. Specialisation can be built, but it should not be just that.

Cloud computing is gaining importance as businesses are providing more and more Software as a Service and thriving. This has led to cloud and application architectures to be entirely owned and managed by the developer, in a "You Build It and You Run It" principle. As a leader, promoting and encouraging developers to own what they build until the service is operated, monitored and managed in cloud is an important skill leaders should inculcate. Building different groups to run this horizontally will only add significant hardship in delivering business value.

I am surprised to not see chaos testing here - any performance metrics should be performed with an assumption that anything can go wrong in the stack. This is what chaos testing does. Also it is not about the tools really, it is about how well you use them as performance validation is engineering to the core. So any of the top tools should do, as long as you understand how you would do the tests and how well you understand the bottleneck and validate the fix.

Apart from the reviewing the best encryption provider and the encryption algorithm to use, the key to any data encryption solution is the ability to identify what is to be encrypted, in a automated fashion. Data is expected to grow, beyond means and bounds, a solution that can identify the sensitive data will help manage the cost of encryption while maintaining the value of encryption.

Software design is a little bit of art and a little bit science, hence you can never be done. If you need to show passion you should enjoy the process, and its incremental nature of the same. Software design is not about making it perfect at the first attempt as it can never be. It is always about incrementally reaching its best next state. If you continue on improving the design and implementation, you are actually showing passion. It is about understanding what is working what is not working and what has changed to make sure you are finding ways to make it better.

Anything repetitive ought to be automated! Be creative in automating! This helps upgrading skills from task orientation to automation orientation. This also helps in improved quality of repetitive task.