Andy's scripts used to run for hours. Now they run in minutes.
Teams ask us what people actually do after the training. Andy at Broadview converted the scripts his team had been hesitant to let AI touch, and checked the output against the original.
Outcome: Andy reports the runtime went from hours to minutes, with the output matching the original.
“…I'm able to check the output and it's been matching that like spot on. So that's been a big win.”
Before
Important work ran on slow R scripts.
Andy's team runs key processes on R scripts that take hours. They already used AI for other work, but not on the scripts behind their trades.
What he did
He converted them to Python, then checked.
At B43 office hours, Andy shared that he had converted the R scripts to Python. Then he checked the new output against the original. Don't just trust it. Check it.
What changed
Hours became minutes.
Andy reports the runs went from hours to minutes, and the output matches. He shared it with the team at B43 office hours.
What's next
The next slow script.
The same method works for the next slow script: convert it, check it against the original, then move on.
Read the video transcript
Andy's team runs its important processes on R scripts. The runs take hours. The team was already using conversational AI. Just not on the scripts behind their trades. Then the team trained with B43. Don't just trust it. Check it. Andy had conversational AI convert them to Python. Then he checked the output against the original. Runtime: hours to minutes, after converting from R to Python. In Andy's words: "…I'm able to check the output and it's been matching that like spot on. So that's been a big win."
