3 ms·
When I took computer science in 1999-2003, the best professors had rather significant industry experience. The worst professors were completely clueless because
by gwbas1c 8y ago
When I took computer science in 1999-2003, the best professors had rather significant industry experience. The worst professors were completely clueless because they never worked with a large computer program in their life.
I would have been thrilled if my freshman and sophomore computer science classes were taught by guest "professors" who had legitimate careers, and occasionally took the time to teach a class. I'm sure their feedback to my department would have been extremely valuable, because, at the time, every class was some professor's half-baked experiment on teaching computer science.
Now, almost 20 years later, I'd really enjoy the opportunity to take a school's almost complete syllabus, and teach it to students.
How does this apply to Artificial Intelligence? I'm sure there are lots of unwritten lessons from industry that haven't make their way back into academia.
- wellpast 8y ago> The worst professors were completely clueless because they never worked with a large computer program in their life. Completely clueless? I think you mean: clueless about working as a practitioner on a large, messy code base. No?
- deanCommie 8y agoI don't get this narrative (and memes) that University code is clear and perfect and real life code is ugly dirty and hacky. My experience shows the opposite. Academics write code that only they need to understand. And the type of deep thinking required for academia lends itself nicely to fewer context switching, ie massively long classes and functions and procedural execution of steps. On the other hand, in real life you have to worry about others modifying your code, sometimes at the same time as you, meaning abstractions, decomposition, decoupling, etc.
- wellpast 8y agoYou misunderstood me. I wasn’t implying academics write clean code, just exactly what you’re saying usually it’s small & dirty code. However Dijkstra, of course, always wrote impeccable code.
- wvenable 8y agoMy professor for senior level graphics was a prominent employee of the major visual effects company in town and he taught a fantastic course. He was pushed out because the school wanted professors who would do research and he just wanted to work and teach classes in the evening.
- tialaramex 8y ago> The worst professors were completely clueless because they never worked with a large computer program in their life. Seems like what you needed was a trade school. Maybe having a degree from a more prestigious university helped you get an initial job, but in terms of the things you were actually looking for, that's trade school stuff and barely overlaps with Computer Science.
- sgt101 8y agoThis is a problem on so many levels. The evolution of, management of and use of large computer programs over a long period is pretty well unstudied. And yet 100's of millions of people have to use these things every day. The programming methods used by practioners (and now taught in the Ivy league) have been developed by folk science, and are not rigorous in any way I can think of. The Academy has failed in these two ways, at least. For large systems it's a market failure. The study of systems in the field over decades is not a way to get tenure - so it has largely not happened. The development practices created by and advocated by academia failed in the field; so we got "Agile" and we can't get rid of it with science (or at least, we haven't so far) We can dismiss this all as artisanal, but in that case we need to separate Computer Science from Software Engineering properly. This means that Comp Sci goes to the Maths faculty and SE goes to Engineering. Crucially the expected level of funding for Comp Sci goes to Maths levels; buy a whiteboard and get on with it. This is no solution to be honest, but better than the current situation where the community owns to be tacking the problems of industry but actually addresses little in the core.
- sidr 8y agoI actually agree with your separation of Software Engineering and Computer Science comment, but completely disagree with the funding level statement. The notion that branches of Mathematics don't use computer resources is absolutely laughable. If anything, I don't see why the best practices for managing people who are developing the same CRUD apps over and over again needs any significant investment of any kind besides a few laptops. Computer Science can not and should not give a shit about development practices like Agile or its alternatives. CS people do own a lot of problems facing industry like machine learning and AI, and they address plenty of problems "in the core"...just nothing to do with process. Also, this split absolutely does happen at some universities, and the funding is decided by agencies based on their priorities. One such university is the University of Waterloo, and the CS department is not wanting for funding...certainly not at the buy a whiteboard and get on with it levels you're suggesting.