I am a Software Engineer, Technologist, Gamer, but most importantly, I am a student of life.
I recently found myself in a tough situation when I accidentally typed rm * <dir_name>/ as opposed to rm <dir_name>/* , deleting the current project I was working on. Having instantly realized my mistake, I quickly unmounted my drive and powered down the machine I was working on. As I frantically searched the net for some way to undo what I had just done, it seemed as though my month’s hard work was slipping further and further down the drain. Almost every post and response I found seemed to point towards the horrible truth that I might have to rebuild my entire project from scratch. This, of course, was not a suitable solution.
As defined by wikipedia,
Web standards is a general term for the formal standards and other technical specifications that define and describe aspects of the World Wide Web. In recent years, the term has been more frequently associated with the trend of endorsing a set of standardized best practices for building web sites, and a philosophy of web design and development that includes those methods.
I have been a proponent of Web standards ever since I created my first web site back in early 2000. Back then, I was only following what I thought was the correct way to do things, and having the word ‘standards’ seemed to make this movement official for me. As I learned more about these web standards, the importance of the best practices set forth along with the concept and goals of creating markup that would display the same across browsers, the more it all seemed to make sense.
However, seven years later, I am still creating web sites/applications using PHP, XHTML and CSS, but I am getting ever so frustrated with these so called “web standards,” mainly due to the quirks and lack of support in IE6 and to some degree IE7. I am not an XHTML or CSS guru, but I think I know enough to write decent markup and styles to be effective (please don’t judge me using this site, after all, this theme was found on a wordpress theme site and I haven’t had the time to clean it up). Just the other day, I was working on a site that required a three column layout, with columns of equal height, so I decided to use alistapart’s Holy Grail.
Wordpress has really come a long way since I first started using it back when it was version 1.0. It now has a nice clean admin interface (although I am currently using the tiger style admin), a clean and simple installation script, and my new favorites, dynamic sidebars and widgets. However, I noticed that the default links widget creates invalid XHTML markup. After a few minutes of looking through the XHTML and widgets.php file, I realized that the culprit was in fact a core wordpress bug. Currently, wordpress creates widgets with the following code:
I recently found myself writing a REST web service, which, in my opinion, is the easiest way to create a web service, for a project at work. Using XML.com’s How to Create a REST protocol as my Guide, I went to work. However, when I tried to create a service to update some data, I wasn’t sure how to send my data in a POST request using PHP. After some stumbling around, I found what I was looking for on Wez Furlong’s blog which led me to PHP’s documentation on HTTP and HTTPS wrappers.
The following is a code snippet from the HTTP and HTTPS documentation that shows how to easily send data using HTTP POST:
Since I don’t play the game as much as I did when it first game out, I have no business trying to analyze the flaws of the original compared to what Blizzard has done and is doing with the sequel. Therefore, I will stick to enumerating the new additions found in this latest gameplay trailer.
Having used Code Igniter for some small projects at work, I recently decided to take the time to acquaint myself with the Zend Framework(ZF) so that I could build my own comparison between two of the most, in my opinion, developed and used PHP frameworks. While I love the flexibility and functionality offered by ZF, I have become very frustrated and annoyed with some of their documentation. Even though it is detailed and expansive, it is no where near complete and somewhat frustrating to use.