No developer would ever be caught using low-code tools. Or not?

In the latest video in ShiftMag’s Engineer Explains series we’ve talked to Amanda Martin of Wix wants to break the stigma of using low-code platforms as a web developer.

She has changed her mind about low-code while working as a developer and now she wants to change other developers’ minds.

Find out why she thinks developers should look at them as just one of the tools in their toolkit and use them without prejudice when that’s the reasonable solution.

This video is a part of ShiftMag’s video series, Engineer Explains.

We’ve asked experienced engineers to share how they would explain some basic and some less basic tech terminology to different job tech job titles or at three levels of experience – from junior developer to CTO.

More:
How would you explain APIs, internal developer platforms, software architecture, software testing or scaling infrastructure without breaking the bank at three levels of experience?

The post Engineer Explains: Low code platforms as developer tools in 3 minutes appeared first on ShiftMag.

As Lin (Senior Director of Developer Relations at Postman) says, this shift, alongside investments in voice and chat interfaces, reflects a dynamic landscape where developers increasingly explore alternatives like GraphQL and gRPC.

Let’s see what will be the hot things among developers in 2024.

Generative AI fuels Low-Code Tool Investments

“The number one trend I think we’ll be seeing is an investment in low-code tools powered by generative AI“, says Lin. She highlighted that Postman specializes in crafting developer tools tailored for API work, so recently, she has seen more teams seeking low-code options.

This is indicative of the rising importance of APIs within businesses, the prioritization of developer experience, and also the expansion of who is working with APIs (it’s more than just developers). 

This demand, she adds, when coupled with the latest availability of generative AI frameworks, is already resulting in tooling companies investing heavily in redesigning software interfaces to interact with voice and chat, a new layer of abstraction designed to increase developer productivity.

Diverse API Evolution

There is, also, diversifying API technologies. “In the Postman State of the API report, we asked 40,000 developers what API technologies they’re using.

REST is still by far the most popular architectural style because it’s so ubiquitous, but has been declining in market share usage, year after year.

This is the case, claims Lin, because more developers are looking to other API technologies to address issues they face with REST; for example, GraphQL and gRPC were designed to avoid over-/under-fetching. Also, developers have more options for real-time communication, such as webhooks and WebSockets. 

To conclude, Joyce Lin emphasized that developers are actively exploring diverse options, leading to the creation of multi-protocol solutions within their organizations. This trend extends across various aspects of the tech stack, encompassing infrastructure, frameworks, tooling, and API technologies.

The post API Predictions 2024: REST is taking a rest, and we’re entering an era of API diversity appeared first on ShiftMag.

Yet, two-thirds of developers (65%) say that writing new code is the most valuable skill in their role.

These findings look contradictory at first glance. Let’s explore the advantages and disadvantages of each approach – coding from scratch and relying heavily on pre-existing code, tools, and platforms.

High customization requires coding from scratch

Coding from scratch refers to writing code without any pre-existing code or tools. This approach requires a deep understanding of programming languages and their syntax. Programmers who code from scratch have complete control over their code, which allows them to create customized solutions. This approach is often preferred for complex projects requiring high customization and control levels.

On the other hand, using tools and platforms to code offers several advantages. Firstly, it saves developers time and effort using pre-existing code libraries, frameworks, and APIs. This approach also reduces the risk of errors and improves the efficiency of the development process. Tools and platforms provide a high level of abstraction, which means that developers can have a more in-depth understanding of programming languages to use them effectively.

Why are tools and platforms so popular?

Several tools and platforms are available for developers, such as Integrated Development Environments (IDEs), Content Management Systems (CMS), and Low-Code Development Platforms. IDEs provide comprehensive tools for writing, testing, and debugging code. CMS allows developers to manage the content of their websites or applications without writing code. Low-code development platforms provide a drag-and-drop interface that enables developers to create applications without writing code.

Tools and platforms have become increasingly popular in recent years and for a good reason. They offer several benefits that can significantly improve the development process. However, there are some disadvantages to consider:

1. Using pre-existing code libraries can lead to security vulnerabilities if incorrectly implemented;
2. Reliance on tools and platforms can lead to a need for more creativity and innovation among developers;
3. Some tools and platforms can be expensive, a significant barrier for smaller organizations.

What do the numbers say?

According to the following numbers based on Atlassian’s State of Developer report, two-thirds of developers (65%) say that writing new code is the most valuable skill in their role, while 74% feel that being able to read code is vital. Yet 58% of developers don’t feel that writing code from scratch will be required as part of their roles in the future, and 51% say they mainly assemble code written by others. These findings look contradictory at first glance.

If we talk about the value of using the tool, the statistics conducted based on surveyed developers show the following:

These divided opinions mean that we can’t assume that all developers, or even teams of developers, feel the same way about coding or the tools and platforms that may replace it from scratch in the future. Managers and leaders of development teams should think carefully about their toolchains, what tools they add, and when to add them.

This ensures developers have an adequate voice in their work, especially navigating complex transitional periods. Judging by the mentioned research, if we segment these groups further, it shows a clear difference in their views:

Code > tools

• High value of coding and code review;

• Low likelihood of tools replacing code;

• Unlikely to be assembling code written by others.

Code < tools

• High value of coding and code review;

• Low likelihood of tools replacing code;

• Unlikely to be assembling code written by others.

Code = tools

• High value of coding;

• High likelihood of tools replacing code;

• Unlikely to be assembling code written by others;

• Moderate value of code review.

Neither code nor tools

• Moderate value of coding;

• Moderate likelihood of tools replacing code;

• Most likely to be assembling code written by others;

• High value of code review.

Coding from scratch and using tools and platforms both have advantages and disadvantages. It ultimately depends on the project’s requirements, the developer’s skill level, and the available resources. It is crucial to consider both approaches and use them appropriately to create efficient, secure, and innovative solutions.

The groups that favor tools over code or value neither highly are less likely to work in development roles like software engineer, software developer, or DevOps. They are more likely to be in adjacent roles such as network engineer, cloud engineer, security, or quality assurance. This explains part of the pattern because these groups are less likely to work directly with code daily.

This trend is evident when we examine the activities each group frequently performs as part of their role. Both groups are more likely to reuse code, manage code dependencies, and monitor applications. The code<tools group spends more time planning and scoping. The code>tools group is the most frequent one, showing a strong association with all code-related activities measured in research.

The code=tools group spends its time maintaining repositories and deploying and documenting code. They are more likely to design solution architectures and review code but are less likely to write code directly. The most proficient coders are the two groups that most commonly work with code (Code=tools and Code>tools). More than 90% consider themselves experienced or expert coders. Those that think tools will eventually replace coding (Code<tools) are the least proficient coders, with 76% claiming to be proficient or expert.

You can download more details about the Atlassian research dedicated to developers for 2022 as a PDF file.

The post Developers’ dilemma: Code from scratch or assemble existing code  appeared first on ShiftMag.