Javascript on your browser is not enabled.

Aneesh Bendre

Aneesh Bendre

Lead Software QA Engineer, Ouster


10+ years experience in quality assurance. Lead offshore QA team collaboration.
Hands-on Blackbox and Whitebox testing/ debugging along with DevOps and Automation Framework implementation.

Re-defining DevOps rules for remote hardware development
Developing cutting edge smart devices involves a mix of hardware and software technology. Implementing DevOps for the device’s software often proves to be non trivial because it is tied closely to the hardware that it runs on. Also, knowing when to implement the DevOps process is critical as you want to avoid re-doing the infrastructure when the underlying hardware or software architecture changes.

Moreover, DevOps teams need to consider the availability and accessibility of the infrastructure since engineering teams are working remotely now, more than ever. Should you use the existing infrastructure (on-premise) or build out a new one? Will you have “the hardware” available for validation at all times or should you consider using a hardware emulator instead? Should you leverage cloud services or opt for a hybrid solution? The cloud is an attractive approach to get going and fairly easy to scale. But, it can become an expensive recurring cost over time and is typically a one way street. Any new DevOps planning needs to have a remote-first mindset in the current environment, even post the pandemic.

In this presentation, we will discuss DevOps deployment in the context of early-stage embedded product development. How to keep the DevOps implementation agile, scalable and in sync with the development cycle of the overall project.