Right after I graduated from college, I taught 2 low level CS courses over a couple of semesters. Two of my students created some sort of chat program where you could punch your friends in the face if I remember correctly. It was awesome.
Now they’ve graduated and brought something even more amazing into this world: ManBabies.com
I could try to describe it, or respond to it, but I really think you just need to see it for yourself.
I’m so proud.
In case the problem isn’t obvious, I’m listening to LugRadio and Rhythmbox is displaying album art for Songs for Worship Country. I don’t even own an album by that name, so Rhythmbox randomly picked it, one can only assume, based on its own personal preferences.
Ironically despite living in the Midwest and being a Christian, I like neither Country nor Praise and Worship music.
Just noticed my first post appeared on Unofficial Planet Python.
Hello all!
If you’re really bored, you can learn more about me or read all of my posts.
Suffice it to say I’m a new Python consultant. Monday, October 15th, was my last day at my old job, and I’m very excited to be starting a new web development company, Lo-Fi Art, with my friend Chris Pitzer! (No links because I’m really not trying to shamelessly advertise, I’m just excited!)
At any rate, thanks to Christian Wyglendowski for introducing me to Python and now getting me on the Unoffical Planet Python!
I come from a PHP (with some .NET) background, so I’m sorry if my posts seem simple or mundane to experienced Pythoners. I can’t help it if the beautiful simplicity of Python is exciting to a PHP/.NET refugee. 
Contrary to popular belief, Gmail was actually created in 1988.
That’s code by caker, one of the admins over at my favorite hosting provider, Linode. You can see all the “g-mail” code he could find. Unfortunately:
<@caker> there’s more, but that’s all I could find. Pretty sure my 3.5″ floppies labeled “g-mail backup” no longer function
Web Worker Daily’s 7 Rules for Communicating … In E-mail are pretty good, but they miss one of my pet peeves.
Separate important statements or questions into bullet points or at least their own paragraphs. This makes replying much easier.
For example here’s the wrong way to do it:
Thanks for looking into foo. But what about bar? I’d also like you to change oo in foo to more closely resemble the ar in bar. Whats the ETA?
I can’t reply to individual statements easily that way, so write like this:
Foo looks great but make the oo look more like the ar in bar.
How long will that take?
How long until bar is done?
Then I can easily reply inline with clear and concise answers:
> Foo looks great but make the oo look more like the ar in bar.
Great. That shouldn’t be a problem.
> How long will that take?
End of day today.
> How long until bar is done?
After the above changes to foo it should take about another day.
But wait! It gets better! Now the discussion can continue on just one point very easily:
>> How long until bar is done?
> After the above changes to foo it should take about another day.
bar is higher priority than foo. Please do it first.
Tada! Short and sweet communication. Not only that but you can forward that last message to someone else and they can read it from top-to-bottom to catch up.
This same conversation in the usual top-posted-paragraphs format would be an unreadable mess to outsiders by the end.
Now if only I could learn to be less verbose…
I tendered my resignation at Tremont District #702 Schools today.
In 2 weeks I’ll start working full time for the IT consultancy I started with Chris Pitzer, Lo-Fi Art, LLC.* While we mostly specialize in web design and development, I’ll be doing quite a bit of system and network administration at a (different) school at least at first.
Expect lots of posts on this topic in the near future. I haven’t been this excited in a long time, and I’ve never been this excited about work.
So send your RFPs my way! We’d love to help.
* Yeah our own web site isn’t even up yet. But no one pays us to do that.
