development
Articles
 |
The Value of Test-Driven Development when Writing Changeable Code Writing changeable code makes it easier and more cost-effective to add features to existing software. Writing changeable code doesn’t take longer, but it does require paying attention to certain things when building a system. It's important to have a good suite of unit tests that support refactoring code when needed, and test-driven development helps you create independently testable code. |
|
 |
I, Project Manager: Meet the Future of AI Software Delivery
Slideshow
[video:https://www.youtube.com/watch?v=nIuO9-eODZs&feature=youtu.be width:300 height:200 align:right] |
Rachel Burger
|
 |
The Impact of Agile Quantified
Slideshow
For years, people have made recommendations for how to develop software in an agile way based almost entirely on intuition, folklore, and anecdotes. They've never been able to quantitatively show the accuracy or applicability of these recommendations. This session quantifies those recommendations in the most precise and objective terms, including a presentation of general findings in Larry Maccherone's research correlating agile practices to performance along the dimensions of productivity, predictability, quality, and time to market. These data can be used to make general decisions about what to focus on. The presentation also includes the numbers, so that instead of just saying that A is better than B, we can say that A is a 24 percent improvement in quality but a 10 percent reduction in productivity compared to B. |
Larry Maccherone
|
 |
Overcoming Test-Driven Damage
Slideshow
Test-driven development is supposed to help us refactor our code safely, but we often find that when we refactor our code, we also have to refactor our tests. What was supposed to add safety becomes a burden requiring time and effort. Writing good unit tests is a critical skill that developers need to master in order to get the most benefit from test-driven development. Tests must be unique, written at the right level of abstraction, and implementation-independent in order to be most valuable. In this session, David Bernstein will cover effective techniques for doing TDD that support building useful tests and quality code. You’ll learn how to approach TDD in a way that yields the right number and kind of tests to support improved refactoring. Working through a few code examples, you’ll see how many assertions are required to specify a linear range, exceptions, and other boundary conditions. |
David Bernstein
|
 |
Liquibase: An Open Source Version Control Tool for Your Database
Slideshow
[video:https://youtu.be/L63U-B2mdf0 width:300 height:200 align:right] |
Blaine Carter
|
 |
Strategies for Selecting the Right Open Source Framework for Cross-Browser Testing
Slideshow
[video:https://www.youtube.com/watch?v=-M9uWjd4WJY&feature=youtu.be width:300 height:200 align:right] |
Eran Kinsbruner
|
 |
DevOps Tools for Winning Agility
Slideshow
With a myriad of tools to choose from—open source, free, paid, and enterprise level—teams and organizations have seemingly endless options. Making the right tool decisions can impact the level of quality and success within DevOps projects. Kellyn Pot'Vin-Gorman discusses different tools, what tools work best together, and how—even in teams that are in silos—the right choices can make the difference between success and failure in DevOps implementations. Explore tools—such as Ansible, Jenkins, Maven, Delphix, Github, Liquibase, and Terraform—for automating builds and virtualization. Review reasons for choosing open source, “freemium,” or enterprise tools along with different hybrid tool combinations and explore why companies face new challenges as DevOps tools mature. |
Kellyn Pot'Vin-Gorman
|
 |
Use DevOps Principles to Transform Culture
Slideshow
[video:https://youtu.be/EfT_wfBNurs width:300 height:200 align:right] |
Ashley Hunsberger
|
 |
Fitting Technical Writing into Agile Development As teams strive to move to a mature agile process, technical writers must adapt as effectively as the development personnel. This new agile process demands that knowledge dealing with software or product releases is only sparingly documented up front, making the technical writer's job of gathering information much more dependent on talking with people over reading requirements. |
|
 |
Document Why as Well as What: Finding the Purpose of Your Software Code can express what we want to accomplish, but it’s a little more difficult to express why we’re doing something in the first place. The people who maintain code are often not those who originally wrote it, so documenting why helps set a context and gives clues as to what the author was thinking when they came up with a particular design, making developers' jobs easier. |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.