Feb 182010
 

I like this article…from TechRepublic.com…

Hiring a programmer? Ask these questions in the interview | IT Leadership | TechRepublic.com: “One of the hardest things to do when hiring a software developer is to establish his or her level of expertise. It’s pretty easy to learn what their attitude is like after a bit of time in an interview. But actual programming experience is tough. Some companies rely on various tests, but in my experience, those tests often evaluate rote memorization that the modern development environment does not require (e.g., between the IDE’s autocomplete, F1, and the Internet, library knowledge is not as important as it used to be). Here are some questions that are good to ask a developer, and why they are good questions. If you don’t feel comfortable judging the answers on some of the more technical questions, have one of your senior developers sit in as well. These questions are designed to be generic and allow you to “pre-screen” a candidate before you get to questions specific to your projects.”

 Posted by at 12:38 pm
Oct 032009
 

From the Project Team Blog…

Microsoft Project Team Blog : Project 2010: Introducing the Timeline View: “Project 2010: Introducing the Timeline View

In Project 2010, we’ve added a new view called the Timeline view which allows you to easily create a high level view of your project plan that you can then share through other Office applications such as PowerPoint and Outlook.”


 Posted by at 7:32 pm
Feb 172008
 

Good reading prior to my assuming a new position where I have a sizable team of application developers.

By Joe Olson at MSDN Blogs…

Although you may not find many references to dev, test, staging, environments, these are critical to large deployments. Even in the commodity type space where you are simply hosting the out of the box SharePoint code, it still very important if not critical to have a “test” environment where you can validate that the service pack installs, and the steps you follow work, and most important of all it works with your environment. If there’s a user error in the install how much better is it that you learn it on a non critical environment. There are slight differences to all these various stages to deployment. Some more critical than others. Let me provide some insight into the differences. For the record I’m not saying every environment needs all of these, all the time, but they should be considered and incorporated into your planning at various stages. Much of these deployments can be served by virtual environments, but when it comes to perf and figuring out load balancing and some elements to clustering it is helpful to have hardware you can use. I’ve been in some environments where this is a check out process where hardware or virtual images can be allocated temporarily during that phase of the project. More and more I do expect to see environments to move to virtual, but as with anything testing is a major element and even when doing things virtually you’ll find that RAM and CPU are still important elements, so you can’t scrimp.

via Pilots, Proof of Concepts, Test, and Pre Production Environments – Joel Oleson’s Blog – SharePoint Land – Site Home – MSDN Blogs.

 Posted by at 6:42 am