Related Content
3 Critical Considerations for Technical Due Diligence Technical due diligence is the process of verifying a company’s technical capabilities, quality, and processes. It is typically performed by investors or buyers before a contract. There are many aspects you can investigate, but three are crucial: a code review, security evaluation, and open source components compliance. |
||
Evaluating Team Health in Agile and DevOps The importance of the human element in delivering great software is sometimes overlooked, as is the relationship between team health and team performance. Just like physical health checks, team checkups are important. Let's look at some factors that can affect team health and how you can evaluate the important metrics. |
||
Immunizing Your Software against a Defect Pandemic When your released software is infected with problems, there is the possibility of a pandemic defect, when a wide geographic area and an exceptionally high proportion of the end-user population is affected. Just like with the coronavirus, following proper guidelines and taking mitigation steps can reduce the spread. |
||
Comparing Java and Ruby Java and Ruby are both open source languages, and both are ranked in the top 20 of the TIOBE index for most popular programming languages. If you want to learn a new language and are trying to decide between these two, let’s explore common differences in syntax and constructs to discover which may be more useful for you. |
||
Making the Most of Your DevOps: A Slack Takeover with Gene Gotimer Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Gene Gotimer, a senior architect at Coveros, hosted this Slack takeover and discussed all things DevOps, including whether you can have DevOps without agile and how you can reap all its benefits. |
||
3 Ways Leaders Can Change a Blame Culture If your organization has a blame culture, team members get discouraged and mistrust leaders. It focuses on pointing fingers, not coming up with solutions to move forward. To increase trust, inspire creativity, and nurture a generative culture with your team, here are three things leaders can do instead of placing blame. |
||
The Layers in the Test Automation Journey Test automation is not just a bunch of automated scripts to be written and handed off. The scripting process, though important, is just an inner layer embedded deep within the whole. There are several more layers that are important in showcasing the true value of the automated scripts. You need to understand all layers. |
||
Making a Game out of Building an Amazing Team Games are a cost-effective and efficient way to evaluate, assess, and thus hire people with the right expertise and aptitude. It is an equally practical and powerful way to continue to develop and improve the team and individual team members. Try using games to improve your efforts to build and maintain an outstanding team. |