Study: The 4 software program development traits with a purpose to dominate 2019

Enterprise software company Atlassian has released a survey of software builders, revealing a converting panorama in the cutting-edge world of software program development.

The seeds of this variation can be discovered in new priorities that builders say they’ve: “Modern software teams are actually shifting their focus far from the traditional measurements of pace, speed, and efficiency in favor of dreams around increasing customer satisfaction and fine code,” said Sean Regan, Atlassian’s head of boom for software teams, in a blog submit.

SEE: System update coverage template download (Tech Pro Research)

In order to accomplish those goals, the survey located, developers are turning to four strategies which are in all likelihood to be developing tendencies within the improvement world.
Microservices may be the brand new normal

Some say microservices are overhyped, however, it really is no longer stopping developers from falling in love with them.

71% of survey respondents who use microservices said microservices make testing and deployment of recent code less difficult.

Monolithic code, Regan stated within the post, could make non-stop delivery hard due to errors due to feature integration, pass-group code conflicts, and more. Expect microservices to maintain trending upward in 2019.
Expect more automated trying out

Continuous integration and continuous shipping (CI/CD) is a warm DevOps buzzword: It quantities to the practices of making frequent, remarkable releases with a view to meet patron needs.

That CI/CD requires automated checking out is not a brand new opinion, and the surveys locating helps that—sixty-two % stated that guide checking out is a drain on assets that ends in behind schedule software program releases.

Some 57% stated computerized CI/CD made each their release and comments schedules quicker; expect that range to develop in 2019 as greater development groups start automating their trying out, the report stated.
Feature flagging will make real-world testing simpler

Feature flagging—the practice of setting a toggle in software that allows builders to enable new features for a subset of customers—was a popular approach for respondents. The majority (sixty-three %) suggested better testing of recent capabilities and higher satisfactory releases, which is the right news for developers and users alike.

Feature flagging isn’t always a new concept and has been a nice exercise in cellular app development for a while. The year 2019 may additionally see wider adoption of this practice on developer teams that want to lessen insects and delays in the launch.

A cultural shift in measuring fulfillment

Atlassian located that ninety-three % of developers had been greater concerned with customer delight than something else, but Regan referred to that software program teams lack the approach to degree achievement in that manner because “of a long history of measuring work by using the output, now not purchaser outcomes.”

Building software that makes clients happy calls for a shift to final results-pushed improvement, which shifts the focal point of success far from the velocity of improvement cycles and in the direction of personal satisfaction.

75% of builders surveyed said their teams have issues with bugs and code defects at release, something that an final results-pushed subculture ought to resolve.

Software builders that want to be successful in 2019 have to recognize Atlassian’s findings for what they’re: A name to the motion not handiest in terms of recent developments and strategies of building code, however additionally a name to reconsider the subculture surrounding updates and releases.

In 2019, developers have to reduce their code, allow computers do the testing, roll out new features to a subset of customers, and measure success no longer in phrases of speed but in terms of the way easy a launch is.
The big takeaways for tech leaders:

Three new traits in software program development will see a rise in 2019: Microservices, automated trying out, and characteristic flagging. — Atlassian, 2019
In order for those new methods to achieve success, a shift away from improvement speed as a metric of success is wanted, with developers alternatively being measured primarily based at the consequences and customer delight. — Atlassian, 2019