Basing on the things we have learnt so far, we can now move on to discussing the techniques of debt measuring and their use in the prioritisation, monitoring and prevention of technical debt.
Technical debt and the software entropy it brings lie beneath a lot of software making failures. Read this post to find out what technical debt is and where does it come from.
In my opinion the best known example of a company which lets their employees work on “personal” projects, is Google. This “Internet juggernaut”, encourages its engineers to take 20 percent of their time to work on a personal project, which is company-related and is of personal interest.
As the Internet matures, we abandon the classic approach whereby the user is presented with a handful of URLs which reload the page when clicked; the new approach aims to make the web application work seamlessly.
The fundamental goal behind the performance tests – it is all about the quality and the user experience delivered on the product you implement. And the key concern is the app response time your users are exposed to.
The year 2011 has ended and I think one might justifiably claim that it was a ‘year of mobile’ indeed. We are going through tough economic times and yet we can observe how smartphones, tablet devices and mobile technologies are driving the growth of world’s largest markets like the US, Europe and Asia.
