Things to look out for when building a large application, by Joshua Schachter, del.icio.us

I always keep referring to this little txt document everyday:

Learn Apache - tuning can make things a lot faster. Understand headers,
mod_rewrite (a dark art). Put a proxy in front of Apache e.g. Perlbal from
LiveJournal - one guy on a modem can suck up lots of resources otherwise.

Images off a different server, RSS from a different server.

"Save site for offline use" feature in IE is particularly nasty.

The easier the API to get in and out of, the more people will use it. There's
a long tail of smart developers. Stuff like SOAP discourages adoption. No API
key = people can play with it faster; drives attention.

More....