Welcome to the Internet.

I was going to say not possible, then I saw how old my account was. :( Thanks for making me feel old.

Not completely true, a full time employee is a very large liability these days, you want to make sure they are going to fit before adding them to payroll. I'm not so sure I would do the hire multiple knowing you can only fill one position, but I have regularly used contract-to-hire.

Agreed, I never ding someone because they have certifications, however I also don't ding people for not having certifications unless the position requires one (usually a client-facing or public facing position that requires lots of letters after their name).

You do sound like a fun guy and pretty competent, however I have to say that any firmware upgrade SOP 101 is to have a copy of the current firmware available if something bad happens. It shouldn't be luck that you have a rollback plan for any type of upgrade.

That's not a very useful executive. At the point it has been proven to be outside of your control it is time to get the customer support team working with the client to help them talk to their ISP and provide as much information as possible so that they can tell the ISP what is wrong. This accomplishes the task of letting the client know that it is not related to your service. It also lets them know that even though it isn't your problem you are willing to help in any way you can.

If he/she just keeps yelling at a tech that can't solve the problem, you have a leadership problem that needs resolving.

Yelling is almost never useful, back when I was a manager or director I would let the executive know that we are working on it and let us do the job they pay us to do. I also found it helpful that if you are having a vendor issue, let the executive send an e-mail stating it is an urgent matter to your contact, this lets the executive be a hero and gives the vendor bargaining power to escalate the issue to their upper management.

During an incident the leadership should be maintaining calm so that the people doing the work are at their peak performance.

Odd timing, the laws just changed for HIPAA and HITECH

If each thread allocates its own memory then it is just returning to LWP, which was good a while back, but threading should try to avoid allocating its own memory except in a few specific instances.

However, based on this thread most people don't know how CPUs work.

Yes, most modern programmers do think that way based on most of the code I've seen in the past 10 years.

There are very few developers left in the US that even know what memory management is.

People don't even try anymore.

Nope, simple facts. The worst part is that it is a basic logic debate, the only reason HFCS is used in the USA (and almost nowhere else) is that we lobby for corn farmers.

Spend an hour doing research. Yes, it ends up the same, but sugar requires the body to WORK to get those calories (net calories is lower).

http://community.bamboosolutions.com/blogs/sharepoint-price-calculator/default.aspx

I ran my internal numbers of different divisions (very large company) and it was almost exactly right each time, so the math seems correct.

2010 is getting a bit worse (more expensive, but less complicated).

The worst is if you want to host Sharepoint on the Internet.

This has been an easy sell to the CEO/CTO types for years, it is the reason for all the 4GL languages that let you "build applications without developers".

Businesses don't like Development, they don't understand it, can't measure it well (except highly developed CMM shops) and the developers are "expensive".

To business, development is a huge overhead they have been trying to get rid of for years, and Microsoft is providing them with yet another way to try to do that.

Microsoft knows a lot of businesses don't understand development and have been playing on that ignorance since the creation of VB.