PHP is like a handgun. On its own, it is simply an inanimate tool that has no moral leaning. In the hands of a responsible citizen, it can be used to the benefit of society. But in the hands of someone who is untrained or mentally unstable, it can be used to commit horrible atrocities.
Whenever there’s such a tragedy, other developers are quick to blame PHP. If PHP were illegal, then Yahoo! would never have happened. If we regulated PHP tightly, then there would be no Digg.
via The Register
Posted via web
By posterous | May 25th, 2010 in
General |
No Comments
By posterous | May 9th, 2010 in
General |
1 Comment
By posterous | April 28th, 2010 in
Funny |
No Comments
via constipated_HELP:
Honestly, if you just move the dial to “M” mode and tape it there, after a week you will be far and away better than 90% of amateurs out there. That’s what everyone had to do until the 70s, and they didn’t even have a screen to make sure they got exposure right.
Here are the basics of what you need to know:
There are three camera settings that control exposure – shutter speed, aperture, and ISO. Set the Iso as low as you can for the amount of light you have (daylight 100-400, twilight ~800, indoor 800-3200), then set shutter and aperture according to fine adjustments in lighting. There is a lightmeter inside the camera; use it, then check exposure on your screen to make sure it’s okay.
Shutter speed (1/60, 1/125, 1/250, etc) is the amount of time the shutter is open. A rule is to keep the shutter speed at 2x the length of the lens to get sharp handheld shots (18mm = ~1/60, 50mm = 1/125) – this can be knocked down significantly once you get better.
1/15 is for getting blur on slow objects while panning example, and 1/125 is just about the fastest you can use for panning fast objects. 1/250 will freeze sports with less motion, and by about 1/500 you should be fast enough for most action.
Aperture (also f-stops) is how wide the lens is open. Small numbers correspond to large openings. f/2.8 is rather large, f/16 is rather small. Small aperture numbers (large openings) mean less is in focus. (Think of it this way – if you need glasses, take them off. Looking through squinted eyes or making a small hole between your index finger and thumb will make everything look sharper.)
So – shallow depth of field (less in focus) – f/2.8. Deep depth of field (more in focus) – f/11.
Finally, ISO. Iso is simply how sensitive to light your camera is. 100 is the best one because it gives you the best image quality, but in lower light you can go down higher and higher until you are able to shoot (100, 200, 400, 800, 1600, 3200). I would recommend trying to stay under 1600 90% of the time. Only go to 3200 if you really need it; the image quality gets pretty bad.
Posted via web
By posterous | April 27th, 2010 in
Photography |
No Comments
Internet Explorer Six, resident of the interwebs for over 8 years, died the morning of March 1, 2010 in Mountain View, California, as a result of a workplace injury sustained at the headquarters of Google, Inc. Internet Explorer Six, known to friends and family as “IE6,” is survived by son Internet Explorer Seven, and grand-daughter Internet Explorer Eight.
Read More
By Raghu | February 24th, 2010 in
Funny,
Random Websites |
No Comments
With basic HTML tables, the structure and the way the table are presented inherits the native html style. And if you like to change it then you need to change the underlying HTML code or spend time in adding attributes to all tables tags, in order to style it with CSS . But what if you want to make the tables more interesting, more dynamic, more visual appealing without spending so much time. Yes you can certainly use JavaScript for this, but coding it from scratch will be time consuming and it’s not worth. But JS libraries/frameworks will allow you to add a range of dynamic behavior to your tables and manipulate it for better presentation on a webpage without spending much time. We decided to list a few for the benefit of those who intend to use tables with JavaScript(JS). Most of these are for the popular jQuery, MooTools and Prototype/script.aculo.us JS frameworks. Since most of the JS frameworks mentioned below are plug-ins that work on top of existing JS frameworks, it is recommended that you take a look at those base frameworks first. But there are a few others that do not require an existing JS frameworks.
Read more
By Mikhail Esteves | January 5th, 2010 in
Links |
No Comments
Client-side optimization is getting a lot of attention lately, but some of its basic aspects seem to go unnoticed. If you look carefully at pages on the web (even those that are supposed to be highly optimized), it’s easy to spot a good amount of redundancies, and inefficient or archaic structures in their markup. All this baggage adds extra weight to pages that are supposed to be as light as possible.
The reason to keep documents clean is not so much about faster load times, as it is about having a solid and robust foundation to build upon. Clean markup means better accessibility, easier maintenance, and good search engine visibility. Smaller size is just a property of clean documents, and another reason to keep them this way.
In this post, we’ll take a look at HTML optimization: removing some of the common markup smells; reducing document size by getting rid of redundant structures, and employing minification techniques. We’ll look at currently available minification tools, and analyze what they do wrong and right. We’ll also talk about what can be done in a future.
Read more
By Mikhail Esteves | January 4th, 2010 in
General |
No Comments
There are three questions you have when you’re hiring a programmer (or anyone, for that matter): Are they smart? Can they get stuff done? Can you work with them? Someone who’s smart but doesn’t get stuff done should be your friend, not your employee. You can talk your problems over with them while they procrastinate on their actual job. Someone who gets stuff done but isn’t smart is inefficient: non-smart people get stuff done by doing it the hard way and working with them is slow and frustrating. Someone you can’t work with, you can’t work with.
The traditional programmer hiring process consists of: a) reading a resume, b) asking some hard questions on the phone, and c) giving them a programming problem in person. I think this is a terrible system for hiring people. You learn very little from a resume and people get real nervous when you ask them tough questions in an interview. Programming isn’t typically a job done under pressure, so seeing how people perform when nervous is pretty useless. And the interview questions usually asked seem chosen just to be cruel. I think I’m a pretty good programmer, but I’ve never passed one of these interviews and I doubt I ever could.
Read more
By Mikhail Esteves | December 5th, 2009 in
General |
No Comments
