lrobb

My point, which was apparently lost, is that the underlying implementation of these structures is the same in PHP.

"Put it all together and I think we all now see the fundamental utility of LinkedIn — it’s the one place where you can demonstrate how honest, decent and accomplished you are, even if you have to lie and cheat to do it." http://www.creators.com/lifestylefeatures/humor/work-daze/li...

Introducing facebook background searches! For a low fee of $2499, fb will comb through your prospective employee's postings and alert you of any trouble spots!

From the site: Please note that Flourish has undergone a good deal of real-world testing, and can generally be considered production ready.

I'm reminded of this great presentation by the mule design guy (NSFW) F*ck you, pay me: http://vimeo.com/22053820

While I don't doubt your good intentions... Isn't the fact that WikiPedia is a 501(c)3 and you have outside influences a rather large difference?

*you

So you're really only putting in an extra 30 minutes per day... Minus the dinner you eat...

I'm going to go out on a limb and say you're probably not the target audience the poster had in mind.

I'm looking at implementing this for a new site...

Here's apache tuned to serve static files of 50kb in length, with 20 requests per client, 500 uniques per hour...

vs.

Here's apache tuned to serve a wordpress blog that gets 500 uniques per hour and each client makes 50 requests (average time on site is 5 minutes)...

and then...

apache serving wordpress on a VPS vs apache serving wordpress on a single core vs apache serving wordpress on a quad-core..

and oh-wait... if we're talking php then let's consider prefork/FastCGI/yada yada yada

The "problem" (or as I prefer to look at it: feature) with Apache, is that it's been around for so long, that it can accommodate all of the above specific issues.

Apache can be tweaked in so many different ways depending on what your traffic patterns look like, and how you're processing your requests. MaxClients / KeepAlive / MaxRequestsPerChild / etc...

e.g. you would have a completely different config for serving wordpress vs static images for a photo album.

"Making a major horizontal product that’s useful in any walk of life is almost impossible to pull off. You can’t charge very much, because you’re competing with other horizontal products that can amortize their development costs across a huge number of users. It’s high risk, high reward: not suitable for a young bootstrapped startup, but not a bad idea for a second or third product from a mature and stable company like Fog Creek."

I've noticed a big difference in interviews between software companies vs. internal IT departments. IT departments tend to favor how much product knowledge you have. So they think a senior person should know what's new in sql-server 2005 vs 2000... or be able to rattle off the differences between all of the various ways to store date/time.

Software companies, on the other hand, care more about how you think and design things, and what you've built. Design an algorithm to do "X"... Make "X" scale... etc... I saw you built "X"... How did you do it?

I put down that I had used C# on a resume... My first experience with it was writing a server that monitored a directory for alerts, then did some processing on the alerts, and routed them to various other 3rd party boxes... I used the file notification, threadpool, and http client libs, wpf... I subsequently used it for some Project Euler problems.

Do I "know" C#? Well... After a couple of interviews full of questions such as "explain what a delegate is... what a mutable class is... explain IOC..." I would have to say no, I don't really know C#.

That hasn't kept me from using it to bring in hundreds of thousands in revenue.

I made the decision to focus on low level C++ / Windows right around the time tcl/aolserver was cutting edge.

I think my career advice for younger programmers is to stay away from whatever technologies I'm using.

And then... An error occurred while trying to retrieve your Twitter username. Please try again.

Not me... We work with a bunch of troglodytes...

I've worked in a place where I could locate the female programmer by where the flock of nerds were hovering.

I worked telecom billing about 10 years ago... Our system consisted of a couple dozen fairly large C++ programs, and numerous DBF tables.

This system was originally written in Clipper(1), which IIRC defines numeric as an 18 digit text field. Well, when that particular program got ported to C++, the author simply used a 32-bit int in place of NUMERIC... Which needless to say worked just fine up until we started getting clients that had values larger than 2^31-1 for that field.

The scary part, is that it would just overflow, so you wouldn't get any errors... It wasn't until some guy in ops noticed a number that just seemed a little too odd.

1: Serendipity: The founder was a medical student that happened to know clipper, that happened to have a friend that had just started a telecom company and needed a billing solution (right after the Bell breakup).

Right now it's "harmless"... But people get a lot more personal in email or google searches than they do on, say, facebook.

There's some gold to be mined in there.

I wonder what the survival rate is after being dry-humped by Scoble?

Eventually, as it happens in all public companies, the "do no evil" people are going to be out, and the "maximize the buck" people are going to be in.