323 karma · joined March 10, 2018
Maybe I'm missing something, but it seems like the only blogging software that offers self-hosted comments that are integrated into the platform is good ol' Wordpress.org.
If an "ivory tower" approach is working, I'm on board, but I bet more people get value out of SICP after they have a lot of classes and experience under their belt and not the other way around.
Supposedly all of these books assume (or at least allow for) no background in programming, but I think the reality is that taking SICP or even HtDP into the intro class at a non-elite university or a community college would be a complete non-starter and/or abject failure.
What I'm trying to say is that there is a place for both of these approaches: A deep look into computer science, and the nuts and bolts of basic "get it done" programming.
Should both of these things happen in a single class, or series of classes? I think the answer is yes. But how to do that and not leave non-elite students back on the road is another matter.
I believe that the HtDP authors think that the "domain-specific knowledge" required of SICP was a barrier.
And I also understand how advanced CS students think that a class focused on how to manipulate strings, use loops, deal with variables of various types, and work with basic logic in the context of a specific computer language is NOT computer science.
But in my view, most students -- and all average students -- need to crawl quite a way, then walk, before they can run.
Even Sedgewick's Computer Science, which focuses on Java and has a wealth of great questions/assignments all along the way, could really be a barrier to students who aren't steeped in math and science. I learned some math while going through the book, but I didn't learn so much programming. Liang's approach might be too basic for someone who has already done years and years of programming but is way more approachable for those who have not.
My guess is that many professors tried SICP and had a very poor rate of success. I fully support a selective class that says, "this is very hard, but you will learn a lot and look at the world in a different way, and if you really want to understand computer science, this is the class for you."
But there also needs to be more of a gateway class for future programmers (not necessarily graduate-school-bound CS majors) that eases them into the world of writing code. Offering the basics and sneaking in some CS seems better than doing it the other way around.
In a way, it's like the difference between carpentry and architecture. You can teach people who want to build houses how to design them, but at some point they're going to have to get out a saw, hammer and nails and make something happen.
It looks like Python is your only option if you want a community of any sort who is actually doing GUI development with a scripting language (Perl/Python/Ruby)
I don't know if "Unix for Luddites" ever made it to the web, but if not, I did find my copy, and I will scan it.
If you're a developer and don't mind older packages, or if you install and manage your dev tools from outside the distribution, it can also work for you. This is a lot of people.
But if you rely on your distribution to provide reasonably up-to-date packages (and for better or worse, that's me right now), then Debian Stable might not be the right choice. When I do development in Linux, I tend to be more comfortable in Fedora, which is much more aggressive when it comes to updating packages during the life of a release. I'm not crazy about major upgrades every 6 months, though you can do it once a year if you wish.
For better or worse, I think that Ubuntu + PPAs is the path of least resistance -- if you trust the maintainers of your PPAs, that is.
All you really need in a CS class is to be able to write your code, compile and run it, and Geany does that very well for many languages. I've never been able to do that with JavaScript/Node -- that's one language that I haven't gotten working (as far as running it from within the editor).
One thing that didn't work so well for me was indentation/code formatting. When you first write it in Geany, it looks good, but once you star messing with the code, the indents can go haywire, and as far as I know there is no way to automatically re-format the code. That's where a "real" IDE comes in, I guess.