It's much better, quicker and more functional than VS2010. Pity its so fugly. Here's my +1 for VS2014 interface being touch only :zzz:

The mobile environment is ideal for the consumer model where the application consumes data but does little with it other than display it to the user. For me the tablet and smart phone are simply extensions of the PC platform. No mobile device can capture the requirements for Power Users or developers. Imaging developing an application on a touch screen without a keyboard or mouse or being an administrator of an application and entering data via said touchscreen. It simply doesn't make sense. The tablet model is here to stay and line of business applications to provide reporting to managers etc,etc is ideal but that's as far as it goes. In my business the only people with tablets are the business directory who use them to consume data (as well as being a fashion accessory)

This one has it beat.

About 10 years ago I got a call from an external client to the software company I was working for as a developer asking me to turn down the dialing screeches of the dial up modem next to him... A week later he phoned me asking how to open Windows Explorer... No I'm not kidding. :laugh:

If it was that intelligent it would write itself :-D

Agree completely, the more you achieve the more you are expected to achieve. My first development roll we were doing 100+ hour weeks for about 2 years :zzz: The quality of the code in that business was poor to say the best and costed the company much more to rectify the issue. I pretty much work 8 hours a day now and never find myself in the same situation, its also made me a much better developer as you think about how you do things rather than just knocking code out to get something done. Increasing hours is all about diminishing returns...

I agree with what you are saying but do degree level courses still discuss low level memory management? Its been a while since I was in education :-D I do understand the benifit from understanding how a computer processes tasks but in the world of 4th generation languages and garbage collection I would imagine that most day to day developers rarely use it. What I believe college will help in is when cross skilling into new platforms or technologies a person with a degree should be able to understand the underlying concepts more quickly and avoid some of the obvious gotcha's that I personnally may fall into. In the end what makes a good developer? In my experience its the drive to become a good developer and the willingness to admit they don't know everything.

I thought pi was something you eat with cream :)

Again, I believe it depends on the individual. I have experience with graduates that wrote bad, poorly performing code where we had to re-educate them quickly and of the otherside where graduates were already there writing exceptional production ready code. I don't believe that a degree makes a good developer or even the ability to become a good developer. Its the person and the personal drive to improve that shows through. I am basically self taught and have to admit when I started professionally I had to learn on my feet which is not ideal but does give a developer an understanding of what makes the customer tick. Some developers never get this.

To be honest I have limited formal education within IT areas and I have been doing this for 13 years. I don't doubt that a college education gives people what they need to get a foot in the door but in my experience you have to knock graduates into shape and teach them real world skill. Education skills != Real life programming ability

At 14 at the moment at various states in the life cycle :((