Itdaily - “Manual coding is a thing of the past”: Visma makes a radical shift

“Manual coding is a thing of the past”: Visma makes a radical shift

Developer typing on a laptop, screen showing lines of program code in a dark editor.

Manual coding is the exception rather than the rule within Visma. The role of developers is changing, but at the end of the day, they remain responsible for the code.

Software development is at a crucial turning point in 2026. There are as many opinions on automated coding as there are tools for it. The Norwegian software group Visma has made a clear choice for itself: “The era of manual coding is over,” says Diana Viorica Bara, Product Development Director at Visma.

Bara has worked in software development for twenty-five years and joined Visma eighteen years ago. Since February 2025, she has held a leading role within product development. From that position, she supports companies in their AI transformation.

More than just assisting

Visma didn’t just change course on a whim. “The rollout began with practical applications where the value and impact were clear, such as code assistance, documentation, prototyping, and testing. From there, it is expanding to other layers,” says Bara.

The first phase of AI in software development was primarily about assistance. Bara: “Developers push a button and code appears. This was followed by a phase of supervision, in which humans and AI work more closely together on the same task.”

For Bara, the added value lies in the next phases: delegation and orchestration. “AI agents can handle more than a single defined task; they can manage an entire workflow. Many steps of the cycle can already be taken over by AI. The human developer remains responsible for the context and the outcome.”

Shared strategy with local autonomy

Visma has therefore made the shift internally: manual coding must be the exception, and no longer the rule. Bara sees the clearest gains in speed and productivity. “Developers no longer have to do work that is slow, repetitive, and expensive. The impact of AI is significant when applied to the right work.”

Bara gives an example from their own operations. “With AI, we managed to modernize a complex payroll system in 6 weeks with a team of 3 people, which we estimate would otherwise have taken five years. In some cases, we can already reduce human labor by 90 percent. This also allows us to roll out improvements and AI functionality for customers faster. Systems of record are evolving into systems of action: software no longer has to wait until you click.”

The Visma Group comprises more than 180 companies with their own software, customers, and IT environments. The goal is not to change who these Visma companies are, but to help them reach their full potential. “There is a shared strategy, but with local autonomy for our companies. They are free to test what works best for them. Not every product will contain the same degree of agentic AI. The goal is not just to add some AI to software, but to change the entire process.”

Software no longer has to wait until you click.

Diana Viorica Bara, Product Development Director Visma

Construction worker becomes architect

The higher degree of automation does not mean Visma is sending its software developers into early retirement. However, their role is changing from a construction worker performing the heavy lifting to an architect who designs and oversees the plans. “Humans are still needed to orchestrate the work, validate code, and set up guardrails. It’s not just about generating code, but also about understanding the context. The developer becomes an architect of outcomes,” says Bara.

At the end of the day, responsibility remains with people. According to Bara, this is crucial to guarantee code security. “AI offers opportunities as long as the right guardrails are in place. You cannot blindly trust AI code. Without guardrails, it actually accelerates errors. Adoption is not just about speed, but also about understanding where it adds value and what the risks are.”

“At Visma, we take this very seriously because we develop business-critical software. Validation is not separate from the development process. Responsibility for software lies with the teams. While the role of developers is shifting toward architecture, they must remain close to the code,” Bara clarifies.

Young developers will have to learn to deal with these changing patterns. Juniors used to gain experience primarily through manual coding, but they will now have to master automated coding. “The role of the programmer is becoming broader and more strategic. Product-oriented thinking and understanding customer needs are becoming the new standard. It’s not about whether you use AI, but how you handle it in AI-native workflows. Junior developers will have to learn that from the start. The basics remain important, but orchestration is increasingly becoming a core skill.”

Manual coding is a thing of the past

Visma is gradually making manual programming the exception. This evolution does not mean that software development is becoming fully autonomous. AI agents can perform more and more tasks and workflows, but humans must provide the context, define boundaries, and take ultimate responsibility. Especially with business software involving critical processes, this control remains necessary.

Bara summarizes the change clearly: “The era of manual code is coming to an end, and a new phase of orchestration is beginning.” For Visma, this isn’t a story about a single tool or a short-lived wave. It’s about making development teams work differently, letting products orchestrate more workflows and perform actions, and sharing knowledge faster.