| Thoughts on Microsoft's Recent Organizational Restructuring | By Michael K. Campbell
| | I don't pay enough attention to Microsoft's place in the market or its internal structure to really be a pundit. Sure, I read various op-ed pieces here and there and have seen enough information about the IT market to know that we're in the midst of a sea change. But I don't hold myself as being wise or astute enough to have opinions that carry much weight. I also think that pundits who have long been claiming the death of Microsoft just don't know what billions in the bank can do for a company. More importantly, I don't think Microsoft will ever simply die or become irrelevant; instead, I think Microsoft will become less and less of an industry leader while gradually remaining an insanely viable and powerful company, such as IBM. But in the end, I think Ballmer needs to go. To read the rest of the article, click here. Related: "Microsoft's Surface RT is Shaping Up to be a Train Wreck"
| | | | ADVERTISEMENT | |
Follow us Twitter! Don't miss real-time updates on articles, virtual events, white papers, Essential Guides, webcasts, and more. Meet your peers and tell us what you think. Also look for us on Facebook and LinkedIn.
| | | | | | WinRT vs. .NET Application Development | By Danny Warren
| | The release of Windows 8 brought with it a new software framework: Windows Runtime (WinRT). Although the approach used for WinRT application development mimics how development in .NET Framework works from a code standpoint, there are crucial differences between app development in WinRT and in .NET.
To build applications optimally under WinRT, developers need to understand the differences between WinRT app development and traditional .NET development on the desktop. Here I will outline six essential areas of difference that .NET developers should understand in order to transition successfully into building apps in WinRT. To read the rest of the article, click here. Related: "Developing Windows 8 Applications"
| | Agile/Scrum Development with Team Foundation Server 2010 | By Brian Minisi
| | The agile software development methodology supports quickly adapting a project to changing business realities. This alternative approach to the traditional waterfall software development paradigm emphasizes communication and collaboration in building functioning software in an unpredictable environment. Scrum is a subset of agile in which the software development team decides how the project will proceed. In Scrum, no details are given on how to manage a project; instead, the team decides this as the project evolves. For this reason, Scrum is not a methodology or a process; rather it is a framework.
Visual Studio Team Foundation Server (TFS) 2010 is an enterprise-level solution for managing software projects in both agile and Scrum. TFS provides the tools to project-manage, track work through work items and have full traceability from requirements down to code. Entering work items in TFS stores metrics that enable a development team to monitor the health of the project through reports. Part of a team's usage of TFS involves deciding which project type to use. This decision depends on a number of factors, including the challenges that software projects are experiencing, the resources available, and the organization's culture.
The goal of this article is to provide a high-level overview of Scrum and agile and to detail what TFS offers in the areas of project management, work-item tracking, metrics capture, and reporting. This information can help you choose which development methodology/framework to use in your organization. To read the rest of the article, click here. Related: "Visual Studio 2013 Emphasizes Agile Development & DevOps Collaboration"
| | Dev Pro Tech Talk | In this week's Dev Pro Tech Talk, we're highlighting a reader comment from Tim Huckaby's article, "Thoughts on Microsoft Build 2013 and the Worldwide Partner Conference."
Responding to Tim's thoughts, reader neaflow says:
"I don't quite understand the reference you made to apologizing for Silverlight confusion? I thought true leaders do fix the problem once it is acknowledged. But these people ONLY apologize and leave Silverlight die! That's cynical and plain stupid ... Silverlight doesn't hurt win8 ecosystem in any way. I can't develop win8 apps for enterprise because the UI is limited, is directed clearly to home consumers who only tap couple of times in an app and then close it."
Neaflow says a lot more, and Tim Huckaby also responds to the reader's comment. So be sure to check out the article for the full conversation. Do you think Microsoft's apology was genuine during the keynote at Build?
As always, please continue to share your thoughts on Facebook, Twitter, Google+, and LinkedIn! As I mentioned last week, Dev Pro is now on LinkedIn, so please give us a follow for more great development tips and tricks. Look for an article on best UX considerations for Windows 8 development. Hope to see you there!
Blair Greenwood, assistant editor
| | |
No comments:
Post a Comment