Object Oriented Programming is the one area of PHP programming that I’m having difficulty grasping :(
I’ve managed to come to terms with functions, regular expressions and the likes, but I just can’t seem to grasp the concept of methods, and especially stuff like passing by reference! Are there any tricks other programmers out there use?
If you know of any good books, articles or tutorials that might help me in my quest to overcome this affliction, please, please, let me know!
In December 2005 we did an analysis of a sample of slightly over a billion documents, extracting information about popular class names, elements, attributes, and related metadata.
Some interesting things I picked up from the study are:
- A whole slew of people are specifying the xml:lang attribute, which will have absolutely no effect (no HTML processor will look at that attribute; it’s an XML attribute).
- Of the top twenty most-used attributes on body, fourteen are purely presentational.
- The br element is a simple one, yet used on so many pages that it is the 8th most-used element. It is used more than the p element. There are very few legitimate semantic places to use this element (addresses and poems are the canonical examples), which means that most uses are probably presentational.
- In our data sample there were twice as many pages that used the table element but didn’t use the td element
- The script element was used on roughly half the pages we checked.
Google Code: Web Authoring Statistics
Plenty of people have been talking about whether or not those that refuse to adopt web standards in web design should be entitled to call themselves web professionals.
While I agree that those who design should be looking to learn web standards, I also feel that not everyone has the same learning curve when it comes to standards. Some people need more time to learn than others. I especially didn’t like one particular quote from John Oxton (certain words censored):
What I want is HTML that kicks up a royal f*****g stink if it isn’t treated properly. HTML that takes no s**t, with a built in big flashy message (GO AWAY AND LEARN ABOUT ME!) for people who refuse to take the time to learn this super simple language and who refuse to refine their understanding.
I think some people seem to forget that it’s not a ‘super simple language’ to everyone. That quote is like a typical ‘RTFM’ response you’d get on a forum. Don’t slate someone just because they don’t know as much as you. I’m sure you wouldn’t like the same response from someone who knows more about another topic than you.
Read Jakob Nielsen’s report on the Top Ten Web Design Mistakes of 2005.
1. Legibility Problems
2. Non-Standard Links
4. Content That’s Not Written for the Web
5. Bad Search
6. Browser Incompatibility
7. Cumbersome Forms
8. No Contact Information or Other Company Info
9. Frozen Layouts with Fixed Page Widths
10. Inadequate Photo Enlargement
How many does your site fall short on?
While I enjoy most aspects of creating a website, the one part I enjoy the most is creating the initial design. I love tinkering about in Photoshop trying different colours, fonts, filters, and the likes.
I always feel good after I’ve completed a new design. I can’t say the same about coding. After I’m done coding a site/page I feel more relief than anything – relief that it’s done. But when I’m designing I’m always enthusiastic or excited. It’s a really nice feeling knowing you’ve created something new… fresh… never seen before.
What part of creating or running a website gives you the most satisfaction (not including the monetary aspect)? Is it creating the design or coding the HTML/CSS afterwards? What about search engine marketing or writing the content?