Things not normally taught in computer science curriculums that should be included 🧵
This will be a part 2, since I did one of these a little while ago. I recently thought of more things so wanted to do a follow on. If you wanna check out the first one, here it is:
https://twitter.com/varcharr/status/1430891610716340224
1. How to break down a problem.
These curriculums tend to go from “practice your while loops” to “implement this data structure” to “code this big thing”.
You will never succeed at the latter if you don’t learn how to break down the problems into smaller programmable pieces.
These curriculums tend to go from “practice your while loops” to “implement this data structure” to “code this big thing”.
You will never succeed at the latter if you don’t learn how to break down the problems into smaller programmable pieces.
2. How to set up your development environment.
These vary depending on languages and what you’re trying to build. Coding skills are difficult to transfer if you don’t have the foundational environment to work in, so getting started with full projects can be super confusing.
These vary depending on languages and what you’re trying to build. Coding skills are difficult to transfer if you don’t have the foundational environment to work in, so getting started with full projects can be super confusing.
3. Web development
A lot of people go into web dev, but experience with only C++, assembly, and knowledge of operating systems isn’t super transferable. Not to leave those behind, web dev should be taught in addition. Not assumed to be understood after such classes.
A lot of people go into web dev, but experience with only C++, assembly, and knowledge of operating systems isn’t super transferable. Not to leave those behind, web dev should be taught in addition. Not assumed to be understood after such classes.
4. Pair programming
The real world doesn’t work in “everyone program alone” mode. You need to know how to work on projects with others and how to read their code.
The real world doesn’t work in “everyone program alone” mode. You need to know how to work on projects with others and how to read their code.
5. Version control
Good grief. I went through all of undergrad with no version control. Please don’t do that. It’s only future problems for you, both in school and in the workplace.
Good grief. I went through all of undergrad with no version control. Please don’t do that. It’s only future problems for you, both in school and in the workplace.
6. Tangible networking
With things like ESXi existing, there’s no reason for students not to be building clients and servers and understanding configuration setups. Writing sockets connections by hand is fine, but the former should occur as well.
With things like ESXi existing, there’s no reason for students not to be building clients and servers and understanding configuration setups. Writing sockets connections by hand is fine, but the former should occur as well.
7. Engineering applications
As much as I may have hated it, a hands-on class like robotics would have complimented the rest of my classes really well. How to connect programming with physical things is a fundamental skill.
As much as I may have hated it, a hands-on class like robotics would have complimented the rest of my classes really well. How to connect programming with physical things is a fundamental skill.
Alright, that’s it for part 2. If this is interesting to read and discuss, maybe a part 3 will come in the future!
As before, please add any you think of!
As before, please add any you think of!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
