I'd caveat this. Finishing through at least ASA/ACAS documents the discipline and aptitude to pass the math based exams. If down the actuarial track, and find it's not for you, that's a good stopping point for the increased recruiter attention it can bring.

One of the CAS publications recently had a good comparison between where Data Science and Actuarial role falls in terms of a venn diagram illustrating 1) computer science, 2) mathematics, and 3) domain expertise. Data science falling heavier on computer science and mathematics. Actuarial work heavier on business/domain expertise and mathematics.

In general I've found the actuarial side frustrating in often we've got the skillsets to crank out our own dashboards and tools if given the access to do so, but our priorities in terms of yearly goals and role expectation is to spend the time on the business, finance, accounting, communication, and domain expertise ends of it. Hand the fun programming off to IT or people in the company specializing in those roles.

When I look at the future my thought is the actuarial world will need to adopt heavier programming, but the current state of the industry does not reflect the drive to push that forward. With exception of limited roles.