LabVIEW

to run the tests.

And there's no weird graphical language like LabVIEW.

It's just plain text that you can work with and put it into version control and everything.

Yeah, to me, that's where I would find it really valuable is less for renting a dev board on the cloud, but that I'm ready to graduate to real hill testing.

The real leap came a decade later.

In 1986, they released LabVIEW, short for Laboratory Virtual Instrumentation Engineering Workbench.

Instead of forcing users to write lines of text that described what a program should do, LabVIEW let them draw it.

Users dropped icons representing sensors, filters, math functions, and displays onto a canvas and connected them with virtual wires.

The resulting block diagram looked like the signal flow charts engineers already sketched on whiteboards.

The timing mattered.

Traditional instruments were optimized for high volume and fixed use cases.

LabVIEW inverted the economics.

Any semiconductor business, probably the test handlers are the one, which eventually we will start making it in India.

And MT Automation, the entire experience of what I have, developing the skills for the mechanical engineers, for the machine design, and also for the electrical engineering, doing the PLC programming, or the LabVIEW, and even the tool room experience, that we are going to consolidate everything and we are going to do the test handlers.

For that, it is important that I have a right technology partner who can give us a transfer of technology and the both party can mutually benefit in this program.

Yeah, absolutely, absolutely.