Visual studio feeds

All Visual Studio blogs in one place


Enter your email address:

Delivered by FeedBurner

Increase your website traffic with



Anti-spam: How many eyes has a typical person?

Follow us on FB


Ignite and St. Louis SharePoint Users Group

AddThis Social Bookmark Button
Just wanted to let you know a couple of upcoming events I'll be attending that I wanted to let you know about:   Ignite What used to be the SharePoint Conference has now morphed into Ignite, a conference that harkens back to the huge Microsoft conferences of old, when mutliple product groups all met during a single conference. Luckily, this year the conference is being held (relatively) in St. Louis's back yard, the Windy City of Chicago. I'll be working in the hands-on-labs, so
come by and say hi, and take some products for a spin. Unlike folks who visited the SharePoint Conference in the past, this is an opportunity to get hands on experience with other products such as well. There are already 135 labs posted, and this year you'll be able to BYOD, which means you'll be able to run the labs from your own device, and even from the comfort of your hotel room! How awesome is that? No more being smushed into a hot room of desktops, except that if you spend some time in the lab space, you can...(Read whole news on source site)

Q&A with Sandro Mancuso about The Software Craftsman

AddThis Social Bookmark Button
Q&A with Sandro Mancuso about The Software Craftsman

The Software Craftsman, Professionalism, Pragmatism, Pride
Sandro Mancuso explores how craftmanship plays a role in agile software
development. The book contains stories, examples and practical advice
for software developers and other professionals involved in software
projects to achieve technical excellence and customer satisfaction.

InfoQ readers can download a sample of the book "The Software Craftsman" to get an impression of this book.

Sweet Aspects

AddThis Social Bookmark Button
Originally posted on: When a module has a single responsibility that means it’s focused on producing the behavior of a single aspect. That’s how I described the Single Responsibility Principle (SRP) in my previous article. Since the SRP is so important and at the same time a bit elusive, I thought, I try to illustrate this “traits and aspects thing” a bit more. Maybe you can even develop a taste for the SRP :-) Look at this heap of sweets: Let them represent logic in your code. You know, those 5,000 lines of code in
a method, or those 200 methods in a class, or those 1000 classes in a library… It’s all the same. Unstructured stuff. High entropy. Disorder. Not clean. Yet at least ;-) At some point it might have been a good thing to throw all this together. Maybe that way delivery was faster/easier? You know all those explanation how legacy code just happened over time. Should get into technical debt very consciously; have a plan how to pay it back. But in my experience that’s not how it works for teams. Like many private households (and companies) they stumble and falter...(Read whole news on source site)