5 ms·

> and then you get employers saying they dont get skilled people. That’s not the problem of academia.

by hk__2 8y ago

BrandoElFollito 8y ago
yes it is - the aim of academia is to prepare people for what they will do in the future, not some reality-disconnected curriculum.
- hk__2 8y ago
  > yes it is - the aim of academia is to prepare people for what they will do in the future, not some reality-disconnected curriculum. They already do that. The fact that some people believe going in class and doing nothing on the side will suffice is the issue here, not academia itself.
sumedh 8y ago
It should be, try telling students and their parents that the degree which you got after going in debt wont help you in getting a job.
- hk__2 8y ago
  It helps tremendously. But is it sufficient in getting you a job? No, you have to work on the side in order to practice what you learn. Employers often care more about your GitHub than your degree.
  - sumedh 8y ago
    Yes students need to work on the side as well but you cannot just wash your hands off and say "That’s not the problem of academia."
    - hk__2 8y ago
      > Yes students need to work on the side as well but you cannot just wash your hands off and say "That’s not the problem of academia." My point is that academia must priorize theory over practice: 1- knowing the theory makes learning the practice easy, and not the other way around. 2- the theory is useful for your whole career. 3- Languages and frameworks evolve quickly, quicker than university courses [1]. [1]: In the university I was in they (re)define all courses every 3 years. That mean if you want to teach practice you must find something stable enough to be relevant for at the very least 3 years. They teach Java as a first language, Python for scripting; PHP for the Web; C for system stuff; OCaml then Scala as a functional language. As far as I remember it was roughly 80% theory 20% general practice (i.e. writing vanilla PHP instead of learning a Web framework).

> and then you get employers saying they dont get skilled people. That’s not the problem of academia.

by hk__2 8y ago

> and then you get employers saying they dont get skilled people. That’s not the problem of academia.

yes it is - the aim of academia is to prepare people for what they will do in the future, not some reality-disconnected curriculum.

hk__2 8y ago
> yes it is - the aim of academia is to prepare people for what they will do in the future, not some reality-disconnected curriculum. They already do that. The fact that some people believe going in class and doing nothing on the side will suffice is the issue here, not academia itself.

sumedh 8y ago

It should be, try telling students and their parents that the degree which you got after going in debt wont help you in getting a job.

hk__2 8y ago
It helps tremendously. But is it sufficient in getting you a job? No, you have to work on the side in order to practice what you learn. Employers often care more about your GitHub than your degree.
- sumedh 8y ago
  Yes students need to work on the side as well but you cannot just wash your hands off and say "That’s not the problem of academia."
  - hk__2 8y ago
    > Yes students need to work on the side as well but you cannot just wash your hands off and say "That’s not the problem of academia." My point is that academia must priorize theory over practice: 1- knowing the theory makes learning the practice easy, and not the other way around. 2- the theory is useful for your whole career. 3- Languages and frameworks evolve quickly, quicker than university courses [1]. [1]: In the university I was in they (re)define all courses every 3 years. That mean if you want to teach practice you must find something stable enough to be relevant for at the very least 3 years. They teach Java as a first language, Python for scripting; PHP for the Web; C for system stuff; OCaml then Scala as a functional language. As far as I remember it was roughly 80% theory 20% general practice (i.e. writing vanilla PHP instead of learning a Web framework).