Can someone with understanding of the process chime in here?
Here is the text snippet from the original korean article. Indeed the information was misrepresented:
"Customer-specific SoC verification work, which Usually takes Over a month, was completed in just two days. A second-year employee completed a USB model development that previously takes a month in a single day".
> SOC and piece of test equipment might have it's own control language
OK, so apart from code generation the LLMs are providing language integration and data integration.
But how would you control quality, or make sure the LLms does not create some unwordly control code? I am trying to understand if they are using type checking or any other methodology that keeps the LLM generated code in check.
I am not from the hardware field, but I do understand that we are trying to build deterministic mashines. It is quite mindboggling that we are using statistical models for building the test suite, instead of, say, permutating through all critical input states and testing the output parameters for it.
I am asking because this isnt certainly the only mode of operation for LLMs in testing and quality control, and I would love to get a better understanding how to build such a system.
All of the problems they listed seem quite solvable. And it seems like it's saving a lot of time.
But saying AI is doing good doesn't generate the same number of clicks!
But it is not a divine shotgun sniper rifle hybrid.
Seems a lot went quite right, traditional 30 day task done in 2 days