There are lots of successful working programmers that will never need to deal with "algorithmic complexity" because "programming" encompasses a very wide spectrum of skills. I attempted to explain a rough categorization of 2 groups:
https://news.ycombinator.com/item?id=12079697
So yes, a programmer in group 1 -- let's say a 30-year veteran of COBOL -- can conceivably never have to make a decision about designing an algorithm & data structure to be O(n) vs O(log n) because he works at a higher abstraction level using COBOL. His domain of work doesn't need to deal with low-level things like raw pointers to linked-lists in C/C++ where Big-O complexity is considered when engineering a custom b-tree from scratch.
The programmers in group 1 are not any "worse" than group 2. They just do a different type of programming.
That would be around the era of the Intel 80486 processor. All of us cared a hell of a lot about both algorithmic and data structure efficiency back then since computers were so feeble compared to today's systems; people who didn't couldn't produce programs that functioned properly.
In the ancient 1990s, A COBOL programmer writing "green screen" terminal apps to hit a database on an IBM 360 mainframe doesn't deploy to 80486 desktop pcs.
Even today, if you type "COBOL programmer" into monster.com to search for jobs, most of the results will be programming work for mainframe environments instead of targeting consumer computers like iOS/Android/Windows/macOS/etc.
The point is during a degree you are lead to some topics and guided through them.
Sure, you can get the knowledge in other ways, and sure, some of the houses built by people who haven't studied architecture are great too.
Some aren't though, and their builders could have benefitted from a bit of theory ahead of time.
It's almost more like the relationship between materials science and hoise building - it can enable you to do a better job.
For those saying you've never been helped by your CS degree, I think you either took a bad degree or you'be been stuck in un-taxing work. You've seriously never bothered thinking about, say, algorithmic complexity? Or other topics that should have been covered?