About the author: Matt Snider is the lead frontend engineer for Mint.com (now a part of Intuit), where he makes extensive use of YUI in the presentation layer. He is also the author of a popular blog on JavaScript. Matt contributed the YUI 2 Storage Utility to YUI and is an active community member; you can see his presentation from YUICONF 2009 on YUI Theater.
Natively, JavaScript has a very limited set of functions for working with numbers located on the global Math object. Mostly these functions are for working with exponents, trigonometry, and rounding. And while these functions are needed and efficient, the Math API has remained unchanged for years, and probably won’t be improved anytime in the near future. So it is up to the developers of JavaScript libraries to create and maintain a component for working with numbers.
The Number component in the YUI 3 Gallery, derived from work originally used on Mint.com, aims to fill in missing number-related functionality. It provides a light-weight set of static functions for working with numbers. The Number component weighs in at about 1.8kb after minification and before gzip; it’s supported by all A-grade browsers.
One of the features in Number that I use the most is the format() function, which injects a formatted number into a string by evaluating the format of the placeholder number in the string. (Note: This is similar to the formatting support Y.DataType.Number currently provides, but rolls up the separate configuration properties which Y.DataType.Number.format accepts into a single formatting pattern string.) The function works with all symbols, but it formats numbers according to the English standard. Here are a few example of how to use format() from its unit test:
var n = 1111.11, formatDollars = "$0,0.00'" // use comma and decimal when formatting formatPercent = "0.00%", // use decimal when formatting formatRound = "0,000", // use comma when formatting formatText = "Please add the $0,0.00 to my tab!"; Y.Assert.areEqual("$1,111.11", Y.Number.format(n, formatDollars)); Y.Assert.areEqual("1111.11%", Y.Number.format(n, formatPercent)); Y.Assert.areEqual("1,111", Y.Number.format(n, formatRound)); Y.Assert.areEqual("Please add the $1,111.11 to my tab!", Y.Number.format(n, formatText));Other useful functions include:
To use the Number allery component, first include the script:
<script src="http://yui.yahooapis.com/combo?3.0.0/build/yui/yui-min.js& gallery-2010.02.22-22/build/gallery-number/gallery-gallery-min.js"></script>Then include 'gallery-number' in your use() function, to get the following functions:
YUI().use('gallery-number', function(Y) { Y.Number = { degrees(number), number(number, format), getPrecision(number), isNotBetween(number, number, number, boolean), isBetween(number, number, number, boolean), isPrime(number), radians(number), random(number, number), roundToPrecision(number, number) }; });These functions were modeled after the native Math functions and, like the Math functions, the functions on Y.Number return NaN if the value provided is not a number. If you would like to contribute to the development of or require new features added to Number, please leave a message on the Forum.
The Yahoo! Search engineering teams are rolling out updates to crawling, indexing, and ranking algorithms. Similar to previous updates, you may notice some ranking changes and page shuffling during the process, which we expect to complete over the next few days.
To share your thoughts on this latest update, please visit the Site Explorer Suggestion Board.
Dan Rampton
Program Manager, Yahoo! Search
Since its emergence, the digital photography market has gradually supplanted the traditional one. APN and digital SLR cameras entered our lives, and some people announced the death of silver-based images. This is not all lie, and yet old-fashioned images have been particularly popular in the past few years. All we do seem to do now is try to recreate the atmosphere of those bygone times anyway. Blurry, distorted and over-saturated images are not just a fad anymore. People have became familiar with the style and even consider it a full-fledged photographic genre.
And this is where toy cameras play a role. These devices, made entirely of plastic, including often the lens itself, are not only toys. Sure, they cost next to nothing and have no controls to speak of, but this is what people like about them: they create unpredictable pictures, with equally unpredictable vintage effects. Once you understand this, the rest is a beautiful game. Take them anywhere, anytime, and photograph whatever you like.
Posted by jennita
Note: This post will make you smile, possibly even laugh. It won't however teach you much about SEO. You've been warned.
Last week I attended SMX West in Santa Clara, California and took a couple flip video cameras along. I thought it would be fun to do "man on the street" interviews, somewhat along the lines of Jay Leno's "Jaywalking" episodes on The Tonight Show. Another great idea I had was to employ the help of Dana Lookadoo from Yo! Yo! SEO to help with the interviews. Little did I know she'd be so great at it (ok, I lie. I knew she'd do much better than I would!). She did so well in fact that our video editor, none other than my (awesome) husband Rudy Lopez, mainly only used Dana's interviews. A rockstar in the making!
Rather than keeping you from this awesome video any further... I present to you: SEOmoz "Man on Street" - A Who's Who in Search Marketing.
Thanks to all our great participants!
Matt McGee, Search Engine Land and SmallBusinessSEM.com Curtis R. Curtis, Universal Business Listing Ross Dunn, Step Forth Marketing Ian Lurie, Portent Interactive Steve (sorry - didn't get his full name or company. If you know him, let me know!) Shannon Poole, Bruce Clay, Inc Greg Finn, 10e20 Danny Sullivan, Search Engine Land Virginia Nussey, Bruce Clay, Inc Bruce Clay, Bruce Clay, Inc David Szetela, Clix Marketing (didn't make it in the video, but suffered through it and deserves props!) Jill Whalen, High Rankings (again, she didn't make it in but did endure my questions!) Matt Cutts, GoogleI also had great intentions of getting several Whiteboard Friday's with some of the speakers. Unfortunately I ended up just toting a mini whiteboard around with me all week instead. I'm sure I looked like quite the winner with my whiteboard in hand. I wonder if people think all mozzers are required to carry a whiteboard around just in case they get the urge to record a Whiteboard Friday. heh.
Thanks for watching along! I hope you had as much fun watching, as we had putting it together. Again a HUGE thanks to Dana Lookadoo and Rudy Lopez for all their help.
Those of you that have been paying attention to the Django release roadmap will have noticed that the original estimated release date for Django 1.2 final has passed, but we haven't actually made a final release.
Although Django's release cycle is generally date-based, we also try to keep our release dates flexible to account for bugfixing time. At the beginning of the development sprints at PyCon a few weeks ago, over 300 tickets were still open on the Django 1.2 milestone. Now it's down to 120 (we've been clearing out, on average, about ten tickets a day), but that's still a lot more than we're comfortable shipping; as a result, we're pushing back the final 1.2 release a bit.
Some of the tickets still open for 1.2 are documentation or translation updates; these will be dealt with before the final 1.2 release. Others are minor bugs or edge cases which are difficult to trigger or unlikely to cause serious problems in actual deployment; these tickets will likely be bumped to a pure-bugfix release in the 1.2 series, or to 1.3 as warranted.
Over the next couple of days, the Django core team will be reviewing all of the currently-open tickets, and identifying those which:
Tickets which don't meet these criteria may be removed from the 1.2 milestone, or may simply be left out of the final release. We won't forget about these issues -- they'll still be in Trac, and they will be addressed -- but bugfix work prior to the 1.2 release will focus in major issues fitting the criteria above.
We're sensitive to the fact that during the Django 1.2 release cycle, we haven't paid as much attention to bugs and smaller features as we have done during previous releases. To address this, we're considering making Django 1.3 a "feature light" release -- that is, we will spend more time focussing on little features and long standing bugs, rather than adding lots of big features like we have done with Django 1.2. Once 1.2 lands, we'll have some more details about our exact plans for the 1.3 cycle.
Until then, we'll be posting here every few days to give you a status update, letting you know how many tickets remain, any problems we foresee, and to provide an updated estimate of the 1.2 final delivery date.
So: there are 120 tickets remaining, but quite a few of these of these will be bumped from the final release. It's difficult to know exactly how much work is left before we do the final ticket cull, but our first-cut revised estimate is for an RC1 release around March 22, with a final release around March 29. This is, for those of you who were following along during the early parts of the 1.2 cycle, roughly consistent with extra time added to the release schedule for the 1.2 alpha and beta milestones.
As always, any assistance preparing, reviewing or testing patches is most welcome; the more help we get, the sooner we can release. If you want to help out, check out the 1.2 todo list, find something that sounds interesting and dig in!
Posted by randfish
WARNING: Get ready to read with this one. There aren't a ton of fun graphics or quick bullet points, but I do promise that if you read through, you'll feel much more knowledgeable about the topic, and likely get more value from organizing, speaking or attending an event.
Over the past 6 years, I've attended nearly 100 conferences on search, online marketing, startups and technology. I've given presentations or sat on panels at nearly all of them. I've organized our own SEOmoz seminars here in Seattle and in London, built panels for a variety of other conference series and sat in the audience for many hundreds of sessions. Oddly, in the past 3 months, I've had more discussions about the conference format and the optimization of the experience than I can ever recall in previous years.
I don't know whether it's me thinking about the problem more or just stumbling into conversations that center around conference strategy and business models, but like Twitter and conversion rate optimization, it's been finding its way into the nooks and crannies of every lunch, dinner, casual coffee or post-session beer.
Wow... Even Google Trends says this is a hot topic.
I consider the organizers of conferences like SMX, SES, Pubcon & many overseas events (RIMC, SMX Sydney, the SMX/SES shows in the UK & Europe, etc.) to be both good friends and good people. This blog post is in no way meant to denigrate or cast aspersions at their intents or achievements (which have been remarkable - SEO itself has gained tremendous legitimacy because of their efforts). Quite the opposite - it's meant to highlight some of the reasons why things we, as conference goers and speakers, complain about continue and why it's hard to change the status quo. I'm also going to try putting forward some ideas at the end of the post that I have seen work well and would love to see more of (or more experimentation with) in the future.
Competing IncentivesOn one side, we have conference & event organizers. They have businesses to maintain, revenue and profits to grow and pressures from owners/investors/boards to meet certain goals. They have to please advertisers.
On the other, we have attendees (and, to a lesser extent, speakers) who want to learn, have an enjoyable experience and get personal and professional value from the event(s). Most attendees are not paying themselves - this is a business expense they need to justify and hence, managers and C-level types hold the pursestrings.
In the subsections below, I'll try to walk through the competing incentives and goals of these two parties and why they make the conference experience so tough to perfect.
Venues, Locations & TimingThis is one of the easiest dichotomies to describe. In one corner, we have the organizers, who are optimizing on cost. In the other, we've got attendees, who want the best experience (particularly if they're traveling). Not surprisingly, every organizer wants to hold their event at the best possible time in the most optimal location. That means, at least here in the US, winter events in warm weather climates like southern California, Las Vegas, Florida and Hawaii, summer events in mild climates like the Pacific Northwest or the Bay Area and events in extreme climates like the Northeast and Midwest in Fall/Spring.
Economics dictates that supply for these optimal locations at optimal times will be low because demand is high. This also means that prices will rise accordingly. Organizers know it's hard to pass those costs on to attendees. Once a conference's price has been set for a few years, fluctuating dramatically is challenging.
What many may not realize is some of the additional, behind-the-scenes inputs. For example, conference venues like to book 12-18 months in advance (sometimes more for very large/expensive/high demand events/locations). They require down payments and guarantees, since re-booking a space if an event cancels 3 or even 6 months ahead often proves impossible. In addition, advertisers, speakers, exhibitors and conference goers themselves get accustomed to certain events at certain times in specific places. Changing an established event always carries risk.
Next time you wonder why SES has a show in Chicago in December and New York in March or why RIMC hits Reykjavik in winter, remember that costs, momentum and contracts make those very hard things to change. If we were all willing to fly to Anchorage in January, you can bet the costs would be rock bottom.
Attendance LevelThis one isn't quite as clear cut. For some attendees, an intimate, small show experience is ideal. You get one-on-one time with the speakers, more opportunity for Q+A, a less stressful environment and, typically, easier times with everything from getting good food to booking hotels to scheduling meetings with other conference-goers/speakers. However...
The incentives are frequently the reverse for both speakers (who want large crowds so they can justify the travel expense and preparation time) and for organizers (who have a tough time charging enough to a small group to make up for what a larger base could bring). Organizers also want to signal that their event is "a big deal" and high attendance numbers is one of the best ways to do this.
So why not go for huge venues and trim the costs down to minimal levels I hear you ask? Good question.
The obvious answer is profit margins, but it's not the whole reason. Advertisers, sponsors, exhibitors and even speakers want to be in front of "qualified" audiences. An audience of web marketers paying $100 to go to a show is hard to pitch as a compelling and potentially lucrative base to these groups. However, if tickets are $1,800 and 5,000 people show up, every speaker and sponsor in the world wants to make their voice heard and presence known to that group. Even the big industry players like Google, Microsoft, Facebook, etc. will be willing to lose their top notch talent for a week to get in front of the audience, mingle with the crowd and network with the best and brightest.
Some attendees are also more excited by large events. They provide greater opportunities to meet a high quantity of peers and help lend credibility to the value and importance of the event. They also tend to draw big name speakers and presenters, which means a perception of greater value from the learning aspects of the conference.
Of course, this is all balanced by the availability and affordability of venues. SMX Advanced happens in Seattle and for each of the past 2 years, it's been completely sold out. The organizers could go to a larger facility, but Seattle doesn't have many that support in excess of 2,000 people without dramatically raising the costs (and likely lowering quality). It can also be a positive signal to consistently sell out a show - every SEOmoz seminar we've thrown has sold out weeks before the event and this means more early bookings, greater consistency in attendance and revenue and an easier time planning (to be fair, SEOmoz's seminars are a small fraction of the size - 150-250 attendees - of large conferences like Pubcon, SES, SMX or even OMS).
SpeakersThings get more contentious and thorny around the issue of speakers. Attendees and organizers alike can agree that in a perfect world, only speakers who consistently earn top ratings and attract large followings would present. Sadly, in virtually every industry, these individuals comprise only a handful of players. Google's Matt Cutts and Avinash Kaushik are likely among them as is Danny Sullivan of Third Door and Seth Godin. However, I'm hard pressed to name many more that would attract paying audiences simply with their presence.
There's also a large group of phenomenal speakers like Greg Boser, Dave Naylor, Vanessa Fox, Jessica Bowman, Marshall Simmonds and the like who are excellent presenters, incredibly valuable to the audience, and, together with other positive signals, are likely to draw in paying attendees. This is where the trouble starts, though. These individuals didn't necessarily start out as remarkable presenters. In fact, I've personally seen speakers I'd consider "rock stars" today many years back and the same couldn't always be said of them. It takes a trial-and-error, weeding-out process to determine who's going to be great, and that means you need to try out new names and faces as an organizer.
Finally, you've got groups of new or nearly-new speakers, some of whom may be diamonds in the rough and others who may be complete duds. Organizers have little information to base this on other than their CV, a pitch form and possibly recommendations from previous events. Tragically, even great online writers/bloggers/personalities sometimes turn out to be less-than-amazing when placed in front of hot lights, a restless audience and 15 minutes of Powerpoint.
Organizers complain to me all the time about the necessity of finding the new stars, getting those diamonds-in-the-rough enough experience to shine and providing a diversity of speakers. Many technology conferences face the constant problem of gender imbalance and I'm certainly not immune to it. Last year, between Seattle and London events SEOmoz & Distilled had less than 15% women give talks - a shameful number, but one we definitely need to overcome.
Everyone can agree that we need more truly great speakers and fewer mediocre/poor ones. But when you're trying to discover new talent, mature up-and-coming stars AND bring as many speakers into the event as possible (see the next section), it clashes with the goals of consistently excellent quality speakers and presentations.
Session FormatsThis might be the toughest problem of all. More speakers = more attendees. And yes, that often holds true for even new speakers and those of low-middling quality. The reason is that speakers frequently invite clients, partners and colleagues as well as promote the event on their sites, blogs and social media accounts. If you want your event to have thousands of attendees, get 100+ speakers and they'll (hopefully) help spread the word for you.
The problem is the session formats this creates. In order to maximize numbers of speakers while fixing the event length, you move from solo presentations to panels with increasingly larger number of participants.
Some organizers argue that panels are a good thing and I'd agree in moderation. For something like an "Ask the Search Engines" panel, having a representative from both Bing & Google makes sense. For Q+A sessions in general, 3-4 panelists can help to spark discussion and even get into vigorous and valuable debates (at SMX West last week, my friend Roger Monti and I got into a nice tiff that I think helped keep the audience on its toes - and yes, it was all in good fun and good humor).
However, when it comes to learning about an individual topic in a robust, in-depth fashion, not even conference organizers will argue that having a highly talented panel of 4 or 5 speakers give 10-14 minute slide decks can compare to a single 45-50 minute session with a single great speaker who can go both broad and deep (and then take questions). The highest rated panels (from my understanding and from direct experience with the ones I've seen) are always those where a remarkable presenter has the full time to dig into their subject matter. Three weeks ago I was at OMS San Diego where Dharmesh Shah spoke on Twitter and Tim Ash presented on Conversion Rate Optimization. The difference between that and a panel approach is night and day - there's just no comparison.
But, as an organizer, if you optimize towards these highly rated sessions and kill the panels, you lose speakers which costs you reach and buzz and, likely, attendees. Happy attendees might rave about the value of the session in their reviews, but no one has the incentive to fill the seats like a speaker (even a bad one). Solving this issue might be a pipe dream.
Session TopicsWhat about the topic choices themselves? I hear attendees constantly complain about certain topics going missing while others get too much coverage. Organizers, meanwhile, struggle with how to fit in esoteric, but likely fascinating topics against tried-and-true (and in-demand) popular sessions.
The best thing an organizer can do is to survey their audience ahead of time and plan/prepare from that feedback. But, this is much easier said than done. Organizers don't necessarily know who's going to be at a show with enough lead time to arrange speaker schedules and build a topic plan. It's also very hard to get commitments from a large number of speakers with a shorter deadline and nearly impossible to nail down keynotes and big names without months of advance notice.
When Will Critchlow and I do the planning for the SEOmoz/Distilled seminars, we get to cheat in a lot of ways. First off, we have the email addresses of all the PRO and registered (free) members on SEOmoz, so we can survey to our heart's content ahead of time (and do). Second, we actually optimize to speakers - since we largely don't use the panel approach, we pool together a list of the speakers we've seen in the last 12 months that have wowed us and then ask them to give performances that speak to their strengths and experiences. Since we only need 10-15 speakers per event, we can personally invite a handful of top-notch folks each time.
Can a larger conference use these tactics? Almost certainly not. Their audiences aren't nearly as nicely packaged ahead of time, and panels are critical to growing the number of speakers, providing the diversity, giving experience to the "diamonds-in-the-rough," etc. Conferences like Pubcon, SMX, SES and OMS would also almost certainly take a huge amount of heat if they stopped accepting pitches and simply relied on a smaller contingent of consistently excellent speakers. Advertisers, exhibitors and sponsorships would likely drop too (even though they're technically not at all tied to the editorial programming side of the equation), and these are a massive source of revenue.
AmenitiesAs an attendee, we probably think that things like reliable wifi, better food and comfortable seating with tables and power outlets in session rooms makes a big difference. The problem is, these don't tend to correlate with how we actually choose conferences to attend and/or return to. I know organizers who've invested hugely in the attendee experience, only to see retention rates drop (despite the fewer numbers of tweeted/blogged complaints). When those dollars are re-invested in marketing the conference, drawing in bigger keynotes, or optimizing other aspects, the numbers get better (even when cardboard sandwiches and grade-school chairs are employed).
We, as conference goers, vote with our wallets, and we apparently don't care as much about the amenities as we make out to (personal note - please, conference organizers, don't use this knowledge against us too much; I love comfy chairs, good food and great wifi).
Press Passes & Guest PassesSpeaking of thorny issues - little in the conference world raises as much public ire as this one. For nearly every event it makes good sense to give bloggers and journalists press passes. However, when a big, expensive, popular event is thrown, these can quickly gobble into profit margins with questionable returns.
The problems are myriad - bloggers don't often deliver the extent or quality of coverage they promise and traditional journalists frequently make no promise of coverage at all (and then write nothing). Feeding and seating them alone can run into the hundreds of dollars per day (trust me, you don't want to know what a trade venue will charge for a cup of coffee or a bag of Cheetos). And, as savvy organizers know, some (possibly even many or most) bloggers would pay to attend the event if their press pass request was rejected. You don't want to anger this vocal minority, but you also can't afford to be taken advantage of.
For sold out events, it gets even harder. Longtime "friends" and traditional receivers of press passes may need to be sacrificed to make room for paying attendees, especially if the event relies on those last 1-200 seats for the majority of the profit margin.
Organizers know they need to be careful to be generous, but discerning, or risk becoming known for "giving free access to anyone who can set up Wordpress." They also want to try to give newcomers to the blogging/coverage scene a chance to make an impact, while being mindful of abuse and sensitive to the dangers of angering influencers. It's a tough tightrope to walk and one that press pass requesters should be more sensitive to (I'm speaking from personal experience on this one, and know that we certainly owe some apologies for past requests and perceived slights).
Optimizing the Conference ExperienceNow that we're through some of the reasons events are so hard to get right, I'll try to provide some recommendations for every participant in the process. This is personal opinion, and unlike SEO, it's not based on thousands of hours of experience, but probably just a few hundred and my own observations. Still, I hope it's valuable, or, at the least, worth considering.
Advice & Experiments for OrganizersI don't mean to be forward, but I suspect a lot of organizers, speakers and attendees in the search marketing conference space will check out this post. Please, please share your thoughts and feedback below, with one caveat - we like to keep this blog TAGFEE, so no harsh insults or personal attacks. That's what YouTube comments are for :-)
p.s. I'm just back from Searchfest in Portland (which was a terrific event that continues to get better every year). I was originally asked to give a 20 minute presentation on SEOmoz's toolset, but decided I couldn't be quite that self promotional and created a deck that covers a wider range. I saw folks giving my co-presenter, Enquisite's Richard Zwicky, a hard time over Twitter for talking all about Enquisite's software, but in fact, that's what we were asked to do and I was the one who went off-focus (so if anything, you should blame me). You can check out my slide deck here - SEO Problems and the Tool to Solve Them. Hope you enjoy and sorry about the weird formatting; Scribd didn't import PPTx very well this time.
p.p.s. Please excuse my lack of links to appropriate sites/pages/people and probably spelling errors (drove back from Portland tonight and still not over my sinus infection). Jen, if you have time early tomorrow, maybe you can help add those in? :-)
Last week, we introduced you to some great search features to keep up with the 82nd Academy Awards. The coveted statuettes have been distributed and the post-show analysis is in full swing!
The buzziest acceptance speeches of the evening: Sandra Bullock and Mo’Nique – although the story behind Elinor Burkett and her so-called “hijacked” acceptance speech blazed a path through search logs on Monday.
Best Motion Picture contender that is the most anticipated DVD in search: The Blind Side, followed by Avatar, Precious, and The Hurt Locker.
The buzz, of course, is never simply about who won. One of our favorite ways to explore major events is to check out the questions they inspired in search. One standout: “Are the Oscars the same as the Academy Awards?” (Why, yes!)
A sampling of notable Oscar 2010 search questions:
Check out The Buzz Log for more Oscar search trends and buzzing topics, courtesy of our friends at Yahoo! Buzz.
Andrea Sandke
Yahoo! Search
Last week, Yahoo! JavaScript architect Douglas Crockford delivered the fourth installment of his Crockford on JavaScript series:
In this session, Douglas tackles the DOM. On the one hand there was JavaScript, he says, and JavaScript is “what made the browser work.”
On the other hand, there was the Document Object Model, also known affectionately as the DOM. It is what most people hate when they say they hate JavaScript. Most of the people who say they hate JavaScript don’t know JavaScript, might have never seen JavaScript, but they’ve felt the DOM alright. If you don’t know what the difference is and you say, “JavaScript is the stupidest thing I’ve ever seen,” you’re not talking about JavaScript, you’re talking about the DOM. The DOM is the browser’s API. It is the interface. It provides JavaScript for manipulating documents.
The DOM may be imperfect, but it’s nonetheless crucial to what frontend engineers do when they write web applications. In this talk, Douglas provides an overview, situated historically, of where the DOM came from, how it achieved ascendance with Ajax, and what the future might hold. In Douglas’s inimitable fashion, this history starts with Sir John Harrington and takes us up to the present day. A few choice words for CSS are among the many applause lines for veteran developers:
I find within the community of people who use CSS great affection for it. They’re totally invested in CSS, they love it. They can’t imagine any other way of doing formatting in a document. It’s it. It’s sort of like watching an episode of Cops where the cops come in and break up the family dispute, and there’s this “CSS ain’t bad, you just don’t understand it like I do. I know it hurts me, but I make mistakes, I’m wrong.” CSS is awful, and it amazes me the way people get invested in it. It’s like once you figure it out, kind of go “oh, OK, I see how I might be able to make it work,” then you flip from hating it to loving it, and despising anybody who hasn’t gone through what you’ve gone through. It doesn’t make sense to me.
If the video embed below doesn’t show up correctly in your RSS reader of choice, be sure to click through to watch the high-resolution version of the video on YUI Theater.
I thought I could not be out-geeked. With a background in radio, and having dabbled in the demo scene on the Commodore 64 and hung out on BBSes and IRC for a long time and all the other things normal kids don't quite get, I thought I was safe in this area.
Then I went to my first WhereCamp, an unconference dealing with geographical issues and how they relate to the world of Web development. Even my A-Levels in Astronomy did not help me there. I was out-geeked by the people who drive and tweak the things that we now consider normal about geo-location on the Web.
Pulling out your phone, find your location and getting directions to the nearest bar is easy, but a lot of work has gone into making that possible. The good news is that because of that effort, mere geo-mortals like you and me can now create geographically aware products using a few lines of code. So, let's give the geo-community a big hand.