Developing software seems to be non-automatable process which represents a new challenge each new time. The reasons for unpredictable quality, missing deadlines, project success or failure. Analyzing the source of the problem in-depth.
Deciding between two options of professional development. Becoming a highly skilled specialist in one particular technology or mastering a variety of techniques and tools. Benefits, tradeoffs and consequences of these paths.
Basic concepts of user interface design and usability for hardcore programmers. A first-time introduction into the matters most programmers know nothing about.
ASP.NET WebForms applications share similar architectural decisions and follow same design patterns. ASP.NET MVC brings a significant change of paradigm. Analysis of options and challenges faced with migration of these design solutions to ASP.NET MVC.
Automatically detecting the user location and displaying the localized content has become a ubiquitous practice among many sites. The user setting of preferred culture in their browser is however completely ignored. Why it is wrong and how the problem should be approached.
Team work skills are highly praised and actively taught to students. Does this really add to their professional skills or rather stops their learning process and destroys their learning abilities?
Dangers and risks of micromanagement for software projects. Its impact on deadlines, work quality, team morale and the project success. A true story about one micromanaged project.
Best programming practices and coding techniques that will help you write clean and maintainable code, reduce the potential for bugs, minimize maintenance efforts and keep high overall quality of your projects.
A great read for programmers to recognize themselves and understand their inner powers. A simple introduction for the rest of humanity to glance a look at the mystery of software creation and to understand the ways of masters.
Microsoft decided to support both VB.NET and C# in their .NET framework. Was it a smart decision or a strategic mistake? Has it reconciled and united Visual Basic and C++ developers on the common ground or rather drawn a stronger line between them?