Also I made an schema-application tool to keep track of which .sql files have been applied in what environment.  Trust me, this is useful.

So where did I go for two months, far, far away from Gruedorf?  I honestly can say I was shocked to crack open this dev folder to find the last svn log from July 10.  So wherever I went, it didn’t seem as long as it was. :(

function test_nine() {
	$$"9" = 22;
}

fails to parse.
(which is good, I suppose)

This passes:

function test_nine() {
	$n = 9;
	$$n = 22;
	$this->assertEqual($$n, 22);
}

-Andy Friesen,
of giant-communist-robots.com.

…it sets $whatever on my outer instanced class.

Here’s some illustrative code:

<?
    class Inner_Static {
        function burrito() {
            $this->_member = ‘A keyboard. How quaint.’;
        }
    }

    class Outer_Instance {
        function taco() {
            Inner_Static::burrito();
        }
    }

    $my_guy = new Outer_Instance();
    $my_guy->taco();

    print ‘$my_guy->_member: ‘ . $my_guy->_member; 

This boggles my mind a bit. Tracking it down cost me a bit of time. Is there actually a sane use for this little tidbit, or am I justified in thinking that a good language would warn you that scope shenanigans are going on here?

A need for a simple one-off occurred Monday evening at work. Some non-engineer coworkers needed to be shown how to make some non-Latin-1 text into html entities.

Basically, they needed a 5 line php script.

Right before sending them to any number of sites that already do this 5-line operation, I decide: what the hell, I’ll just make one of my own. And so, that night after unwinding, I did.

Here’s my HTML Entitizer. Suitable for all your HTML entitizing needs, large or small!

PHP in Escape from L.A.(jokesfornerds)

One of the reasons PHP is so popular is the fact that it’s got so many handy little functions. In this case, htmlentities() is the blade of PHP’s swiss army knife that we’re using. Of course, indiscriminate use of functions like this cause problems like double-escaped characters (&) showing up in databases.

PHP’s solution to this sort of thing is generally to throw new corkscrews and toothpicks onto it’s ever-growing pile of tools on it’s knife. If you look at the documentation page for htmlentities(), you can see that as of version 5.2.3 of PHP, another optional parameter was added: double_encode. Which will

Getting the right escape order can be hard, especially for novices or small teams inheriting code from other small teams. To date I don’t think I’ve inherited work on a webapp whose database wasn’t littered with extraneous &’s and rogue \\’s. It’s only by virtue of verge-rpg.com having a single developer who is really, really annoyed by this problem the the point of neuroticism that & never appears in the database except in posts that actually wanted to display &.

Although even this level of OCD-database-cleansing didn’t prevent escaping-related errors on the first go-round.

Teh (sic) Implementation.

So, the only time-consuming part of getting this script into my wordpress site (other than me taking a bloody half hour to blog about a 2-minute job) was convincing wordpress that it should allow <?php fragments into my posts.

Luckily, other people before me have wanted this very thing. WordPress’s biggest strength is again one of PHP’s: if you want it, it’s already been made for you. In this case the Exec-PHP module will let admin-level users of your blog post for-reals, actual PHP into your posts! You’d better hope your admins don’t have their accounts compromised! (…one moment. Changing my password.)

In PHP’s case, the code that you want that’ already been written for you is in every single function’s talkback thread. These functions may not be hyper-optimized or the best solution for any given problem, but they generally are what you want to prove a point. You scan the docs, you grab the code, you put it in your site, and you move on to the next problem in your own app.

Quick and dirty, the way PHP likes it.

For the curious, here’s the solution I spat out (copy included):

<h1>Escape html</h1>
<p>This is a simple script to give the escaped codes for some html. Useful
for making foreign languages play nice with html, regardless of how the
server handles string encoding.</p>
<?
if( isset($_POST['escape_me']) ) {
echo('<h2>Your escaped html</h2><div'.
     'style="background-color: #ddd; padding: 8px;">');
echo(str_replace('&','&amp;',htmlentities(stripslashes($_POST['escape_me']),
     ENT_NOQUOTES,'UTF-8')));
echo( '</div>' );
}
?>
<form action='/html-entitizer/' method='POST'>
Text to escape:
<textarea name='escape_me' style='width: 550px; height: 200px;'></textarea>
<input type='submit' value='Create my html entities'>
</form>

(weird formatting so it doesn’t run off the side of the screen; I don’t actually code like that. Mostly. ;)

Coda

It is of note that this tiny amount of effort got me two really sincere “thank yous” from the non-engineers. It’s important to note that things that are mindlessly trivial to a programmer can be tedious tasks to someone without the power to bully the computer into doing labor for them. One of the guys, a computer saavy guy who had access to lists of what each escaped character translated to, insisted that he’d just search/replace the offensive characters by hand.

Ostensibly, this was offered to save me work.

How much time did my 2 minutes of code save him?

(Don’t forget a google for “html entity converter” would’ve saved even that, had I cared to not make the tiny toy script of my own. I’ll ramble on about re-using other people’s work more later, but it’s key to remember even what little work I did end up doing was extraneous and largely an exercise in vanity.)

Late at night a few days ago in imvu.com’s secret lair, #engineering…

<Veep> from an article on an ultimate fighting controversy about a guy
       putting slippery stuff on to gain an unfair advantage:
<Veep> Oh, and a fair word of warning to those looking to do additional
       research: Do not Google "oily sweat wrestling men."
       Just don't do it. Some things can't be unseen.
<Grue> :D
<Grue> That which does not kill you will make you OH GOD.
<Veep> that would be a good webpage: "things you shouldn't search for on
       google", with http://www.google.com/search?q=  links
<Grue> hm, yeah.
<Grue> simple apps are simple.
<Grue> it's something that you need not even moderate the submission to.
<Veep> No match for "DONOTGOOGLETHAT.COM".
<Grue> This is a compelling application, veep.
<Veep> thanks.
<Grue> you calling dibs?
<Veep> no, my queue of unfinished projects is large. if you want it, you
       can have it.

The Addiction

I have a problem with domain name purchasing. They’re all so pretty. Most of my domains are empty, so the idea of a fully operational site made within a few hours of coding was very appealing to me.

I haven’t had a simple project since I made my exceptionally puerile knockoff of ipchicken.com (whose sole functionality is to display $_SERVER['REMOTE_ADDR'] and $_SERVER['HTTP_USER_AGENT'] to the user, and doa ip2latlon lookup to feed to gmaps. Oh: and a gif png of urine.). The idea of completing an “art project” website in less than half a day and throwing some ads on it to potentially make it so it can be cash-neutral for my lifetime as far as domain re-registration costs go is oddly, strangely, irrationally appealing to me. And this felt like that.

So I bought donotgooglethat.com.

And then I bought dontgooglethat.com and made donotgooglethat.com 301 redirect to this one. Because I have a problem with buying domains.

The Implementation

Who needs security or user auth on a site meant to provide terrible, sullied links to the underbelly of the googleverse?

Style decisions

I started out by ripping apart a copy of everyone’s favorite search page. After taking out a bunch of stuff (wow, they use tables!) I was left with a raw googlish-looking site. I replaced the topbar links with a few links to some of my sites, and added the minimalist google ads to the side, with a link to the real google on the right.

My goal is to be googlish but not confusable with the Real McCoy for legal reasons, so I opted not to go with any rainbow text or the google Font (Catull, for you typography nerds).

Even so, I’m wary of using the trademarked term. Worse comes to worse I’m out $14 for reg costs and have a cute story.

Finally I grabbed two icons from the Silk Icon Set over at famfamfam. Even though I’m a competent sprite artist, I was trying to get this done as quickly as possible.

User Experience Decisions

I wanted to keep it damned simple. So I opted for only showing the top ten “worst” searches that were upvoted, without an option for pagination. There are no “about” pages since the links go straight to google searches, so there’s no need for SEO’d urls or concern for “losing valuable index space” by not exposing all of the content. Who cares? Not this site!

Each of the top ten links can be voted up or down. On successful vote (or failure!) you’re notified above the dontGOOGLEthat header. You can add a new search by clicking on the yellow button after entering some (hopefully offensive) text into the search box, or just by searching (done via an async post onClick of the “No Don’t Search” button).

The search results go to an adsense’d google personal search result page, which I chose to keep unbranded. The rationale here was that I want this thing to basically net $7 a year, so the least annoying way to do that would be to tie any possible revenue into the only real thing it does: making searches. Even so, I’m not pleased with the results; Google Safesearch seems to be on by default, and I couldn’t find anything (in the five minutes I scanned for it) in the customized search api to turn it off programatically or via a pref setting in adsense.

I decided to put a minimal amount of discouragement for vote-hammering by putting a session-based lock on votes in. However, anyone with half a brain and an ounce of desire can get around it. Really: I don’t care. Should I start caring, it wouldn’t be that hard to fix it or just disable voting…

To get a small amount of churn, the most recent search shows up at the bottom with a googlish New! next to it, and the option to upvote it there.

Also to promote searching, I did the same very simple trick google did to up their revenue long ago: a

document.getElementById('q').focus();

on page load. This just puts the cursor straight into the search form, so when you load the page and type, the input goes straight there. Such a tiny trick, and it netted them millions and millions more dolars in revenue. And it improved the user experience.

Codey Decisions

MySQL Database: One table. Three fields: id, query, and votes. Trivial.

Two queries per page load: one to get the top ten votes, one to get the most recent post. The votes field has an index (normal), so both queries are optimally cheap.

One of two optional queries per page load: an insert of a new search term or an up/down vote. The insert actually is two queries: one to see if a search already exists, and if it doesn’t: do an insert (and if it does, and you haven’t already voted on it, upvote it!).

No templating. No javascript libraries. A few boilerplate functions (mainly query error reporting stuff I handrolled years ago that’s been very faithful and useful). A few lifted javascript functions (because who needs to include all of jQuery for a single XMLHttpRequest call?). A google analytics tracker just for the hell of it, because analytics are fun!

There is only the main index and the About page, and the about page has no preprocessing logic.

The index weighs in at 12kb, and 297 lines.

A few tests shows that the main index presently renders in 0.008s from a cold start and in 0.001s afterwards. I assume this 8x speedup is just Filesystem or OS or MySQL or Apache level caching, since I sure didn’t put any caching in myself.

The whole operation was 4 hours top to bottom, sans tweaks here and there for the past few days. This is roundtrip from registration, administrative stuff like editing my dns entries, apache conf files, setting up the database user, setting up an adsense and analytics account, and then implementation. The actual coding part was between 60 and 120 minutes, mostly debug stemming from sandbox/server inconsistencies. A lot of time was also wasted talking to the girlfriend on gtalk.

For contrast, this blog post has taken about 90 minutes in a text editor, and currently weighs 8kb. The line count is lower, but the lines are far longer; English is a less concise language than PHP… but even English is more internally consistent than PHP.

And that’s it!

I’d like to see if it gets some use, but I’m not exactly sure who to expose it to to see if anyone cares. I thought about posting it to 4chan, but I don’t think it’s got enough shock value for that, especially since it defaults to safesearch.

Even if it rots in obscurity, though, it’s a tiny completed work, so I’m all good by it.

If anyone has any comments or suggestions: please leave them!

A screenshot of code for Syn

As a brief gruedorf update, I’ve completed moving the old site’s code from mysql_fetch_row() to mysql_fetch_assoc() on all queries with tablename.* on their select clause.

I can now move forward with the beta site’s schema changes unimpeded.  

Hell truly is revisiting old, crufty code made by yourself.

As an unintentional side effect, several old bugs have cleared up.  Apparently in the past I added fields and some time later noticed bugs and never correlated the two events happening.  

Hell truly is revisiting old, crufty code made by yourself.

I added a screenshot of the last two days of gruedorf progress for Syn, who apparently likes screenshots.