Related Content
Dealing with a Coworker You Can't Stand If you worked with someone years ago who was highly unlikable, it’s natural to assume that the person is just as unappealing now. If circumstances bring you together again, it’s unlikely you’ll find the person tolerable. You might as well expect the worst because once a jerk, always a jerk, right? Not necessarily. |
||
It's Time to Be Cautiously Optimistic about Artificial Intelligence Artificial intelligence (AI) is an ongoing trend today. However, the picture is not all rosy—even for the insiders who are heavily invested in this space. They are being cautiously optimistic about the potential it holds and the potential adverse impact if the threshold is exceeded. |
||
How to Deal with Crabby Coworkers We've all had to deal with crabby coworkers—the people who have good technical skills but are a pain to work with. They grouse, gripe, and are generally negative. Luckily, there are more things you can do than just hope you don't have to interact with these people. Here are tips for dealing with your crabby coworkers. |
||
The Normalization of Deviance Could Be Hurting Your Team Normalization of deviance refers to becoming blasé about counterproductive behavior or activities. The concept applies to processes that become ingrained in a team even though they contribute to negative outcomes, such as slipping deadlines. Employees become so accustomed to the deviance that, to them, it seems normal. |
||
Testing the Tester: Building a High-Impact QA Team Teams don’t always understand the impact their roles have on the business outcome, so their lack of focus can affect software quality and lead to an array of disasters. You can help your existing testers become a high-performing QA team focused on goals. Here’s what you can do to transform how your QA team functions. |
||
Mob Programming: Working Well Together Mob programming is a whole-team approach to creating software where everyone works together on the same thing at the same computer. It's not a bunch of people watching one person write code, but rather everyone thinking, discussing, designing, and collaborating. Sound crazy? Here's how it improves the quality of code. |
||
Thinking Inside the Box before Venturing Outside It In their rush to solve a problem, teams often overlook conventional methods in favor of out-of-the-box ideas. But sometimes, the old standbys—thinking first, reviewing criteria, and asking questions—work the best. Before jumping to creative tactics, start by examining the possibilities readily available inside the box. |
||
Analyzing the Software Team Generalist There's a recent trend in having generalists on the software team—there are no developers or testers, only "team members." The idea of the two roles learning from each other is a good one, but it's usually a one-way street: Testers learn to write production code or test tooling, but no one focuses on deep testing. |