Related Content
Expanding AI for Earth in 2018 In an ambitious undertaking, Microsoft is pledging $50 million over the next five years to expand Microsoft’s AI for Earth program and put artificial intelligence technology in the hands of individuals and organizations around the world who are working to protect our planet. |
||
A Tester’s Guide to Choosing a Programming Language Many testers want to learn a programming language, but how should they decide which one? Justin Rohrman suggests finding an authentic problem to solve and moving from there to determine which language would be best. You can also ask developer coworkers for suggestions and help—take advantage of available resources. |
||
Why the Gig Economy Thrives in the World of DevOps Even if the industry is booming, it’s not easy filling the full-time DevOps roles. Every software team is vying to find the perfect person to come in and establish a culture to promote improved software release cycles, software quality, security, and rapid feedback on product development. But it's not easy. |
||
Growing Security Intelligence: DARPA Proposes Plants as Sensors The new Advanced Plant Technologies program established by DARPA, the Defense Advanced Research Projects Agency, will explore ways to use plants' natural responsiveness to their environment as a military sensor to detect and report on the presence of threats such as explosive devices or radioactivity. |
||
Think through System Changes to Anticipate Quality Issues When you replace or significantly modify components of a larger system, too frequently we focus on whether the code we are building functions correctly. This is important, but it’s also short-sighted. It’s easy to introduce errors because we are changing interactions. Coding bugs are only one quality problem. |
||
Why You Should Have an Observer on Your Project Team If your project team suffers from misunderstandings or squabbles, it may be valuable to designate an observer role. This person would sit back and pay attention to whether there are patterns of miscommunication, interruptions, or conflicts that those in the conversations may not notice, helping resolve problems. |
||
Driving Continuous Improvement to the Entire Organization In traditional agile approaches, retrospectives are valuable to team improvement. However, when teams encounter organizational issues beyond their control, such as project structure, interorganizational communication, or resources, it's more difficult. Here's how to expand continuous improvement to the whole company. |
||
Integrating Code in Agile Software Development: Start with the Goal in Mind Agile software development works because of continuous feedback at various levels, and the most important form of feedback is working software. One way to achieve rapid feedback is to integrate and deploy code frequently. Rather than starting with the process, first decide what "frequently" should mean for your team. |