Software developers should be thrilled with the potential this year. The introduction of modern tools, innovations, and frameworks will provide opportunities for greater efficiency and more fun as a programmer in 2023.
Yoav Abrahami, chief architect at Wix Code and head of Velo, discussed with TechNewsWorld why he sees such great potential for 2023.
“I see the best year yet but can’t guarantee there won’t be better years ahead,” he said. “I think a lot of exciting things are changing in the world in the way we code.”
To that end, Abrahami credits a few things for coming together. There has been a long-standing trend of moving to major platforms that continues in full force. Another innovation is taking place by including designers as part of the developer team. He said that it is important to bridge the gap between the designer and the developer.
6 developer predictions for 2023
Looking ahead through his software developer eyes, Abraham sees a great year to be a developer. Here are his six predictions for what to expect:
- Developers will be able to tackle more complex projects at scale.
- Collaboration between developers and designers will be more effective and inspiring.
- The cloud platform and low-code tools will integrate, introducing a range of new products including websites, web apps and mobile apps.
- The move to more managed environments will continue, offering new and better-managed services.
- AI will clean up the code and free up developers for more creative work.
- Dev talent will be more decentralized than ever, which translates into greater diversity and wider-reaching end products.
If predictions have a compelling force Why? And how Read on for Abrahami’s in-depth explanations of his vision for you, the developer community.
DevOps closes the gap
This history of the developer community is marked by ongoing friction between “systems people” and software developers. Too often developers shipped software that failed to meet expectations, and then it was the system people’s job to make it work, which led to more friction.
“We resolved that friction by introducing the idea of DevOps. This shifted the responsibility for failure due to system changes back to the developers becoming a team,” observed Abrahami.
He suggested that another approach that is helping to foster better opportunities for developers is to keep both elements within the same working environment. His company follows this method of team building for software development.
Wix’s solution: let the designer take responsibility for the design and create a team that includes both a designer and a developer. Everyone involved gets the same equipment.
“In the same environment, the designer designs the UI, and the developers write the code to work with the UI. The reality is that 99.9% of teams will opt for more modern tools, as happened with DevOps – and this revolution It is happening now, and we see that simply because projects are being sent at a velocity that we never imagined. It is so amazing to see,” he said.
Digging Deeper into the Developer Environment
With this Q&A my conversation with Yoav Abrahami continues.
TechNewsWorld: What makes it possible for devs to tackle more complex projects at scale?
Yoav Abrahami: No one brought into the team is opposed to developers and designers working together. This means you can work much faster and be more productive. But more than that, we will continue to move towards more managed environments. This means that you are going to be much more efficient in terms of all your software.
What’s changing in the developer community?
Abrahami: You must remember what managed software really is. It’s always a trade off. You’re trading your freedom to choose, such as which service works right now.
Years ago, you would be working on your own machines, and you would choose your OS. Today you don’t even do that. Years ago, you would build servers and try to figure out which framework to use. Today, you can use multiple lists, and you don’t really care what’s happening below them.
Looking at what we have today, we are taking another step forward. You don’t even choose your front-end framework. We provide you an out-of-the-box solution where your ID, development environment, database, back end and front end all work together.
How widespread is this innovation? Is Wix in the minority with these viewpoints?
Abrahami: We are not the only ones doing this. This is happening across the industry. You can see more and more solutions with online development environments with zero configuration of the platform required.
To understand what I’m talking about, consider how long it would take to build a call center where thousands of volunteers can sign in, go through the process of verifying who they are, and then Be able to call people to ask if they need help with medicine or food or anything during covid. It will probably take months, even two years, to become normal.
We made one in two weeks. Within a month, we had 700 volunteers using that system. It used Twilio for telephony, a ready-made solution available for the UI for two separate applications. That’s where we’re moving very quickly.
I would say that if today you are struggling to make products for months, then you are doing something wrong.
How much of an impact is using cloud platforms and low-code/no-code tools?
Abrahami: The idea of low-code is to make it very fast in the context of what you’re building. You don’t need to write all the code and bring it to the main platform. You just add a little bit, a few lines of code here and there – and we have a solution.
But then again, even less code can fail when you want to do something, like comparing 600 steps of coding, and you want to change something. How do you test this? How do you test that change? How do you know the effect? How do you see the changes between one version and another?
How does artificial intelligence factor into what’s happening now within the dev community?
Abrahami: To be honest, no one knows. But we know it’s going to disrupt everything. This is the reality.
Let’s say you ask the best AI to write code for you, and that code is a piece of software to drive your train. Who do you blame when a train crashes due to a bug? Is it AI’s fault? Is it the AI vendor’s fault? Is it the fault of the person who wrote the code with the bug the AI trained?
All of those questions lead to one big issue: How will it work? We don’t know! But we do recognize that AI coding has potential.
Do you have hope for AI as a benevolent tool for developers?
Abrahami: I see huge potential in AI. We look at quality, and quality has two things we don’t know how to measure. We don’t know how to measure usability, and we don’t know how to measure correctness. Now, AI may be able to give us the answer there, and I may be able to create an AI that will give me that.
Where do you see all this potential heading?
Abrahami: Think utility for Application Programming Interface (API). This is much easier to do than to measure whether it can attempt to write code that solves your next big problem. Now, this is just one example. Another example you can think of involves AI.
When should I increase, or when should I decrease? When should I do failover? When should I stop a service because it causes problems for other services? And so on.
Maybe all those things can be automated using AI. Automating can prevent shipping faulty software through early bug detection. So many possibilities exist. There are a lot of things we can do with AI today to change the way we work as developers. The things we trust about AI, like the tools to help you do what you’re doing.
Another example is semantic search. Too often, you move into a category, especially in larger organizations. You’re pretty sure someone in the company has done what you’re looking for, but you don’t know how to find it because you lack the exact syntax.