Attend QCon Plus (November 1-12) and stay ahead of the tech that matters to keep your skills fresh. Register
Facilitating the spread of knowledge and innovation in professional software development


In this article, we’ll explore the benefits of using blockchain for business solutions, describing the differences between public and private versions of this technology in practice. We’ll also talk about a new type of chain — a hybrid of private and public chains which takes the benefits of both to create a truly versatile platform with no compromises.
The uptake of low code software is so strong that it will almost certainly make its way into your organization. Most software engineers shouldn’t be concerned about this because they are good at the things that low code software is not yet good at. The key to surviving and thriving during this change is ensuring that your role encompasses responsibilities that low code can’t do yet.
In the podcast, Rosaria Silipo talks about the emerging trends in deep learning, with focus on low code visual programming to help data scientists apply deep learning techniques without having to code the solution from scratch.
Scrum is easy to explain and hard to do well. The majority of Scrum Teams struggle to do Scrum well. The OMG Essence standard promises to make practices more accessible and to free them from the tyranny of formal methods and frameworks. This article explains how Essence Scrum practices produced by Ian Spence and Dr Jeff Sutherland can help your teams get better at Scrum regardless of the context
AI tools are slowly replacing the role of the developer – just as DevOps did before – and will eventually supplant DevOps entirely. Assessing whether that prediction is true is tricky. In this article, we’ll look at what AI promises for the development process, assess whether it can really ever take over from human developers, and what DevOps is likely to look like in a decades’ time.
Learn how to apply Microservices and DevSecOps to improve application security & deployment speed. Virtual Event on Oct 19th, 9AM EDT/ 3PM CEST
Turn advice from 64+ world-class professionals into immediate action items. Attend online on Nov 1-12.
Learn from practitioners driving innovation and change in software. Attend in-person on April 4-6, 2022.
InfoQ Homepage Articles How to Not Lose Your Job to Low-Code Software
Oct 12, 2021 9 min read
by
Doug Hudgeon
reviewed by
Daniel Bryant
When I was younger, my best friend's uncle was slowly reversed over by a party bus. At his funeral, underneath the sorrow, was a question in everyone's mind: How did he not see or hear the party bus in time to step out of the way? A similar question pops into my mind when I hear about enterprise software developers losing their jobs to low code software. Surely they could have stepped out of the way of that bus!
My friend's uncle couldn't get out of the way because he was caught in a pinch point – a spot where he had nowhere to move to. This article shows you the low-code pinch points for software engineers and how to avoid them.
Let's carry on with the party bus analogy. Imagine you are an enterprise software developer in a mid to large sized enterprise. You and your team spend your days building, deploying and maintaining a variety of applications used by your company. Some of the applications you've coded yourselves, other applications were "off-the-shelf" but required customization or integration.
Uncover emerging trends and practices from the world’s most innovative software professionals. Attend QCon Plus (November, 2021).
Suddenly you notice that a bunch of business users are riding around in the low-code party bus building their own applications. Should you be worried? I think not.
From 2010, with the rise of Blue Prism and then UIPath, you may have seen the dramatic impact of automation on your colleagues in Finance and HR. This is because there are lots of pinch points in those operational areas. When Accounts Payable is largely automated it is difficult for an accounts payable team member to slide into a different role – their entire job is gone. 
But software engineering is not accounts payable. The amount of work you have is driven by the ability of software to make a meaningful difference in your organization. Take a look at your current queue of work. If your team is like most IT teams there will be a mountain of unmet demand for new applications or additional functionality for existing applications. Thinking that any amount of automation will reduce that demand to zero is like thinking that a faster car will get you to Mars. If low code software starts taking some of your work, there will likely be other projects you can work on. If you handle this right, you can even shuffle some of the painful projects over to the party-goers on the low code bus.
The work performed by software engineers may be deepened rather than diminished by the introduction of automation.
— Ralph Aboujaoude Diaz, HFS Research
Secondly, and more fundamentally, there are certain aspects of software engineering that are harder to automate than others – making it unsuitable terrain for the low code party bus to drive across.
For example, low code tools make it easy for non-developers to create a table to store data. But they can't do much to help the non-developer structure their tables to best map to the business problem they are trying to solve.
Low code tools also make it easy for a non-developer to build and deploy an app. But the tools don't ensure that the right stakeholders have been involved at the right parts of the project to comply with your risk and compliance guidelines.
Rather than losing your job as an enterprise software engineer, you are more likely to spend less time coding and more time on the other parts of your job as low-code spreads through your enterprise.
For most software engineers, the arrival of low code software in their company will give them the opportunity to add a lot more value to their company now that they don’t have to do the boring, repetitive stuff.
— Jan Oberhauser, CEO, n8n
Low code software can be used for lots of different types of projects from process automation through to apps that help users do their jobs faster and more consistently. As you read through the article picture one of the following scenarios:
There are lots of books on how to structure an enterprise software project (See Blair Reeves' Building Products for the Enterprise for a good quick read). For the purposes of this article, let's categorise a project into four stages:
To help understand how low code software tools will impact your work, let's look at their current capability across each of these stages.
Of the four stages this is the last stage that low code software will take over. The planning and design stage encompasses everything from getting the right stakeholders involved to ensuring there is sufficient budget and resources to build and maintain the app and checking that you are building the right app. For example, imagine you work for a real estate company with customers complaining that there is too long a delay in getting contract documentation over to them. There are several ways to solve this problem but determining which way is best for your company depends on understanding the source of the delay and the various ways that delay can be minimised. This type of analysis won't be handled by low code software anytime soon.
This is the core capability of low code software today. Once you have your overall design then your team or your business users can crank out an application using low code software faster than ever before. The key advantage of getting your users using low code software for this stage of the project is that low code software helps them determine what it is they truly need. Instead of attempting to draft and communicate detailed requirements and a spec they can iterate over the solution until they have something that suits their needs.
One of the key areas of low code disruption is its ability to abstract away the complexities of infrastructure – which makes it possible for non-experts to build and deploy surprisingly complex applications
— Rick Lamers, CEO, Orchest
There is one area of this phase that will still involve your team – that is tackling the tough problems that aren't handled neatly by your selected low code solution because they are specific to the business problem you are tackling: For example, how do you extract relevant data from real estate contracts? How do you get access to a particular government dataset that doesn't have a standardized interface? How do you build a machine learning model that can categorize claims based on risk? But even if you don’t have the expertise in-house, a new category of software companies such as Managed Functions are emerging to handle these bespoke requirements.
This stage is currently the wild west of low code software. Each type of low code platform takes a different approach to deployment.
The upshot is that your team will need to set some guidelines on how this should be handled and who should handle it. I covered this in an earlier article in this series. Once the guidelines are set the low code platforms will help follow the guidelines – but responsibility for this rightfully sits with IT rather than the business.
This is currently the trickiest stage to address. Maintenance involves both break/fix activities as well as ongoing enhancements. Most business units are not set up to do this work but need to be involved because, if they built the application themselves, they are the only ones who know how it works from a business perspective.
Over time, low code solutions will handle this phase better but it will likely always require a combined effort from software engineers and the business to manage properly.
If you are a software engineer in a mid to large sized company and you’re able to communicate well with business users then you don’t have much to worry about. You’ll always find a way to add value to your company.
But, there are two areas low code will have a big impact on software engineers and, if you work in one of these areas, you should be aware of the larger trends at play:
In smaller companies, the decision to use low code software rather than building custom apps makes a lot of sense. Look at it from the perspective of the CEO of a smaller company: He or she must choose between hiring a React developer to build a few custom apps (and then hope they never leave, retire or die) or use low code software to build the app. Going with the latter is a no-brainer. Software engineers employed in these companies will lose their jobs or will transition over to building low code apps for their company.
The greatest job losses will occur in app development companies. In these companies, the junior to mid-level developers rarely have the opportunity to utilise their communication skills in the same way a directly-employed enterprise software engineer can. If you are a junior to mid-level developer cranking out apps or building ETL pipelines and you look around your office and see dozens of your peers doing the same thing then it may be time to look at how you can enhance your communication and client-facing skills.
Technology change happens slowly and then all at once. It feels like we’re at the cusp of the all-at-once inflection point for low code software. The next couple of years will see dramatic changes in the type of work performed by software engineers. If you stay away from the pinch points, these can be very good years indeed.
The Low Code Road is a series of articles written for InfoQ by Doug Hudgeon, CEO of Managed Functions. You can read the first articles in the series here and here.
Doug Hudgeon is the chief executive officer of Managed Functions, an integration company specializing in helping enterprise low-code and RPA teams deliver projects faster by providing bespoke components to handle the thorny problems they may encounter on a project. Uniquely, the components can be deployed as serverless functions to the enterprise’s cloud (AWS, Azure or GCP) so the solution runs entirely on their infrastructure. He is also the co-author of the Manning book "Machine Learning for Business" which shows your users how to solve real-world business problems using AWS SageMaker. You can find him on Twitter.

 

A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. View an example

We protect your privacy.
You need to Register an InfoQ account or or login to post comments. But there’s so much more behind being registered.
Get the most out of the InfoQ experience.
Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p
by Leo Mat,
by Leo Mat,
Your message is awaiting moderation. Thank you for participating in the discussion.
The author is contradicting himself, at first he’s saying that small companies or large companies with small tech teams will get rid of some of their software engineers then he’s saying if there are too many software engineers doing the same thing (they’re in large teams) are gonna lose their jobs. So far Salesforce has been the most successful low code platform yet it requires plenty of developers and learning to use it is more complicated than learning Java to build a clone of it from scratch, not too mention it sucks and has too many limitations, most of software engineers including me hate to work on it and would prefer to work on CRM built j2ee.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. View an example

We protect your privacy.
Focus on the topics that matter in software development right now.
Deep-dive with 64+ world-class software leaders. Discover how they are applying emerging trends. Learn their use cases and best practices.
Stay ahead of the adoption curve and shape your roadmap with QCon Plus online software development conference.
InfoQ.com and all content copyright © 2006-2021 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we’ve ever worked with.
Privacy Notice, Terms And Conditions, Cookie Policy

source

Leave a Reply