Do you enjoy solving tough problems and grappling with technical challenges? Google Code Jam is a coding competition in which professional and student programmers are asked to solve complex algorithmic challenges in a limited amount of time. The contest is all-inclusive: Google Code Jam lets you program in the coding language and development environment of your choice.
Google Code Jam begins in July and continues in August, when you will compete in online rounds against contestants from around the world. The Top 500 participants will advance to onsite competitions at a local Google office to compete against those in their region (Asia Pacific; Europe, Middle East and Africa; and the Americas). The Top 100 will participate in the final round at the Google Headquarters in Mountain View, California on Friday, November 14.
Don’t be left out! Make sure to register between June 17 and July 17, and show your coding creativity in Google Code Jam. The top 100 finalists will divide over $80,000 in prize money!
Source: http://code.google.com/codejam/
Do you actually think you can rid the world of the scourge that is Internet Explorer 6? We can only hope, but the truth of the matter is that not all users have the luxury of upgrading their browser, and some simply fail to see the flaws and therefore adopt the “if it aint broke, don’t fix it” mentality.
For the next few years we’ll probably need to continue supporting Internet Explorer 6, but that doesn’t mean we just have to wait for users to find something new. The goal of SaveTheDevelopers.org is to rally the development community behind the goal of reducing the number of Internet Explorer 6 browsers in use by urging users to upgrade their browsers without hindering the user experience.
SaveTheDevelopers.org strives to be different is that they want to offer an unobtrusive option for developers to inform their visitors that there are more secure, stable browsers available as opposed to slapping them on the wrist and hiding content if they happen to visit a site using Internet Explorer 6.
Source: http://www.savethedevelopers.org
Cross-browser compatibility is one of the most time consuming tasks for any web designer. We’ve seen many different articles over the net describing common problems and fixes. Anthonyshort has collated all the information he could find to create some coding conventions for ensuring that your site will work first time in every browser. There are some things you should consider for Safari and Firefox also, and IE isn’t always the culprit for your CSS woes. Here is a quick summary of How to get Cross Browser Compatibility Every Time:
- Always use strict doctype and standards-compliant HTML/CSS
- Always use a reset at the start of your css
- Use -moz-opacity:0.99 on text elements to clean up rendering in Firefox, and text-shadow: #000 0 0 0 in Safari
- Never resize images in the CSS or HTML
- Check font rendering in every browser. Don’t use Lucida
- Size text as a % in the body, and as em’s throughout
- All layout divs that are floated should include display:inline and overflow:hidden
- Containers should have overflow:auto and trigger hasLayout via a width or height
- Don’t use any fancy CSS3 selectors
- Don’t use transparent PNG’s unless you have loaded the alpha
Source: How to get Cross Browser Compatibility Every Time
PHPBench was constructed as a way to open people’s eyes to the fact that not every PHP code snippet will run at the same speed. You may be surprised at the results PHPBench generates. It was also created so that you would be able to find discovery in these statistics and then maybe re-run these tests in your own server environment to play around with this idea yourself, by using the code examples. You can see some interesting conclusions from PHPBench as follow as well.
1. Surprising results show that if you implement sizeof() there is almost no difference in whether calculating the size of a loop in advance.
2. In reality the echo and print functions serve the exact purpose and therefore in the backend the exact same code applies. The one small thing to notice is that when using a comma to separate items whilst using the echo function, items run slightly faster.
3. The while loop 90% of the time is indeed slightly faster.
Requirements: –
Demo: http://www.phpbench.com/
License: License Free
Nick La has made another great great tutorial for us. Nick La shows us how to decorate our images and photo galleries without editing the source images. The trick is very simple. All you need is an extra tag and apply a background image to create the overlaying effect. It is very easy and flexible with over 20 styles, from a simple image icon to a rounded corner to a masked layer (both decorative and complex). To change the look and feel, simply edit the CSS specifications of the span element. To show how flexible it is, Nick La has created 15 different styles as examples for us (notice the HTML markup is same).
Source: CSS Decorative Gallery
If your website doesn’t stand out and do a heck of lot of things right, then chances are it’s going to crash and burn. Take the “Successful Website Checklist Challenge†designed by Chromatic Sites and see what you’re doing right, what you’re doing wrong, and what you’re forgetting to do. They have even included notes and resources for nearly every item on the checklist (just to make your life easier). The checklist is divided into the following sections.
1. Planning
2. Design/Layout
3. Usability/Accessibility
4. Content
5. Website Optimization/Standards
6. Search Engine Optimization/Marketing
Source: The Official “Successful Website Checklist Challenge”
As web designers, we’ve grown pretty good at understanding how to create a modern, semantic, accessible website using XHTML and CSS. We understand what makes a good website, and how to make it happen.
When it comes time to design emails though, do all the same rules apply? Are there things we should be doing specifically for email that don’t make sense on a website? Campaign Monitor has published an article of 2008 Email Design Guidelines that shows us the technical, design and information elements that make up a successful HTML email.
- Don’t waste your readers’ time — An email inbox is a busy place, you won’t get much attention.
- Permission matters — Not only do you need to have permission to email people, but it helps to remind them of how they gave you permission, as specifically as you can.
- Relevance trumps permission — Just having permission is not enough, the content you are sending must also be relevant.
- Make unsubscribing easy — There’s no point emailing people who are not interested.
- Image blocking is common — You can’t rely on people actually seeing your images.
- Bring back tables — Structural tables are still often necessary for creating columns.
- Add inline styles — Gmail removes anything else.
- Don’t forget your plain text version — You can make blocks of text more readable.
- Meet your legal obligations — For example, CAN-SPAM for US senders.
- Test, test, test — It’s the only way to be confident about your design working.
Source: 2008 Email Design Guidelines
Google Doctype is an open encyclopedia and reference library. Written by web developers, for web developers. It includes articles on web security, JavaScript DOM manipulation, CSS tips and tricks, and more. The reference section includes a growing library of test cases for checking cross-browser and cross-platform compatibility.
Many sites offer browser compatibility charts, but few back up their compatibility claims with repeatable tests. Google believes strongly in the value of test cases and automated regression testing. All of the tests in Google Doctype can be run individually or in groups, using the JSUnit automated testing framework. This allows us to update our charts quickly and easily as new browser versions come out. It also allows you to test in your own browser to see exactly what the compatibility claims mean.
Many sites offer developer resources for the open web, but few sites make those resources available under open licenses. You can read, but you can’t download. Or you can download, but you can’t redistribute. Google makes it easy to download the entire encyclopedia and take it with you, publish it on your private intranet, or package it for redistribution.
Source: Google Doctype
Few days ago, we have SEO Cheat Sheet from SEOMoz. Now, Nick La from WebDesignerWall has discovered that just over 1 out of 10 people don’t think SEO (Search Engine Optimization) is mandatory as a designer as well, therefore he has written an SEO Guide for Designers who want to learn about making it easier for websites or blogs to be found by search engines. He explains the common mistakes made by designers and developers. He also provides some basic tips that you should be practising to optimize your site for search engines.
Source: SEO Guide for Designers
SEOmoz has become a recognized leader in the field of SEO by providing the very highest quality solutions to their clients. These services are intended to help websites achieve higher rankings and greater levels of traffic through the organic listings on search engines (Google, Yahoo!, MSN & Ask). Recently, SEOmoz has released The Web Developer’s SEO Cheat Sheet which I have found very useful for webmasters. The Web Developer’s SEO Cheat Sheet shows us the following.
- Important SEO Html Tags, Search Engine Indexing Limits
- Recommended Title Tag Syntax, Common Canonical Issues
- 301 Redirect, Important Search Engine Robot User-Agents
- Common Robot Traps to Avoid, Robots Meta Tag Syntax
- Robots.txt Syntax, Sitemap Syntax
Source: The Web Developer’s SEO Cheat Sheet
