3 ms·
I had been coding for a long time before joining university and I still learned a ton. This is what I consider that helps me daily on the job Algorithms, data
by sebstefan 3y ago
I had been coding for a long time before joining university and I still learned a ton. This is what I consider that helps me daily on the job
Algorithms, data structures, functional programming, object oriented programming, dynamic programming, compilers, shell, basic front-end web development, android apps, systems programming, concurrency, distributed software, hadoop, UI/UX, testing, information theory, cryptography, security, networks, configuring switches, embedded software development, databases, linear algebra, assembly, computer architecture, graph theory, statistics, complexity theory, automata theory, discrete mathematics
I did not get classes on electromagnetism, fluid dynamics or engineering topics like you seem to have had
I've excluded things I don't use as much such as
Prolog, algorithm provers (COQ/Promella), advanced calculus, lambda calculus, lots of common-sense classes related to soft-skills like communication and project management
Also I didn't enroll in the graphics programming classes and I regret it a lot
- lordnacho 3y agoPerhaps it was worth adding the caveat that people who did a CS course actually do seem to use it directly. Practical things like Git and Linux commands are the real thing. CS is somewhat unique in that you actually do what you do at a job, with the same exact tools. You don't use a toy version of a c++ compiler or a version control system, and your computer is as powerful as the one you get at work. Everyone else at uni does things that are not the same thing at all, with the exception of medics who are sent to the hospitals. I built a 1m model of a bridge, and a radio that was fixed to one AM station. I used Cadence for a week to build a CPU with a few thousand transistors. Don't get me started on Economics and Management.