You must be good at Math
-
This post did not contain any content.
My ex boss describes himself as such. King of the dickheads.
-
tbf all good programmers are good at math. Not classic arithmetic necessarily, but at the very least applied calculus. It's a crime how many people used a mathematical discipline every day, but don't think they're "good at math" because of how lazer focused the world is on algebra, geometry and trig as being all that "math" is.
A senior firmware engineer said to the group that we just have to integrate the acceleration of an IMU to get velocity. I said “plus a constant.” I was fired for it.
-
This post did not contain any content.
I have been coding since I was 10 years old. I have a CS degree and have been in professional IT for like 30 years. Started as a developer but I’m primarily hardware and architecture now. I have never ever said I was a computer scientist. That just sounds weird.
-
This post did not contain any content.
wow you have a degree I'm soooooo impressed
-
This post did not contain any content.
good they escaped early
-
good physics/graphics engine require calculus
How?
Again, legit question.
-
This post did not contain any content.wrote last edited by [email protected]
Had a graduate Dev who did not have a fucking clue about anything computer related. How tf he passed his degree I have no idea.
Basic programming principles? No clue. Data structures? Nope.
We were once having a discussion about the limitations of transistors and dude's like "what's a transistor?" ~_~#
-
This post did not contain any content.
If you want to know how computers work, do electrical engineering. If you want to know how electricity works, do physics. If you want to know how physics works, do mathematics. If you want to know how mathematics works, too bad, best you can do is think about the fact it works in philosophy.
-
If you want to know how computers work, do electrical engineering. If you want to know how electricity works, do physics. If you want to know how physics works, do mathematics. If you want to know how mathematics works, too bad, best you can do is think about the fact it works in philosophy.
-
I literally have no idea what this picture means, and at this point I'm too afraid to ask.
The typical holder of a four-year degree from a decent university, whether it's in "computer science", "datalogy", "data science", or "informatics", learns about 3-5 programming languages at an introductory level and knows about programs, algorithms, data structures, and software engineering. Degrees usually require a bit of discrete maths too: sets, graphs, groups, and basic number theory. They do not necessarily know about computability theory: models & limits of computation; information theory: thresholds, tolerances, entropy, compression, machine learning; foundations for graphics, parsing, cryptography, or other essentials for the modern desktop.
For a taste of the difference, consider English WP's take on computability vs my recent rewrite of the esoteric-languages page, computable. Or compare WP's page on Conway's law to the nLab page which I wrote on Conway's law; it's kind of jaw-dropping that WP has the wrong quote for the law itself and gets the consequences wrong.
-
Had a graduate Dev who did not have a fucking clue about anything computer related. How tf he passed his degree I have no idea.
Basic programming principles? No clue. Data structures? Nope.
We were once having a discussion about the limitations of transistors and dude's like "what's a transistor?" ~_~#
Tbh, as a dev knowledge of transistors is about as essential as knowledge about screws for a car driver.
It's common knowledge and in general maybe a little shameful to not know, but it's really not in any way relevant for the task at hand.
-
How?
Again, legit question.
If you write them yourself. Then you actually need a bit of math.
But claiming that you need math skills as a programmer because some kinds of programs need you to know maths is like claiming every programmer needs to know a lot about logistics because some people write software for warehouses.
-
Had a graduate Dev who did not have a fucking clue about anything computer related. How tf he passed his degree I have no idea.
Basic programming principles? No clue. Data structures? Nope.
We were once having a discussion about the limitations of transistors and dude's like "what's a transistor?" ~_~#
Could be a case of bad memory. Solved the exams and forgot everything in the next hour.
-
Tbh, as a dev knowledge of transistors is about as essential as knowledge about screws for a car driver.
It's common knowledge and in general maybe a little shameful to not know, but it's really not in any way relevant for the task at hand.
Maybe for dev knowledge, but computer science? The science of computers?
-
This post did not contain any content.
I mean, I am applying various kinds of science but I'm not actually doing any science so I'm not thinking about myself as a scientist. What I do is solving problems - I'm an engineer.
-
Maybe for dev knowledge, but computer science? The science of computers?
Well, computer science is not the science of computers, is it? It's about using computers (in the sense of programming them), not about making computers. Making computers is electrical engineering.
We all know how great we IT people are at naming things
-
Well, computer science is not the science of computers, is it? It's about using computers (in the sense of programming them), not about making computers. Making computers is electrical engineering.
We all know how great we IT people are at naming things
Informatics is a much better name imo
-
Maybe for dev knowledge, but computer science? The science of computers?
If you want someone to know about the physical properties of transistors, find an electrical engineer.
-
The typical holder of a four-year degree from a decent university, whether it's in "computer science", "datalogy", "data science", or "informatics", learns about 3-5 programming languages at an introductory level and knows about programs, algorithms, data structures, and software engineering. Degrees usually require a bit of discrete maths too: sets, graphs, groups, and basic number theory. They do not necessarily know about computability theory: models & limits of computation; information theory: thresholds, tolerances, entropy, compression, machine learning; foundations for graphics, parsing, cryptography, or other essentials for the modern desktop.
For a taste of the difference, consider English WP's take on computability vs my recent rewrite of the esoteric-languages page, computable. Or compare WP's page on Conway's law to the nLab page which I wrote on Conway's law; it's kind of jaw-dropping that WP has the wrong quote for the law itself and gets the consequences wrong.
I meant the guy in the picture, but thanks anyway
-
If you want to know how computers work, do electrical engineering. If you want to know how electricity works, do physics. If you want to know how physics works, do mathematics. If you want to know how mathematics works, too bad, best you can do is think about the fact it works in philosophy.
If you want to know how philosophy works, do sociology...
It's kind of like a horseshoe with philosophy and math at the ends.
