I'd say the "get you further" remark is true in the narrow sense of a career: you'll be more likely to beat the interview if you can write a recursive solution to a problem than if you can talk fluidly about python generators.
But being a productive engineer really requires both, they aren't separable skills, yet paradoxically they're actually poorly correlated! The world is filled with productive hackers who can get the wrong solution to "work" quickly, and insightful theoreticians who just can't produce working code.
"Hacker" or "tinkerer" mindset is very helpful. When hiring, especially at the entry level(s), those who hacker/tinker outside of their job usually standout and have a better understanding of how all the "things" we work with as Engineers connect because they are out there trying/failing outside of their 9-5.
The challenge with "hackers" is learning how to unplug, so make sure to develop skills/interests that are completely unrelated to "work".
Try to code something everyday. Learn to use tools. Doesn't matter what you code or what tools you use really.
The idea is to get comfortable with not knowing all the answers and then get fast at figuring things out.
Most importantly, get enough sleep, exercise, and sun. Your mind needs to be sharp and that starts with maintaining your body. Good luck!
fish45 made it clear they're already an experienced programmer, so I don't see that it makes sense to emphasise this.
They're more likely to struggle with theory than with their programming tools.
My point was that for the programming material, they're more prepared than many of their peers. For theoretical material, they're on the starting block with everyone else.
It's good to work on your developer skills beyond what your degree gives you, but no-one should expect that their undergraduate studies will be easy simply because they're already a programmer. That's like assuming your degree in pure math will be easy because you studied algebra in high school.
If you have a choice between doing well in your degree course, and learning additional developer skills, you should go with the former.
2. Go for depth, not breadth. I know most US colleges make students do all sort of breadth stuff, which I don't get (I come from European undergrad, all our classes were CS/EE - coming to US for grad school, I was more prepared than others coming from top US undergrads). You have time to dive into other stuff after school. Do adjacent things like Biology or EE.
3. Find grad students and see what they're working on. This is where you'll see the value of the fundamentals. Then work backwards and fill the gaps. Try to get a tiny part in a research project (ideally one that can lead to publication).
4. Read timeless papers one each topic.
5. Hack, hack, hack - the gap between theory and practice is small in theory but large in practice.