3 ms·
Few people have to do all the specific algorithms stuff we learned, because now that's all in libraries, but it's still useful to know how those things work, ju
by pg 19y ago
Few people have to do all the specific algorithms stuff we learned, because now that's all in libraries, but it's still useful to know how those things work, just as it's useful to a pilot to know how all the systems in his plane work.
I think the most useful thing I ever learned in a CS class was from Michael Rabin: that the best way to solve a problem is often to redefine it as something that's easier to solve. This turns out to be applicable to practically every kind of work.
- yagibear 19y agoUniversities seem to be struggling to cope with the depth of knowledge that has accumulated. It is empowering to "know how those things work" from first principles, but as time progresses, the volume of such knowledge grows towards and beyond the capacity of the courses that convey it. Universities must then (as they are now) make a delicate balance between covering fundamentals (which most practitioners consider too "academic") and preparing graduates with skills that they can immediately apply in practice. Many graduates seem dissatisfied with the balance that universities choose.
- mercurio 19y agoI would suggest reading this great short story by Asimov. Its called "Profession". http://www.abelard.org/asimov.htm http://www.abelard.org/asimov.htm
- yagibear 19y agoThanks for the link; I've always been an Asimov fan. The short story format is fine for entertainment, but takes a while to get to the point: Tapes are actually bad. They teach too much; they’re too painless. A man who learns that way doesn’t know how to learn any other way. He’s frozen into whatever position he’s been taped. Now if a person weren't given tapes but were forced to learn by hand, so to speak, from the start; why, then he’d get the habit of learning, and continue to learn. I've never questioned the goal of schools to develop learning and thinking skills, rather than just convey content. However, the question is with what content should those skills be developed? It is that choice that requires a delicate balance between fundamental and practical content.
- gms 19y agoI don't disagree at all, but I'm interested in if you have a particularly memorable example where this sort of thinking helped you.
- pg 19y agoIt would be hard to think of something I'd done that didn't use this trick. There are lots of examples in Arc. I chose quite different problems to solve than language designers usually do. It's not that common to design a language by writing applications in it, and making the language have whatever features are necessary to make those applications short. In this case the difference isn't so much that I chose a different problem to solve as that I chose any problem at all. I get the impression most language design is driven not so much by explicit goals as by a collection of half-formulated principles.
- Spyckie 19y agoThe most useful thing I've learned in CS is to define and keep stringent rules while programming. These can be time/space constraints, programming time constraints, keeping the code modular, readable, or reusable, etc. Define rules that make the most sense for the project you have to do and write code with these rules in mind regardless of your own personal coding preferences. All CS knowledge learned enables you to keep to these rules. Of course, good rules to follow can be 'learn as much as possible' or 'enjoy yourself', but when it comes down to building something, enjoying yourself doesn't mean you've written good code.