Laurier Rochon

art, technology and other nice things


I made these

What is What?
What is what?
Doubting.us
Doubting.us
Digital ecology
Digital ecology
iamclean.org
iamclean.org
EASE
EASE
Fish need hard drive
Fish need hard drive

Find the gat

Guardians of the world

Suburban twins

{} Trailer


It's a bad time to be a good web developer


Had this thought today while talking with a colleague at work, we are currently transitioning between many browsers as some are on the rise, others dying out – but one thing is for sure, we’ve past the time where developers had to check their website in IE and Firefox (if you had time) and that was good enough. With people buying more Macs, the Safari people are starting to have their say in the misaligned floating div wars, Internet Explorer 8 just came out, but people are mostly on 7, while a bunch (15% according to w3schools, using stats of their users) of dinosaurs are still lagging on IE6. Then you gotta make sure the Chromers are happy since they already have 3% in less than a year and moving up fast, and if you’re lucky enough that your css hasn’t exploded in a million pieces a few times, you can check Opera and then maybe pat yourself on the back…

I’m all up for choice and having options when it comes to choosing whatever technology suits you best, but we web people should all get raises or something, you know…

Good things to know about SEO


I think most people working at building the web have figured these things out, but there are a lot of details I never knew of when reading Michael Bluejay’s article on Websitehelpers.com, such as putting the most relevant parameters in a GET method first, for the search engines to find them faster. The article is rather dated, but still interesting or useful if you’re starting out with this stuff.

 

Instead of focusing on building a quality site with good, useful information, I should try to find some “trick” to make my site rank well.

FACT: Focusing on tricks is a waste of time. Build a quality site and they will come. There is no magic bullet which will rocket you to the top of the SERPs. There is no way Google could rank eight billion web pages by using only one criterion. There are reportedly hundreds of different factors in Google’s ranking algorithm. Thus your chances of dominating the SERPs by making one specific change are slim.

A search engine’s algorithm is the formula it uses to match websites with a search term. Naturally, the engines keep the details of their algorithm a secret. The algorithm isn’t a simple formula, it’s likely more complicated than most of us would expect — or could even understand. Google’s algorithm reportedly contains hundreds of factors, and Google has dozens of Ph.D’s on staff who constantly tinker with it. They have to, in order to be able to return relevant, high quality sites when there are so many junk sites trying to trick their way to the top of the SERPs. Changes to the algorithm don’t just involve adding or deleting criteria, but also weighting the criteria — figuring out how much each factor should count in the ultimate ranking. It likely goes further than that: Rather than deciding how much weight, say, they <TITLE> tag should carry, the algorithm likely says that when certain criteria are met then the <TITLE> tag should be evaluated a certain way, and when other criteria are met the <TITLE> tag should be evaluated in a different way. The engines could also easily add a randomizing element to the mix to make decoding their formulas virtually impossible.

It’s pointless to try to figure out the details of an algorithm because:

-You probably can’t. The algorithim is too complicated, and it’s extremely difficult to test your assumptions because it’s nearly impossible to correlate cause and effect.
-Even if you figured out some of it, it’s going to change soon anyway.
-Even if you figured out some of it, there’s no guarantee that your strategies would work well for the other engines. Each engine uses its own proprietary algorithm.
-It’s easier — and more rewarding — to focus on building a good site rather than worrying about what the algorithm du jour is.
-Nevertheless, many webmasters try to figure out the details of the algorithms and tailor their sites to what they think they’ve discovered. Such webmasters are known as algorithm-chasers.

There have been certain tricks that people have discovered over the years, but as soon as they exploited them the engines closed the loopholes. The engines aren’t stupid, and they’re not going to stand by while a bunch of webmasters try to game the system. Any trick you might be lucky enough to discover will have a short shelf life. It’s not a long-term strategy.

It’s a good idea to make my keywords invisible, such as by having white letters on a white background.

FACT: The engines are not stupid. But stupid tricks like invisible text can get your site penalized by some engines. Focusing on tricks is a waste of time.

Trading links with any site which will link to mine is a good idea.

FACT: Trading links with anyone is silly. If you have standards in real life (and you should), then you should have standards on the web, too. Don’t associate with useless websites. Choose your friends carefully.

The best n00b ruby on rails tutorial


http://ruby.about.com/od/rubyonrails/ss/railsblog1.htm

I am trying to get my head around Ruby On Rails whenever I have a bit of spare time, and I can tell you, it’s not that simple. Amidst all the directory moving, server starting and command throwing , just to get things working properly, everybody seems to just be screaming for joy, telling us how great RoR is.

Now, I’ve gone through many many many many (many?) tutorials, trying to actually break things apart in an attempt to understand what the hell is going on – but unfortunately most of the tutorials go something like “add a line in your route file to make sure we can catch the url view ‘Lorem Ipsum’”.  Now, I understand vaguely what that means, but can’t you give me an explanation as to what the parameters are/do? Or at least mention that the order is important….

Usually, things on About.com are just plain retarded, but I’ve found this awesome Step-By-Step tutorial going through all the basics in very very easy to understand English, and they actually break things in little pieces so you can replicate or build on any of the steps. It goes a little like

1) Setting up ROR
2) Building the blog application
3) adding some layout to skin it a bit
4) Adding RESTful authentification (very useful!)
5) Allowing comments
6) Adding REDCloth

Starts here : http://ruby.about.com/od/rubyonrails/ss/railsblog1.htm

 

© 2009 Laurier Rochon. All Rights Reserved.

This blog is powered by Wordpress and Magatheme by Bryan Helmig.