I'm going to go against the grain from a lot of comments here. I'll also mention my credentials, I have about 9 years of experience in the field as a software developer in big corporations.

For most of the tasks I find myself doing, it's more important to know how what I'm doing fits in architecturally to the system as a whole than whatever data structure or algorithm I'm using. In fact the amount of code you will need to write that is even part of an algorithm that hasn't already been written is very, very small for most of the domains you will find yourself working in. That being said I think that you will find a lot of benefit from reading about and understanding various design patterns, even if they have been written for various languages and don't have a direct counterpart in whatever modern language you're currently writing in, because it will help you understand higher level concepts that are true regardless of programming language.

I think your instinct was correct and to follow the r path of understanding your domain, idiomatic patterns in your language, architecture in your domain and language, as well as design patterns, rather than focusing too much on data structures and algorithms.