I don't see why I can't do compilers if I have to. I didn't take the "compilers" course in my remote study, because I wasn't interested. But when you reach a certain level of computing knowledge, you can learn anything quickly.
But anyway, I agree that "mental gymnastics", "stretching your mind" and "exchanging ideas" are very important things. And so I found ways to do these things. Yes, it's not the default case when you drop out, but as I said - if you have a clear vision how to proceed, including these important aspects, you should.
"I don't see why I can't do compilers if I have to. I didn't take the "compilers" course in my remote study, because I wasn't interested. But when you reach a certain level of computing knowledge, you can learn anything quickly"
Well, consider this. Here's an exercise, without googling for a solution (other than language documentation), do you think you could write your own grep? Write a reasonably performing distributed algorithm for routing over an ad-hoc network? Think you could write an automated theorem prover or model checker? How about just a frequency hopping protocol for congested wireless networks?
Some of these are not things that you can learn quickly with a "certain level of computing knowledge". Sometimes research projects like this take years and decades by huge teams and brilliant people, who often have to spend considerable amount of times formalizing and making consistent the underlying theoretical models, which can only then be effectively implemented.
I very much agree that defining those theories and algorithms is not for everyone. But they are already discovered, so if I need them, I'll (yes) google them and analyze if they are suitable. Of course, I'll need to know what I'm looking for, which is the "level of computing knowledge"
And if I have to do research projects - I agree I won't be able to start as a senior researcher. Perhaps a minor assistant, it is not impossible, if I ever need to. It's not like "I've missed my chance in life to ever do compilers".
Point taken. However, my point wasn't to play gotcha. Of course everyone googles for solutions, that's how things work. It's how they should work. The point was this: what if you need to innovate something new, that necessarily needs to draw from deep results in pure theory. Those without a formal background in CS, by and large, are not equipped to make these discoveries and breakthroughs. Among dropouts I think there is a certain cognitive bias of WIKIATI (What I Know Is All There Is) - they presume their success in their achievement, and in getting professional respect and a salary allows them to say "told you so!" to the weak-willed people who stay in school, without realizing they don't know what they don't know.
But anyway, I agree that "mental gymnastics", "stretching your mind" and "exchanging ideas" are very important things. And so I found ways to do these things. Yes, it's not the default case when you drop out, but as I said - if you have a clear vision how to proceed, including these important aspects, you should.