Related Content
 |
Make Better Software by Learning from Your Mistakes If you accept that it’s OK to make the same mistakes over and over, you’ll never give yourself the opportunity to grow. If you don’t grow, you won’t improve your software. A writer should always ask why an editor did what he did, and a developer should understand how he can fix the code he broke. |
|
 |
Dealing with Chronic Complainers in the Workplace At work, you don’t always have the option to steer clear of chronic complainers. If you're kind (and patient), you can listen and empathize. But if that doesn't sound appealing, there are other options. Read on to learn some suggestions for deferring and discouraging complaining coworkers. |
|
 |
Navigating the Culture of Global Organizations Many companies have very strong cultures and expect employees to embrace their values and view of the world. That can be difficult enough in familiar cultures, but in today's connected world, you may interact with colleagues all over the globe. Understanding their norms and communication styles is essential. |
|
 |
IoT Security Concerns for Quality Assurance Teams In addition to the typical Internet-related security concerns, applications are being made specifically for IoT devices, all of which bring about additional security concerns that quality assurance teams need to consider. |
|
 |
Improve Your Software Organization’s Processes: Focus on the Right Thing While processes may seem like overhead, you need defined, documented procedures to avoid problems. It's when processes exist just because "we've always done it that way" that they become a problem. Keep processes useful by asking questions and constantly verifying that the purpose behind them is relevant. |
|
 |
Finding the Right Ratio of Software Testers to Developers for Your Team Many organizations struggle with finding the optimum ratio of testers to developers. Linda Hayes explains that there's no one right answer. It depends on your needs for planning, test environment and data management, requirements analysis, test design, execution, diagnosis, reporting, and defect management. |
|
 |
Why Agile Begs for Better Team Communication How do you promote effective communication among a group of individuals, especially in agile? That’s the big question. In a world where some people might even have differing definitions of the actual word “communication,” it can seem impossible to get everyone on the same page. |
|
 |
How Innovation Really Happens We tend to seek out creative ideas that will result in innovation, thinking that will bring about success. But popular theories of how innovation happens are actually wrong; more work is required than some think. There is more to innovation than just great ideas—and there is more to success than innovation. |
