Snap! And just like that, COVID-19 has made telecommuting the new (if temporary) norm for software developers - and almost everyone else. For many software developers, telecommuting regularly is not a new concept. But remote work to this extent is still an exception to the rule. Some companies take pride in offering flexible work arrangements and conditions. It’s never been allowed, or mandated, for everyone all at once. Extra attention to a few things can help cut the disruption working from home has on your workflow.
How much time does your software development team spend on manual and automated software testing? Ten percent? Twenty-five? More? A number of recent studies (by Tidelift, The New Stack, Practitest and Tech Republic) indicate nearly 62% of software developers spend less than half of their time coding. That can be attributed to a lot of factors, but software testing is definitely one of the big ones. Clients value solutions to their problems. But is there enough time left for software developers to code and create these solutions, if testing consumes such a large portion of their time? Testing is essential to ensure code quality, but finding the line when you have enough time for both is challenging. This is especially the case when you feel the urge to finish the code as speed is a key success factor in this competitive environment.
Some estimates indicate there’s an average of $1 million of technical debt for each business application that’s been deployed to production. That’s pretty scary. So, to follow up on Pay off your technical debt like debt like a Git analytics pro, we want to provide you tips on how to avoid it in the first place. This requires breaking it down into three different types of technical debt - planned, unplanned and inevitable. Managing each type of technical debt can help you avoid it piling up and its potentially catastrophic consequences.
Technical debt stifles software development productivity, causes developers to quit, deadlines to be missed, and it is inevitable. As there’s no way around it, you and your mighty team of software developers must work through it, pay it down, and constantly keep an eye on it. Technical debt is accrued in different ways with planned, unplanned and inevitable forms requiring a wide range of controls like Git analytics. But, how do you know if technical debt is already out of control, and more importantly, how can you get rid of it? Rest easy, the insight you’ll gain here will will help you pay that debt down.
Dear Friends and Users,
We are extremely happy to announce some important enhancements in the growth and development of Gitential with the start of 2020!