Yesterday, GraphSketch passed over 30,000 graphs rendered. That’s quite a few. Thanks to everyone for making it so popular.
It also seemed like a good time to release something I’ve been working on smoothing out for the past few weeks:
Yep, you can now graph parametric equations. Just head over to http://graphsketch.com/parametric (or click the “Parametric”mode just above the equations on the main GraphSketch page).
To keep things simple, you can only graph three parametric sets of equations at the same time. You can choose the range for t, and it defaults to a reasonable -10 to 10.
Also, while I was updating the website, I made the text a bit smaller (about the difference of going from a 12pt font to a 10pt font) and added a (hopefully unobtrusive) section pointing out the availability of posters, should anyone be interested. Polar graphing should come soon, hopefully, but it is somewhat possible using parametric equations by setting x=r*cos(t) and y=r*sin(t), too.
Andy Schmitz
A few notes on setting up PvPGN (the continuation of bnetd) for a private LAN. (The reason I’m setting it up is that I don’t expect to have an Internet connection for connecting to Battle.net proper, and would like to have the capabilities it provides, especially ladder games.) This post is generally much more technical than most of my previous posts, so you may want to skip it if you’re not really sure what’s going on. You won’t miss much.
So, my setup involves a router with DD-WRT, and an OLPC XO. The XO is set up using Ubuntu Intrepid on an SD card.
(more…)
In under three weeks since it was launched, GraphSketch has now been used to create (over) 10,000 graphs. It also has had over 3,500 visitors, coming from every continent except Antarctica, though many visitors haven’t graphed anything (and many visitors have graphed far more than average). Work on new features (parametric and polar graphing, among others) will likely resume after school is over, as I still have three finals remaining, and am now off to continue studying for a math final.
At any rate, thanks to everyone who has promoted GraphSketch in one place or another for making it so successful.
Andy Schmitz
P.S. If you have any suggestions for GraphSketch itself, the original post on it is still probably the best place to leave them, as I’ll check back there for ideas when I’m working on it. Thanks!
Well, this was written way back when it seemed like a good idea, and it’s finally polished enough to actually release. Yay, something I actually finished!
On the off chance you might have some recycling that needs to be taken out (and you should..), this random little tool will let you set up a weekly reminder (an SMS message, actually) to actually get it out to the curb. It’s been working for me (and a few others) for several months now, so I’m fairly sure it’s stable.
So, if you’re (partially) responsible for getting your recycling out, go head over and sign up right now at Recycling Reminder. You’ll need a standard cellphone of some sort. It’s completely free, though clicking the ads now and then gets me a few pennies, if you’d like.
Please email me or leave a comment (or something) if you happen to find it useful, have a problem, or anything else. Thanks!
Andy
(picture: The line at Staples shortly before it opened on Black Friday, it extended further than you can see here)
“Regression” is a term for a specific type of programming bug: A bug that is introduced into something that had previously worked. It’s also apparently a pretty popular type of bug, because even large, well-maintained projects have them: the OLPC software has a long list of regressions (and they’re shipping anyway – most of them aren’t big problems), and Firefox just released version 2.0.0.11 to fix a (cosmetic) regression in 2.0.0.10 (a security patch release which you should already have if you use Firefox).
Most of the time, regressions should be caught by unit testing, but for some reason weren’t. (This is one reason I don’t like unit tests much at the moment: if you know about a problem enough to test for it, you should be able to avoid it in your code.) But to me, regressions are pretty much a major reason for code segmentation: write one function that does one thing, and combine them to do other things. It should be reasonably easy to determine what inputs and outputs each function gives, and if it isn’t, that’s what JavaDoc, JSDoc, and others are for.
Overall, I really have to think that most regressions could be avoided by having enough simple functions doing well-defined things. However, that isn’t always possible or feasible, which leads to problems. Because the regressions that could easily be tested for usually are, that makes new regressions even harder to nail down, which is one of the reasons they’re so hard to fix. My only bit of advice if you’re trying to fix them is to nail down which changeset caused the problem, and investigate every part of that for how it affects other things.
Andy Schmitz
