development

Conference Presentations

Developing and Testing a Connected Bracelet for Mind and Body
Slideshow

With wristworn wearables, the stakes are higher than almost anywhere else. Not only are you competing with tech giants like Apple and Fitbit, you are competing with luxury watches and accessories for valuable real estate. Skip Orvis, COO and Head of Systems Development for Caeden, will...
Skip Orvis
Rapid Application Development for Raspberry Pi
Slideshow

The IoT explosion has driven many developers to build systems that work with single board computers such as the Raspberry Pi. Because there are not a lot of tools available for these computers, development work slows down. Today, most developers use Python, which has a steep learning...
Geoff Perlman
DevOps diagram Testers: An Integral Part of the DevOps Team

Building innovative software faster and better is imperative to an organization’s success, so it makes sense to take advantage of DevOps. But what some teams fail to consider is that testing is a crucial part of the process. Without a “test early and often” mentality, DevOps would only be able to release software faster—not better.
Renato Quedas's picture Renato Quedas
March 17, 2016
initiation, design, production path Visualizing the Complex Software Development Process

Software development is an elaborate process, so many organizations follow defined procedures. But it can be difficult to keep track of every step. It is often helpful to try to visualize the complex processes involved; seeing them outlined can help you understand what needs to be completed and how to manage the overall effort.
Bob Aiello's picture Bob Aiello
March 10, 2016
person removing a piece of the pie 6 Traits to Seek in an Outsourced Product Development Partner

Lower costs, specialized designers, and rare skills sets are among the reasons companies consider working with outsourced product developers. But there are differences between working with these vendors versus the traditional enterprise software solution vendors you may be used to. Here are six qualities to look for when making your selection.
Kaushal Amin's picture Kaushal Amin
February 25, 2016
myth vs. truth sign Fear Not: DevOps Is Not Killing the Operations Engineer

Development and operations have fundamentally different goals, so some people are wary about how they can collaborate in DevOps. With increased automation and continuous delivery, operations engineers in particular are worried their responsibilities will become obsolete. Not true! DevOps actually creates opportunities for everyone to benefit.
Anuj Kumar Sharma's picture Anuj Kumar Sharma
February 4, 2016
gap between two teams Business and Development: Working Together to Build Better Products

Business stakeholders and DevOps teams both have to take an active approach to app development, but neither faction should have to change practices and processes in order to get their needs across. Investing the time to establish communication between these teams will drive delivery of the applications customers demand.
Renato Quedas's picture Renato Quedas
January 7, 2016
Seven Guidelines for a Great Web API

Web APIs have opened up a brave new world for app collaboration. James Higginbotham presents a series of guidelines that every programmer should consider in the design and implementation of a great API developer experience.
James Higginbotham's picture James Higginbotham
January 7, 2016
arrows right 6 Steps to Bridge DevOps with Release Management in the Enterprise

Balancing time-to-market pressures with regulatory needs and business continuity demands is a challenge for highly regulated large enterprises. Automating processes and mastering proven practices of release management makes developing and releasing software predictable, reliable, and repeatable.
Greg Hughes's picture Greg Hughes
December 24, 2015
Best practice for changes to source code that are part of a solution to resolve two different Product Change Requests?

In practice I have two new features that are under change control and that I want to be able to track them as separate changes from the first change and until the features are deployed to production.
 
How do I handle the fact that they both need to make the same changes to one part of the code? If I let one of them carry the change but then decides later on to back out of that “Feature” then I  will break the other feature that where depending on the same change. 
 
I am curious to know of any good advice or best practices to use i CM when dealing with those type of scenarios. 
 
We use MS TFS as version control and status accounting tool, but I am really interested in learning about best practice in general.
 
Thanks Johan.
Johan Sundqvist's picture Johan Sundqvist
December 22, 2015

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.