3 ms·
> CS programs typically and primarily teach things other than 'coding'. Yeah, but practically what I'm doing most of the time is architecturing, coding, or deb
by HappyTypist 11y ago
> CS programs typically and primarily teach things other than 'coding'.
Yeah, but practically what I'm doing most of the time is architecturing, coding, or debugging, and know/'don't mind learning' a decent amount of 'everything else' to be productive.
I had no trouble learning A* or Minimax or Quicksort when I needed it, I learned enough about neuron networks to build something 'good enough' in two days, I knew enough about networking to mitigate a layer 7 DDoS, etc.
I think I have enough surface breadth to know, most of the time, which tool or algorithm I'll need -- and can then learn that. I don't know too much about genetic algorithms for example, but I think I'll know when it's suitable for the job.
I do not doubt that CS will be valuable to me. I just question "how valuable", because 4 years is a long time.
> It doesn't. You can always drop out.
Good point. I thought that I'd be making a huge commitment, but I won't be in reality. Starting a degree will allow me to better evaluate its value to me too.
Thank you!
- pvg 11y agoI had no trouble learning Astar or Minimax or Quicksort when I needed it, I learned enough about neuron networks to build something 'good enough' in two days, I knew enough about networking to mitigate a layer 7 DDoS, etc. Of course. But pop into a bookstore or library and leaf through SICP or TAoCP or the white book or Patterson and Hennessy, etc. There's a reason these and many other topics are subjects of years-long study. It might turn out to not be your thing but you seem somewhat dismissive of it all and it might be to your detriment, whether or not you give a whit about pursuing this academically (I'm not a CS grad myself, incidentally).