Related Content
 |
The Developer’s Role in Testing and Quality Of course a developer's primary job is to produce good code, but there's also a lot they can do to contribute to quality and test their code before it gets to a tester. Code quality techniques help developers write better code, more thoroughly understand their changes, and avoid builds with many easy-to-find problems. |
|
 |
Developing Artificial Intelligence Systems for Dynamic Environments From navigating unfamiliar terrain and dangerous weather conditions to working in risky situations, AI could be of enormous aid to first responders and the military if AI systems could react appropriately when something significant and unexpected occurs, without needing to be retrained on a large data set. |
|
 |
Before Rolling Out Products, Walk a Mile in Their Shoes Beyond focus groups and surveys, different paths lead to uncovering ways to delight your customers. It is important to recognize the problems, challenges, wants, and needs of people. “Before you criticize someone, walk a mile in their shoes” is also good advice for rolling out products. |
|
 |
4 Reasons Your Company Should Hold a Developer Hackathon Hackathons, where developers meet up to do some collaborative programming, are a great venue for problem-solving and creativity. They give employees the potential to get ideas out there that could pay off big, work the bugs out of new technology, and increase morale—and, best of all, they can be held anywhere. |
|
 |
Raspberry Pi's Latest Compute Module: CM3+ They say all good things eventually come to an end. The Raspberry Pi Foundation announced the latest and last iteration of the Raspberry Pi Compute Module series: Compute Module 3+ (CM3+), designed for industrial applications and digital makers. |
|
 |
The Challenges with Open Source Software Using open source software is all the rage these days, and for good reason. Often teams don’t have the budget to purchase commercial tools, and without an open source solution, their productivity suffers. But open source is not a panacea. There are some challenges that can hit you hard if you aren’t careful. |
|
 |
Who Should Be Doing Automation Work? Testers often look at automation work as the next career step after manual testing. Automation work has more visibility at the project level, and people who do this work usually also tend to have a little more social status. But Justin Rohrman makes a case for why testers shouldn't be the ones doing automation work. |
|
 |
Keep Your Code Base Clean with Regular Refactoring The Boy Scouts have a rule: “Leave the campground cleaner than you found it.” You should apply the same principle to your code. Regular refactoring prevents code rot by keeping the code base clean and easy to maintain. Refactoring activities can be added to the product backlog as user stories to make it a discipline. |
