|
|
|
|
|
by cantremember
4573 days ago
|
|
I hear what you're saying, but I feel the issue is that I'm not really learning the engineering basics or methodologies in my CS program. Basically, the program is geared to churn out mediocre Java developers, and it does a pretty good job of that. It's incredibly frustrating to work on abstract coding projects only to have them reviewed by the TA and then thrown away. I'd much prefer to be working on real world stuff with impact, where I could learn by doing. And when I consider the amount of time in classes, it just seems incredibly inefficient compared to what I could be doing on my own or with the help of a bootcamp. |
|
I didn't do it just "because". I seriously wouldn't recommend dropping out despite me doing it myself.
College helps you with reasoning that you wouldn't otherwise have. I'm using a lot of my formal CS skills now more than I ever have ( I mainly work in the deeper end of things as far as engineering goes vs more traditional web dev/ruby on rails or what have you) . It's a good skillset to have regardless of what you do though.
College teaches you how to learn and if you're lucky the fundamentals. It's not there to churn out engineers despite lots of colleges saying that they do. You learn a lot on the job.
You can be self taught and do relatively well in CS, but be open to criticism and improvement.
At the time I did it I thought I was hot stuff being a freelancer. You learn very quickly that there's a lot of people smarter than you and that there's always something to learn.
I'm going to just warn you to tread lightly and always be open to learning from whoever you can.