I'm self taught, the last math class I took was 9th grade Algebra.
I wrote one of the first vector based, anti-aliased, alpha channeled UI frameworks for Windows 95 (16 bit!). I wrote a DSP processing engine for a telemedical application to monitor heart rate and blood pressure in 1997. I've written control software for elevators. I've written contract after effects plugins for post fx shops. I've written audio and midi sequencers. My video editing app, Shave, is the only other useful editor in the Mac App Store other than iMovie.
I've never cracked a math book.
Am I the exception that proves the rule? I'm not saying I could write Maya, but I think you are overvaluing your opinion a little.
I've also had the severe displeasure of working with CS grads who couldn't figure out why a 54MB file wouldn't fit on a floppy disk, or asked "where is the .EXE" when working on a windows web site.
I'd take a motivated "self-learner" over a paper-backed "scientist" any day.
but yes, I think you are the exception
I honestly think "programmer" and "computer scientist" are slowly being conflated, and the distinction is important to understanding this sort of issue. Is this Granny Smith vs. Fuji, or Fuji vs. Florida Navel?
But even before the availability of those sorts of really convenient tools a lot of people have self-taught themselves past that level. In fact, I remember my abstract algebra prof telling us an anecdote to illustrate the importance of working through things on our own instead of waiting to see what was presented to us in our courses. He talked about a grad level course that he had been teaching for the past 10 years. Clearly, he knew the material inside and out, but the interesting thing is that he had never taken it himself as a student. How did he do it? He read a couple of books about the topic! It's a time-tested method.
I'd say if people aren't learning the math it's because they underestimate its importance. Either that, or people like me (and maybe you) overestimate its importance.
There is a huge collision that's about to happen: increasing costs for post-secondary education; a middle class that will no longer be able to afford said post-secondary education for their kids; and free, quality, ubiquitous educational content like Khan academy. I'm not quite sure how things will play out. But things like Khan academy could pop the educational industry bubble, at best forcing lost cost quality formal education, and at worst, resulting in ubiquitous access to informal education to those that put in the effort.
The key to self-education is effort. It's much easier to be forced to take classes, do assignments, sit through lectures and take exams. It's much harder to have the self-discipline to do this on your own.
I like to read journal articles, and when I stumble onto something I don't know, I go learn about it. Just in the last year or so, I've taught myself stochastic calculus (I was doing HFT and wanted to learn more about the greeks) and the basic typed lambda calculus (was into haskell and wanted to learn more type theory). These days I'm doing distributed systems, so I'm brushing up on the process calculi.
I assume pkaler (and probably many others) would claim that you're the exception to the rule.
Related rant: Many university educated computer scientists think that all the math that they learned was 'invented' specifically for computer science, when in fact it existed long before computers were around. I once got into a heated argument at a Siggraph party with a guy who actually claimed to be the 'inventor' of quaternions.
I'd even wager that most audio engineers who program learned something like, you know, Audio Engineering and just kind of slipped into programming along the way. This maybe makes them a worse programmer than a CS grad, but a heck of a lot better audio algorithm designer.
Many algorithmical problems can be solved in code, but they require specific knowledge about the problem space, which CS grads lack. This is not to say that CS grads are bad at maths, it's just that audio engineers spent years learning about hearing, acoustics and audio analysis and audio algorithm design is more than just some linear algebra.
Aside from the tree-murdering, your cow-orkers (nice reference) are doing the right thing, at least initially. You should always eyeball things before going to statistical tests.
Still, my overall point stands - eyeball first, formal tests later. This has saved me from much statistical foolishness in my time.
Thirty or forty sheets of correlations might be made slightly prettier and on one sheet by just using 'plot' on a data frame in R.
What context is this in?
Not sure of the poster's original context. Just thought I'd air my statistical opinion out of sheer orneriness.
ggplot vs base & lattice in your experience? I have used lattice before but not in a few years, and I use base all the time. Don't have time to muck around with
ggplot: came for the Tufte-type aethestic, stayed for the graph grammars. I have a lot more experience with ggplot than base&lattice since I switched so early but wiser heads tell me that they are similar in capability. I just find ggplot easier to work with and look at.
Most students in the CS program hate math and CS theory courses. Subjects like Algorithm Analysis, Discrete Math, Automata Theory which often get cited as examples of stuff that self-taught programmers might not know are boring and annoying. Almost every student in the department dreads these courses but has to hold his/her nose and take them to fulfill the degree requirement and most people promptly forget these courses after passing the exam unless they have real interest in the topic and are taking fourth year electives in the subject. To be honest I don't think the self-taught programmers are missing anything.
And congratulations for digging up a use case for Calculus in CS. I can site examples of CS fields where say Cognitive Psychology has huge influence. The fact still remains that it is completely irrelevant to most of CS unless you are interesting in that one obscure area (in which case more power to you).
As a self-taught programmer who is just wrapping up pre-program requisites for the CS program at a decent school, I am drooling to get some formal instruction in algorithms and FSAs. And I'm sorry but I've even gleaned some good understanding of time complexity notation from my pre-calc/trig class.
I just don't get this, I guess. I'm dying to get some formal education on the more scientific and heavier math subjects. These are things I wouldn't ever teach myself because I am so task-oriented when I program. Why "waste time" mastering the concepts of FSAs when I've got a web application to build?
I hope you learn to appreciate the potential for greater understanding that these boring and annoying classes give you. You have made the choice to discard their value on your own faulty assumption that your limited understanding of the world is a complete understanding of the world. It makes me kind of sad that all the liberal arts majors in the world are happy as pigs in shit to be studying Proust and how to make coffee, while here you are shitting all over a high quality education in a hard science/engineering that will undoubtedly provide you a lucrative, comfortable career if you choose to pursue such a thing.
I can assure you, as a 31-year-old man who was self taught until last fall, I have definitely missed those topics.
I'm not trying to sound bitter but as I mentioned a vast majority of students barely tolerate these courses and only take it because they are being forced to and once they pass they don't think about such dry material and end up at the same level as "self taught programmers". In that sense I don't think self taught programmers are missing anything. If you are interested in this stuff than more power to you. It's just that from my experience I highly doubt that many self taught programmers would want to or enjoy learning these topics anyways.
The tracks allow a similar siloing. If you take an applications track, it's likely you won't be learning fourier transforms that you'd get in the graphics and vision track. In either of those cases, you may not get the functional programming experience that you would get in the AI or theory tracks. Those two wouldn't require you to take the database courses you'd need for info science.
There's only so much that classes can cover in the course of an undergraduate education. Teaching yourself advanced topics is likely essential in taking on a project of a different nature than what you learned in school.
You can actually make a decent living as a programmer by just gluing js/ruby together, since that constitutes the bulk of most programming jobs.
I guess the point is that formal eduction forces you to learn advanced math, whereas only the motivated self-taught programmers learn it.
Think about how many times you've worked on a unique and perfect piece of code, only to realize someone's already made it. Usually with clever optimisations you never thought of. So it might be in a different language or framework, but porting it would have been easier than understanding the issue and reworking it.
A good code monkey understands the problem, a good businessman doesn't bother and repackages other people's stuff at a price.
I myself have a compsci degree and upvoted you, but the people in charge often don't get this.
The difference between mediocrity and brilliance --in ANY field-- lies in something that has nothing whatsoever to do with a formal education. I have met so many people with impressive pedigree's that are clueless to not need further proof. I have also met a good number of people with what I would call "interrupted educations" that focused so intensely on a particular field of study that they truly became masters within that field.
In engineering or cs there's also what happens before university.
In my particular case, I built my first computer way before I saw my first college textbook on the subject. And, by "build my first computer" I mean that I wired the CPU and ALU from discrete components (Who knows how a diode matrix can be used as an instruction decoder?), created my own machine language and coded instructions bit-by-bit into memory.
After that came wire-wrapping 6502, 8080, 8085 and 68000 computers, again, before seeing my first college textbook. And so, it only stands to reason that the focus and drive once in college and out of college was very, very different from that of someone who never had any such experiences and came to college with a blank stare waiting to be taught something they knew nothing about.
I think you're overvaluing those if you think someone cannot learn those topics if it's apropos to the thing they're doing.
Signal processing is a considerably bigger chunk of schooling though.
I don't disagree with your opinion, I prefer school credentialed programmers, however I don't think your line of reasoning works.
One way to recognize these frauds is whether they list their credentials online. They may write online that you don't need qualifications to be a good programmer, which is true, but they won't actually say they don't have any credentials because that's not what they've told their previous employers and they don't want to be exposed.
When there's 2 people giving presentations, one lists their PhD from a certain university and the other only lists some IT groups they run, I know which one I'll pay more attention to.
Any good math books you can recommend, for people who are genuinely scared of complicated equations? And without losing my day job(graphics designer).
I have met very few self-taught programmers that also happen to be self-taught mathematicians. This limits the type of code you can write.
Linear algebra is required to deeply understand computer graphics.
Calculus is required anywhere you have signal processing. This means audio and video editing.
Physics is required for simulation software and video games.
Discrete and combinatorial math is required in systems software like databases.
You're just not going to hit these issues if what you do all day is glue Javascript and Ruby together.