Both the NYC and London offices of theMechanism are hiring.
New York City
We’re seeking a creative, confident and professional Web Developer for our NYC office. You’ll need to demonstrate that you’re an efficient xHTML/CSS expert who stays on top of future trends. We’re looking for someone who is excited, creative and can work in a comfortable team environment to develop standards-based, lead-generation sites.
Central London
We are looking for a developer with 3-4 years experience building functionally-rich web applications to join the team in our Central London office.
theMechanism is excited to launch our newest podcast series: barKode.
While our other podcast, theMechcast focuses on group discussions, barKode (partially named after the last name of our Senior Developer in New York, Jeffrey Barke [note the wry use of his last name barKe in the title]) will be focused on educational web design and standards-based talks, including those delivered at the The New York Web Standards Meetup Group. The first episode of barKode is called, “Web Mapping Part One–Google Maps Tutorial” where Jeffrey Barke, Senior Developer at theMechanism, leads a two-part discussion on web mapping in general and Google Maps in particular. Part Two will be on February 21st at 6:30 at the New York Creative Bunker.
You can subscribe and enjoy future episodes of barKode at feedburner.
Rashmi, here's the link I promised: Sasha Maps—A Google Web Toolkit-based library that provides functionality similar to the Google Maps API. I've never used it, because I don't know Java.
Next month will be less of a presentation and more of a roundtable as we continue our web mapping discussion. While the focus will remain on Google Maps, we'll also talk about alternatives, both commercial and open source. Other topics include: best practices, our favorite mashups, and what makes the good ones so good.
Please send the URLs of your favorite mashups, any development questions, and any tutorial requests to Jeffrey prior to part two. Thanks!
Please contact us if you'd like to present at the March or April meetup.
The iPhone platform elegantly solves the design problem of small screens by greatly intensifying the information resolution of each displayed page. Small screens, as on traditional cell phones, show very little information per screen, which in turn leads to deep hierarchies of stacked-up thin information—too often leaving users with "Where am I?" puzzles. Better to have users looking over material adjacent in space rather than stacked in time.
To do so requires increasing the information resolution of the screen by the hardware (higher resolution screens) and by screen design (eliminating screen-hogging computer administrative debris, and distributing information adjacent in space).
This video shows some of the resolution-enhancing methods of the iPhone, along with a few places for improvements in resolution.
Read the rest of Tufte's thought's and view the video here.