Lost!

I use to pride myself on being up to date, but lately, I’ve started noticing more and more that I don’t really “surf” anymore. I tend to stay on specific sites or inside my RSS feeds. Well, today, I learned about PlentyOfFish.com. For those that don’t know, it’s a free dating site. Whats interesting is that the site creator was pretty much the single employee, single coder, single everything until very recently when he hired his second employee. It gets really interesting to know how he started the site.

Markus Frind (Blog) started out in the Web bubble bust by deciding to switch from ASP to ASP.Net while hopping jobs during the downturn of the bubble. He would code in the evening since he’s more of a “learn as I go” programmer (like myself) and started hosting from his home computer and internet connection. After he saturated his DSL line, he decided to upgrade and thats the crazy part. Around this time, AdSense rolled out and he started making a few thousand dollars a month. Today, he’s making around $30,000 a day in Ad revenue from Google’s AdSense. Continue reading…

Well, it had to happen sometime. It seems NetCraft has verified that Apache is losing ground to IIS.

While Slashdot users are arguing over IIS being turned on by default or not (it’s not anymore), the real reason is that businesses are switching to .Net. If you’re a corporate web developer and you don’t have C# under your belt, you’re missing out of some serious opportunities. I’m an Open Source Developer (PHP) by night and C# by day Continue reading…

Ever go to a SharePoint website, maybe your own, and noticed that you could just about get a cup of coffee while SharePoint sits there thinking about what to do when you click on a link? Ever wonder why it does this?

Well, when you’re on a SharePoint/IIS server that isn’t used as much as it would like, it shuts down the IIS worker processes. This means that whenever you click a link on an idle server, it literally has to open up an instance of an IIS worker process to serve your page. Wanna fix this behavior?

On your portal server (either Physically or Remotely logged in) go to the IIS Manager
Open the Application Pools on the left hand side.
Right click on the DefaultAppPool and go to properties
Click the Performance Tab
Uncheck “shutdown worker processes after being idle”

*POOF* - fixed…

Now, I must mention that your web server is set by default to turn this stuff off after 20 minutes. If you’re running a SharePoint portal and its doing this, you might want to update your content, grab a few more users, etc.

This fix may cause other problems as well, like memory issues if you get slammed and it can’t close the worker processes - so be careful.