Ada Lovelace Day

About The Authors

Suw Charman-Anderson

Suw Charman-Anderson

Suw Charman-Anderson is a social software consultant and writer who specialises in the use of blogs and wikis behind the firewall. With a background in journalism, publishing and web design, Suw is now one of the UK’s best known bloggers, frequently speaking at conferences and seminars.

Her personal blog is Chocolate and Vodka, and yes, she’s married to Kevin.

Email Suw

Kevin Anderson

Kevin Anderson

Kevin Anderson is a freelance journalist and digital strategist with more than a decade of experience with the BBC and the Guardian. He has been a digital journalist since 1996 with experience in radio, television, print and the web. As a journalist, he uses blogs, social networks, Web 2.0 tools and mobile technology to break news, to engage with audiences and tell the story behind the headlines in multiple media and on multiple platforms.

From 2009-2010, he was the digital research editor at The Guardian where he focused on evaluating and adapting digital innovations to support The Guardian’s world-class journalism. He joined The Guardian in September 2006 as their first blogs editor after 8 years with the BBC working across the web, television and radio. He joined the BBC in 1998 to become their first online journalist outside of the UK, working as the Washington correspondent for BBCNews.com.

And, yes, he’s married to Suw.

E-mail Kevin.

Member of the Media 2.0 Workgroup
Dark Blogs Case Study

Case Study 01 - A European Pharmaceutical Group

Find out how a large pharma company uses dark blogs (behind the firewall) to gather and disseminate competitive intelligence material.


free page hit counter



hit counter script


All content © Kevin Anderson and/or Suw Charman

Interview series:
at the FASTforward blog. Amongst them: John Hagel, David Weinberger, JP Rangaswami, Don Tapscott, and many more!

Corante Blog

Wednesday, February 21st, 2007

FOWA 07: Rasmus Lerdorf - PHP on Hormones: Application Development Using PHP

Posted by Suw Charman-Anderson

Started in 1993 with the Mosaic web browser.

Loves solving problems, but hates coding. But, like flying, one has to endure discomfort to get to interesting places.

But developing PHP was such a big job he gave a lot of it away to other people. Why do people contribute to an open source project?

- self-interest
- self-expression
- hormones, oxytocin which is ‘nature’s trust hormone’
- improve the world, has done that to some extent.

When you know you are dealing with a human on the other end, oxytocin is produced. Encouraging people to interact with each other, to trust each other, and open source is one way of interacting with people and thus producing oxytocin which makes them then feel good.

Lots of people feel like they ‘own’ PHP because they’ve put so much into it.

Relates to Web 2.0 stuff, because a lot of those sites harness network effects and get better the more people use them in a way that caters to their own self-interest. PHP is not a website, but PHP users tend to also be PHP developers.

Benefit to Lerdorf is that if other people are writing PHP then he doesn’t have to do it all. Flickr and WIkipedia would be useless without people’s contributions, and PHP is the same.

Why do users contribute to a website?

- self-interest
- self-expression
- hormones, lots of hormones on Flickr
- improve the world, not the major focus for many [although think of Wikipedia]

Two major hurdles
- Performance
- security

Performance
If you have a good idea but your site can’t handle the attention and users then it’s dead in the water. It’s easy to clone an idea so you have to out-perform your competition. Need to benchmark how fast your stuff goes. Latency needs to be 20-40ms range. Use tools like Callgrind to find out what’s going on in your application. Look at how your application actually works, what are the calls? Look at CPU load. Does it make sense how your app is using resources?

This is purely performance, not scalability. Scalability comes on top of this. You can scale but still be slow.

Security
Security on the web today is awful. There are some valid criticisms of PHP in terms of security. Should have built security into PHP in the early days, but it was hard in 1995 to know what was going to happen, the problem didn’t exist.

There are some common problems in PHP, in Apache, IE - it’s impossible to secure anything in IE6 or older. In short, the web is broken and you can all go home now. But we have to muddle on, because it’s the only one that we have.

Key problem is clicking on links. Unless you understand exactly what’s in the link you’re clicking, it’s really not safe to click on it. Relatively easy to get people to trick people into giving you their login details. Flash movies can be doing things behind the scenes that can talk to any site you’re logged into, e.g. your banking site.

Filter via PHP all content coming into Yahoo! and filter out anything that could possibly cause a problem. Sort of like a network firewall.

Machine tags geocoding photos in Flickr, can specify area and pull out all geocoded photos from that, without specifying a tag.

In conclusion
- avoid participation gimmicks, don’t pay your users to use your site
- get their oxytocin flowing
- solve one problem
- clean and intuitive UI
- APIs
- make it work

Technorati Tags: ,

Email a copy of 'FOWA 07: Rasmus Lerdorf - PHP on Hormones: Application Development Using PHP' to a friend

EMAIL THIS ENTRY TO A FRIEND



Separate multiple entries with a comma. Maximum 5 entries.



Separate multiple entries with a comma. Maximum 5 entries.





E-Mail Image Verification

Loading ... Loading ...

Comments are closed.