Category: Low-Code/No-Code

  • Blue-Green Deployment: What Are the Options?

    Blue-Green Deployment: What Are the Options?

    Blue-green deployment is a change management strategy for software releases. Blue-green deployments require two identically configured hardware environments. One environment is active and serves end users while the other remains idle.

    Blue-green deployments are typically used for applications with strict uptime requirements. First, new code is released to staging environments and fully tested. Once the code is reviewed, the team adjusts the router configuration to redirect application traffic to the staging environment. This staging environment then becomes the production environment.

    If problems are found after the switch, the team switches traffic back to the old production environment and continues running the original version. Once the new code is validated in production, the team can update the code in the idle production environment, and use it to test the next release. For more background, see this detailed blog about the blue-green deployment pattern.

    Blue-Green Deployment Benefits

    Here are some of the main advantages of blue-green deployments.

    Standby System
    A blue-green deployment always ensures a server is on standby, providing a crucial backup when the system fails. In addition to facilitating software updates, this approach improves risk management, allowing you to switch to the backup server during a malware breach.

    Redirecting traffic to the other system version is easy because it has the same infrastructure. The system can stay live and functional while the teams fix issues.

    Smooth, Fast Releases
    A blue-green deployment allows product owners to push software to production quickly. It offers the flexibility to release an update at any time, with no downtime required. End-users don’t feel the impact of each release. DevOps teams can also benefit from smooth releases because they don’t have to race to meet deadlines for scheduled outages.

    Simple Rollback Process
    Rolling back an update is also fast in a blue-green deployment. Simple rollbacks reduce the risk of experimenting in a production environment. You can implement rollbacks by setting the application to read-only or using a load balancer to handle active transactions during the cutover. This can be significant for Kubernetes security because if security vulnerabilities are discovered in the cluster, you can easily roll back to a previous safe version.

    No Downtime
    A blue-green deployment allows you to avoid downtime, whether scheduled or unexpected. You can shift users to the other model during maintenance checks and fixes. Upgrades can occur anytime because there is no need to wait for times with lower traffic (i.e., midnight).

    Testing in Production
    Testing in production allows you to check a live product’s functionality, showing how it performs in the real world. The drawback of this approach is that it can expose end-users to bugs during testing. A blue-green deployment lets you test the product in an inactive production environment, minimizing the risk of bugs making it to the live environment.

    Blue-Green Deployment in Kubernetes

    Many development teams are migrating to Kubernetes as an environment for development, testing and production deployments. Kubernetes makes it easy to deploy applications and can also be used to automate blue-green deployments.

    However, Kubernetes does not provide out-of-the-box blue-green deployments. It has a Deployment object that allows “rolling updates”—this allows you to update your applications without downtime by incrementally replacing pods with the latest version of an application.

    This is similar to a blue-green deployment but doesn’t offer all the benefits. Rolling deployments can make it difficult to roll back if there are issues with the new version. You might require Kubernetes health checks to determine the status of pods within a deployment. Applications might take time to roll out, while the pure blue-green pattern allows you to switch over to a new version instantly.

    Blue-Green Deployment in Kubernetes: What are the Options?

    Argo Rollouts
    Argo Rollouts is a set of Kubernetes controllers and CRDs that provide advanced deployment features for Kubernetes such as blue-green and canary deployments, experiments, and other progressive delivery capabilities.

    Argo Rollouts optionally integrates with Kubernetes ingress controller implementations and service meshes, leveraging traffic shaping to incrementally switch traffic to new versions during updates. Rollouts can also query and interpret metrics from other systems to validate key KPIs, and automatically promote or roll back releases.

    Flagger
    Flagger is a progressive delivery tool that automates the release process of applications running on Kubernetes. It reduces the risk of introducing a new software version into production by gradually migrating traffic to the new version while measuring metrics and performing conformance testing.

    Flagger implements multiple deployment strategies (canary releases, A/B testing, and blue-green deployments) and integrates with various Kubernetes ingress controllers, service meshes, and monitoring solutions.

    GitLab CI/CD
    GitLab is a collaborative DevOps platform and open-source code repository for large software development projects.

    In addition to a code repository, GitLab also provides CI/CD automation and issue tracking. GitLab repositories allow the hosting of different software versions and entire development pipelines, allowing users to roll back software and environments in case of unexpected problems.

    GitLab supports both manually triggered deployments and scheduled deployments to Kubernetes production systems, using progressive deployment (including blue-green deployment).

    CircleCI
    CircleCI is a CI/CD platform that helps engineering teams build, test, and deploy software, while viewing code changes in real-time in a dashboard UI.

    CircleCI can be deployed to virtually any target and can be easily configured to integrate with other services, for deployment strategies such as feature flags, blue-green and canary deployments. It supports both fully automated deployment processes or a process with manual approvals, with the ability to easily customize deployment configuration.

    Conclusion

    In this article, I explained the blue-green deployment pattern, its benefits, and how it can be beneficial for Kubernetes deployments. I introduced four tools that can help you implement blue-green deployments in your Kubernetes clusters:

    ● Argo Rollouts – Part of the open source Argo project. Includes Kubernetes controllers and CRDs that provide advanced progressive deployment features.
    ● Flagger – An open source progressive deployment tool for K8s that supports canary releases, A/B testing, blue-green, and more.
    ● GitLab CI/CD – Supports both manually triggered deployments and scheduled deployments to Kubernetes production systems.
    ● CircleCI – Supports deployment to Kubernetes clusters, with deployment strategies such as feature flags, blue-green and canary deployments.

    I hope this will be useful as you learn to implement progressive deployment patterns in your Kubernetes environment.

  • A DevOps Thanksgiving: What Are You Thankful For?

    A DevOps Thanksgiving: What Are You Thankful For?

    As crazy as it seems, here we are on the cusp of another Thanksgiving. This year has gone by so quickly, and as we enter the holiday season and the end of 2022, those of us in the DevOps community have much to be thankful for. First and foremost, I’m so happy to once again see my colleagues and friends in-person at conferences and events around the world. I’m looking forward to resuming travel not just in the U.S. but the rest of the world and seeing DevOps enthusiasts share their knowledge, their experiences and further the state of DevOps.

    While we are thankful for the resumption of a more normal lifestyle, we also need to pause to acknowledge and mourn for those we’ve lost during this terrible pandemic. Their lives and the time taken from all of us during these past years can never be replaced.

    They say every dark cloud has a silver lining; if there was a silver lining for DevOps during the COVID-19 pandemic, it was the unprecedented pace of digital transformation. Make no mistake—digital transformation is powered by software development and DevOps powers software development. It wasn’t just the sheer number of applications or lines of code that were developed and deployed during these past few years, but the accelerated maturity of software supply chain software pipelines that became the de facto standard for how software is developed and deployed; that was greatly accelerated as a result of the push to digital transformation.

    It was not just software development that was accelerated, software supply chain attacks gave rise to an entirely new subset of security. Software supply chain security and SBOMs are now everyday words in the security lexicon. While I’m not happy about an entirely new class of attacks, I’m grateful for the response the White House and the U.S. government gave to our industry as a whole to address software supply chain attacks. I’m also grateful for the continued evolution of tools and techniques, people and processes around DevOps.

    While some look to make marketing hay by proclaiming that DevOps is dead and other such nonsense, the truth is that DevOps is thriving. It is the way software is developed today. In fact, in conjunction with cloud-native, it would seem that we have a whole new stack and an entirely new way that software is created.

    Looking forward, on the horizon we continue to see the development of AI that is making a real impact on observability, testing and application management. I think we’re also on the verge of AI having a profound impact on software development, as well. Low-code/no-code development tools paired with AI promise to take some of the most mundane software development tasks and automate them. This will free up overworked software developers to focus on higher-value software development tasks.

    Despite macroeconomic conditions putting a damper on the entire tech space (if not the entire world economy), I remain enthusiastically bullish about the continued growth and maturation of DevOps and I am excited to see what the weeks, months and years ahead bring. I am grateful to be involved in our industry during these heady times, and I’m grateful to you, our readers, supporters and the community for your continued support of our company.

    To that end, I wanted to announce that we’re trying something new this year at Techstrong Group, and we hope you’ll join us. We want to know what you believe makes tech strong—and we’re asking people to record a quick TikTok video or LinkedIn video with the hashtag #Techstrong. We’ll select the winners and are giving away two (2) Sony PlayStation5 game consoles to the best two entries as selected by our judges. You can get all the details on our social media channels on Twitter, Facebook and LinkedIn.

    So, now you know what I’m grateful for—we really want to hear what you’re grateful for and what you think makes tech strong! Throughout the holidays and the new year, we wish you health and happiness—and know that tech will remain strong!

  • Avoiding Developer Burnout With Clean Code Best Practices

    Avoiding Developer Burnout With Clean Code Best Practices

    Employee burnout is common in the tech industry, especially for developers. In fact, 83% of software developers feel burnt out from their work and of those, nearly half of them feel overworked. Often, this is because the processes currently in place at their companies are not effective and too much time is spent doing mundane work.

    Resolving coding errors is a necessary part of software development, but this isn’t always an easy chore. Given the complexity of code today, developers do tend to spend a large percentage of their bandwidth on maintenance issues, refactoring, debugging or just modifying code that they never wrote in the first place. That said, 44% of developers stated that fixing software defects and problems is their biggest frustration.

    Every developer wants to create good code, but repetitively dealing with issues that aren’t part of the code they write steals away time from doing interesting work. More than a third of developers claim that they would prefer spending more time with their families, participating in more physical activity and even getting a full night’s sleep than spending the majority of their time fixing code. Developers also stated that they could use the time at work to focus on new features and capabilities.

    By implementing clean code best practices across the organization, development teams can create an environment that prioritizes new and interesting projects while organically addressing errors. Clean code practices help keep developers engaged and interested.

    What is Clean Code?

    Every organization relies heavily on software and the source code that powers it to run successfully. Companies are aware that the source, or DNA, of their software is what counts as its most important asset. The behavior and functionality are both governed by the source code and if it’s not kept in good condition, the source code can turn from an asset into a liability.

    Clean code refers to a codebase that has reached a flawless and problem-free state. It is code that is maintainable, reliable, secure, readable and embodies other such attributes of code. While developers write clean code for their new projects from the beginning, they simultaneously address existing issues through set quality standards. The overall workload of security and development teams also is greatly reduced when clean coding practices are considered and integrated into the development workflow.

    With this method, fewer issues reach the final stage of inspections. It also avoids pricey post-production rework or drawn-out feedback processes. The outcome is a simplified and effective method for managing the state of your code.

    How Clean Code Helps Developers

    By giving your developers access to the power of clean code practices, organizations can make sure that their development teams are working on projects that are impactful and exciting rather than dealing with mundane repetitive work. This means that they have more time to research, put new ideas into action, and also be part of new initiatives that have a direct impact on their organization’s success.

    When using the clean-as-you-code approach, you create a precedent that, moving forward, new code that is added or updated won’t result in new problems. As new updates are made to old code, the overall quality of that code progressively improves. This is a much more manageable process and a huge step toward improving the overall quality of code.

    Additionally, the clean-as-you-code approach empowers developers to take charge of the quality of the code they deliver. The feedback loop to detect and fix issues is naturally shortened with the proper tooling they can use in their current DevOps workflow. And contextualized education helps them quickly understand the root cause and get guidance to fix them. When their everyday routines automatically incorporate this technique, the possibility of recurring or exposed weaknesses is greatly reduced. In the long run, this helps save development time and effort, making development so much more enjoyable.

    There are many things that are a necesssary part of a developer’s everyday responsibilities. Making it simple and efficient is a win-win for everyone. No matter the state of your codebase, the maturity of your development team, or the size of your organization, clean code best practices are easy to embrace and will make your developers happier and more satisfied at work.

  • SAP Adds Low-Code Platform to Build Custom Apps Faster

    SAP Adds Low-Code Platform to Build Custom Apps Faster

    At the SAP TechEd 2022 conference, SAP SE today announced it has added a low-code platform, dubbed SAP Build, to its portfolio to make it simpler for organizations to build custom applications.

    Sebastian Schrötel, vice president and head of low-code/no-code solutions for SAP, said SAP Build is designed to make the company’s low-code tools more accessible to a wider range of developers, including so-called citizen developers that generally don’t have a lot of programming expertise.

    The goal is to make it possible to monitor, analyze and automate processes by leveraging more than 500 templates available within SAP Build. The goal is to make it possible to not only build applications faster but also deploy them via a single click, said Schrötel.

    The company’s approach to building custom applications separates its core applications from code developed by others by running pristine instances of SAP enterprise resource planning (ERP) applications in a separate cloud, known as the SAP digital core. A custom application is then deployed in a separate cloud and accesses SAP data via application programming interface (API). That approach enables SAP to update its ERP environment without worrying about breaking custom extensions.

    Of course, not every organization has transitioned to that model, so there are still plenty of instances of SAP software running in on-premises IT environments extended using code written in Java or the proprietary ABAP programming language. Over time, SAP is hoping that custom code will either be retired in favor of a process it has added to its ERP platform or by a more modern instance of that process running with a custom application deployed on a separate SAP cloud platform.

    SAP also has partnerships with providers of low-code platforms like Mendix and OutSystems that organizations can employ to build applications, but with the launch of SAP Build, the company is making a more concerted effort to encourage organizations to adopt the low-code platform it developed.

    While it’s not clear how eagerly low-code tools are embraced by citizen developers versus professional developers, the one thing that is certain is the pace of application development is accelerating. In many instances, professional developers are embracing low-code platforms as an alternative to procedural code to reduce expanding application development backlogs brought on by digital business transformation initiatives. In other instances, professional developers are employing low-code tools to collaborate more easily with end users as they build and deploy the applications that drive those processes.

    Regardless of the motivation, the impact this accelerated rate of application development will have on DevOps teams is profound. Not only do these applications have to be deployed in production environments, but DevOps teams must also secure and maintain a much larger application portfolio. As a result, the need to automate DevOps workflows will become more pronounced than it already is.

  • OutSystems Acquires Ionic to Further Automate App Development

    OutSystems Acquires Ionic to Further Automate App Development

    OutSystems this week revealed it has acquired Ionic, a provider of an open source framework that provides developers with a higher level of abstraction for building and deploying mobile and desktop applications.

    OutSystems CTO Patrick Jean said Ionic will accelerate the company’s ongoing efforts to extend the reach of its platform for building low-code applications without developers having to worry about, for example, the screen size of the device an application is deployed on it because the framework automatically right-sizes it. Ionic, in effect, will provide an extension to the platform that OutSystems already uses to automate the building and deployment of low-code applications, he added.

    In addition to its namesake user interface (UI) framework for building mobile applications that can run on multiple platforms, the Ionic portfolio also includes a tool for natively deploying web applications, dubbed Capacitor, and a toolchain for building web component-based design systems, dubbed Stencil. Collectively, these tools are used today by more than five million developers.
    OutSystems plans to extend the capabilities of these tools to make it simpler to deploy applications on both mobile devices and desktop systems, said Jean. The overall goal is to reduce the cognitive load that developers currently carry when they need to build and deploy applications that run on multiple platforms, he added.

    That capability will prove critical as more individuals beyond professional developers become involved in building, deploying and updating applications, noted Jean. In fact, many of those developers are likely to be business people that only develop applications on a part-time basis, he added.

    The percentage of applications being built using low-code tools has increased dramatically. Professional developers have embraced these tools and platforms alongside so-called citizen developers that are using them to build applications, as well. As the backlog of applications that needs to be built steadily increases, low-code platforms have played a crucial role in enabling developers to keep pace with the demand for new applications.

    Less clear is the impact these low-code applications are having on DevOps workflows. On one hand, there are clearly more applications that need to be deployed than ever. At the same time, many of the DevOps and data modeling processes that once required, for example, a dedicated continuous integration/continuous delivery (CI/CD) platform are being embedded in the platforms provided by the vendors that create low-code tools.

    Regardless of how low-code applications are deployed, the one thing that is certain is the pace of digital business transformation is being greatly accelerated by these tools and platforms. DevOps teams will soon need to put guardrails in place that enable developers with a wide range of experience and skillsets to securely deploy and update applications.

    On the plus side, DevOps teams should also expect it to become easier to automate the delivery of low-code applications at levels of unprecedented scale. In fact, the issue going forward may not be whether IT can keep up with the needs of the business but whether the business can keep pace with the rate of innovation now being enabled.

  • One-Third of Developers Seeking New Job

    One-Third of Developers Seeking New Job

    With the relentless pace of enterprise digital transformation efforts, even in this softening economy, developers still face an enviable job market. The number of open job positions in computer occupations is greater than 804,000, according to National Foundation for American Policy (NFAP) analysis and, at 326,000 vacancies, software developers have by far the largest number of job openings available to them.

    US Developers Are Less Confident About Job Prospects

    Still, according to a new report from OutSystems, Developer Engagement Report: Are Your Developers Happy or Halfway Out The Door?, slightly more U.S. developers are seriously considering changing companies right now (33% U.S. versus 31% globally) and they feel less confident about their prospects. Only 25% of U.S. developers strongly agreed that there are many opportunities to easily get a better position right now, compared to 42% of global respondents.

    Still, not many developers are thrilled with their current jobs. According to the survey, only 49% of U.S. developers love their jobs and only 37% are very satisfied with the work they do every day. Outside the U.S., developers are a bit more optimistic. Globally, 64% reported that they love their jobs and 46% said that they are very satisfied with their day-to-day work.

    Interestingly, when it came to work-life balance, it was U.S. developers who felt more optimistic than their global counterparts. While 50% of all respondents strongly agreed that they need more work-life balance, only 38% of U.S. developers agreed on the same.

    Finally, while 48% of developers said that they would definitely be with their current employer within a year, when that timeframe was extended to two years, that figure fell to 29%. And U.S. developers are itchier to move, with only 38% saying that they would definitely be with their current employer in a year and 18% said they would remain there in two years.

    Most Low-Code Developers Also Traditional Coders

    The report also examined so-called low-code developers. As a subset of the broader population of developers, 59% of low-code developers reported being very satisfied with both team productivity and 57% were satisfied with the quality of tools they use at work. Only 41% of traditional developers felt the same toward team productivity, and only 36% of traditional developers are very satisfied with the quality of the tools they use.

    Interestingly, 71% of low-code developers reported that they can keep their workweek to the standard 40 hours, while only 44% of traditional developers said the same. While 63% of low-code developers said that they are happy with their salary and benefits, only 40% of traditional developers agreed. Further, low-code developers claimed an average of 3.5 job promotions at their current company while traditional developers said they’ve been promoted two times.

  • Low-Code/No-Code Options Key to Bringing Web3 Mainstream

    Low-Code/No-Code Options Key to Bringing Web3 Mainstream

    Driven by cryptocurrencies and NFTs, Web3 is one of the most talked about technology industry waves in the last several years. But even with all the money it’s generated and the media coverage received, Web3 hasn’t yet gained the mainstream acceptance that Web2 has achieved. One of the main reasons for this gap is that blockchain-based technology continues to be complex, requiring developers to learn new languages and development environments as well as gain expertise in concepts like cryptography, hashing, oracles, zero-knowledge proofs, proof of work, proof of stake and more. And even once users understand that they then need to figure out how these pieces all fit together. The required time and money investment has slowed adoption by developers—until now.  

    Web3 is finally coming into its own, thanks in part to the abstraction provided by SDKs and APIs. This technology is making it increasingly possible for all developers, not just Web3 developers, to participate and innovate on this new wave of technology disruption.

    If you look at many of the providers in Web3 like Infura (ConsenSys), NFT Port and OpenSea, for example, and their growth, there’s been a significant movement from these providers over the past couple of years from simply providing nodes for underlying blockchains to now offering higher-level APIs. This translates into developers and companies no longer having to set up their own nodes to provide SDKs and higher-level APIs that rely on data indexers and pre-audited smart contracts to simplify token minting and reading from blockchains. 

    With the evolution of APIs and SDKs, developers using these programs no longer have to learn the intricacies of creating contracts on different blockchains, multiple developer tools, syntax and languages nor must they possess a deep understanding of these different blockchains. Instead, developers can rely on APIs that abstract the underlying complexity, easing the burden for developers who need only pass parameters like chain for indexing, token or smart contract IDs and other general-purpose information. These APIs will evolve into providing more low-code/no-code offerings with larger graphical UI components that developers can simply drag-and-drop to extract value as well as create DApps that can also be retrofitted into their existing applications or app infrastructure. 

    This evolution will be similar to the way the cloud evolved; look at AWS’ and Azure’s infrastructure-as-a-service (IaaS) as a current example. Existing apps could be lifted and shifted onto the cloud. This led to platform-as-a-service (PaaS) offerings with APIs that were cloud-ready; with developers’ latency, security and scalability needs augmented by low-code or no-code offerings. This is also similar to Microsoft’s Power Platform which used drag-and-drop operations on many cloud components, allowing integration and extensibility of the Microsoft platform in a short amount of time. This spawned a new generation of ecosystem players as the bar to participate and innovate in the cloud lowered; now every type of developer, no matter what their area of expertise, can take advantage. This also meant that the new technology was accessible for all developers to solve business challenges more quickly while significantly decreasing time-to-market.  

    You can already see this parallel in the Web3 world. A lot of the key players building developer tools are starting to target the business and technical decision-makers. They are talking about how easy it would be for Web2 developers to leverage their high-level APIs and SDKs (something that Web2 developers understand extremely well) to use Web3 technology to solve new business challenges. And they can do so without setting up expensive innovation organizations and looking for scarce (and expensive) Web3 developers. The next step in this evolution would be to extend these APIs for NFTs, analytics, streaming, MEVs, estimating gas and more to have no-code, automatically generated components that finally allow more Web2 developers to transition to Web3 and, as a result, bring Web3 into the mainstream.

  • Despite Democratization, IT Department More Central Than Ever

    Despite Democratization, IT Department More Central Than Ever

    There’s been talk of the decentralization of IT within organizations for years, and events of recent years have certainly accelerated this trend. Yet, IT has never been more important to the success of the organization.

    According to ManageEngine’s newly released IT at Work: 2022 and Beyond study, an increasing number of IT-related decisions are being made outside of the formal IT department. Yet, the survey also found that just as non-IT employees and the lines of business take a larger role in choosing their technology stack, collaboration between IT and other areas of the business has actually increased, not decreased as many feared would occur.

    The survey found that 76% of North American decision-makers reported their organization encourages non-IT employees to develop their own applications using low-code/no-code platforms and most departments, most notably notable quality control (24%) and finance (21%), are independently turning to AI/ML solutions to perform their jobs.

    These findings echoed an earlier survey conducted by IDG for Snow Software. This survey found that 67% of respondents believed that at least half of their IT budget is controlled by their various business units and not the IT department. Interestingly, 78% agreed that this is a positive development for their organization and that it would ultimately enable their business to become more innovative and agile.

    That may be so, but many North American IT decision-makers responding to the ManageEngine survey (48%) also believed that a lack of training and basic technical knowledge (47%) are holding back their staff from taking full advantage of the technology available to them. Still, 76% of survey respondents reported that their staff is more technology-savvy today than they were before the pandemic.

    Those benefits aside, a full 99% of respondents said that their organization also faced challenges due to IT decentralization, most notably maintaining IT security (56%), overall quality maintenance (41%) and the reliability of ongoing support (37%).

    Paradoxically, despite the increased technology autonomy within organizations, the ManageEngine survey found that 82% of North American business and technology leaders agreed that collaboration between IT and other lines of business increased in the past two years. Further, 89% believed that the IT department’s success is directly linked with the general success of their organization.

    “Those enterprises that succeed here will be those that are able to not only have the right policies in place that encourage IT and line-of-business collaboration but the technology also in place that will identify applications and cloud services independently deployed by those line-of-business managers,” said Scott Crawford, an analyst with 451 Research, S&P Global Market Intelligence.

    It’s clear that the ease with which low-code/no-code platforms, cloud services and other cloud platforms made business technology accessible to non-IT decision-makers has decentralized and democratized IT decision-making. What’s interesting is that IT departments have found their relevance and importance within organizations increasing, and not decreasing as many feared. Those IT departments that have succeeded, and that will continue to succeed, are those that find themselves capable of supporting the technology decisions their various departments have made rather than centrally trying to control those decisions.

    The ManageEngine survey is based on the responses from 3,300 global IT and business decision-makers with 500 of those respondents residing in North America.

  • Techstrong TV: Leveraging Low-Code Technology with Tools & Digital Transformation

    Techstrong TV: Leveraging Low-Code Technology with Tools & Digital Transformation

    Low-code is playing a big role in Henkel Corporation’s digital transformation by connect remote workers with 30 shop floors all over the globe. Catarina Pinto, Henkel Digital Transformation Manager discusses how the team leverages low-code technology to deliver weekly releases across ten apps. HCL Software AVP Product Management Andrew Manby shares the role HCL Volt VX is playing at Henkel and other customers’ digital transformation initiatives. The video and a transcript of the conversation are below.

    Announcer:                 This is Digital Anarchist.

     

    Interviewer:                Well, the really great pleasure being joined by two very fantastic people talking about low-code/no-code and some of the impact from digital transformation projects. First joining me is Catarina Pinto, who is the digital transformation manager with Henkel, and she’s – Henkel Corporation. She’s gonna be talking about their project and involve low-code and that has been taking place. And a repeat guest, returning guest sitting in the right-hand chair is Andrew Manby, who’s AVP product management with HCL Software. Welcome to you both.

     

    Interviewee 1:             Thank you so much.

     

    Interviewee 2:             It’s great to be back,  Mitch.

     

    Interviewer:                Welcome back. Well, let’s do this. Andrew, why don’t you briefly introduce yourself, and then, Catarina, I’ll have you do the same, tell us a little bit about Henkel, and then we’ll go right into talking about your transformation project.

     

    Interviewee 2:             Right, perfect. So my name’s Andrew Manby. I head up product management for our HCL Digital Solutions portfolio. My specific focus and passion is really about digital transformation and using low-code to do that, and our tool of choice here is Volt MX, our low-code tool for professional developers.

     

    Interviewer:                Funny, that’s our topic today. And then –

     

    Interviewee 1:             I think this is.

     

    Interviewer:                Yes, go ahead.

     

    Interviewee 1:             Sure. Catarina. I am, as were said, digital transformation manager here at Henkel. I’m based in Amsterdam and I mainly work with the factories, so my goal is to lead partly the digitalization of the factories. I’m responsible in leading a global project that is the Connected Worker, where we basically aim to augment our workers in the shop floor. One of the biggest parts in this program is the Connected Worker apps, and that’s made with Volt MX as well.

     

    Interviewer:                Excellent. Well, I’m sure that a lot of interesting things have been happening over the last 18 months plus. How long has this project, digital transformation project been happening? Has it been more related to the pandemic, or is this part of the bigger program that’s going on across the company?

     

    Interviewee 1:             This is part of the bigger program we have. It’s one of our core pillars in the company, and it has been in full force since I joined, so 1. years ago.

     

    Interviewer:                Great. So your part of the project, would you say that’s a big component of it or one of several?

     

    Interviewee 1:             In this moment is the strongest component of it, so especially the Connected Worker apps, but we have a lot of things going on in our factories. We have a very powerful digital backbone. There are plenty of articles out there, business cases out there in terms of our digitalization in the supply chain, especially in Laundry, where I sit in this business unit. And basically what we aim is to extend this super powerful backbone that connects our machines in more than the 30 sites that we have worldwide, and also give the extra information of the user, so the knowledge of the person that is operating the machines, that is making sure that products are with extreme quality, that is making sure that everything is safe in the shop floor.

     

    Interviewer:                Now, we talked about the project you’re doing and with remote workers to the factory floor. Is that people who are across all 30 of those locations generally? Is it more concentrated in certain areas, locations?

     

    Interviewee 1:             No, we have, we are a real global program, so whenever we deploy an app it’s for everyone. It certainly helped during the pandemic because there was less need for people to be all the time in the shop floor if they are not business critical, and you can still see all the information from far away about what is going on in the shop floor, and basically are establishing a new way of communication here.

     

    Interviewer:                Great. And are you most of the way complete with this project? Are you still in the sort of early throes of it? Where are you at on your journey for this particular initiative?

     

    Interviewee 1:             So I would say that we are certainly in the scale up phase. So imagine this as a mini startup within the company where we see in the shop floor what are the processes that we can digitalize, so basically everything that is done in paper we will try to create an app or incorporate in our ecosystem so that we allow this information to be part of our data lake and really have insights from that. So we will work on everything from designing the product based on customer needs, so a lot of needs finding that is out there. Product design is also on our feet. Then we do the development with two teams of developers in this moment that we have, one in Cairo, one in Serbia. And then we also lead the implementation within the factories, so it’s a big project with a lot of scoping and that really hits all the parts of the factory, be that continuous improvement, be that safety, quality, and other departments that we are also thinking about expanding to.

     

    Interviewer:                Yeah. Mission critical for sure. So let’s talk a little bit about the role of low-code and the tools that you’re using, obviously Volt MX being one of those. And I know you’re here not as an endorsement necessarily, but clearly you’ve partnered with HCL Software and they’re playing a role in this also. Is low-code type tools, is that something relatively new to Henkel, or have you been using those types of tools for quite some time?

     

    Interviewee 1:             So they are relatively new, since the project started I would say, but it was super important for us because we really wanted to be very quick to market. And since the beginning of the project we kind of work like an Amazon company would do, so our goal is to get products that are unfinished into the shop floors, so MVPs, and make sure that we kind of use it as a playground with the people in the shop floor to get real user needs, to make sure that it’s customizable to 30 locations. So it’s really important for us to be not only fast in getting the MVP, but also fast in getting the feedback introduction of our people. So we are very people based, very customer obsessed. We really did this very big mindset shift in terms of it’s not creating the whole product and then shipping, but delivering that iteratively with the people that will use it in their day-to-day, and here low-code plays a very important role because it allows us to be very fast in getting to the market needs.

     

    Interviewer:                Yeah, a very lean approach doing MVP, rapid development iterations of your releases, so totally, that’s a great use of low-code type technology. Andrew, are you working directly with Catarina on this in the organization, or kind of observing as part of the HCL team from a little bit more distance?

     

    Interviewee 2:             I would say observing more about what they’re doing, and I think there’s a good interchange between our people in Europe working with Catarina and her team. We want to invest in some future innovation things that they’re looking at as well, and to bring those and help Catarina. Because I think part of the value that I hear from customers is us coming to the customer and saying, “Well, we’re sort of seeing these trends. How do they apply to your individual business?” And then take them through a period of exploration to really try and understand what is your digital vision? Now let’s get concrete on a specific area, and how does that innovation really help?

    I think in terms of Henkel, they are a leading innovator in digital transformation. I mean I, given the types of things they’re doing, they’re very data centric and very outcome oriented, and I think this initiative dovetails. But what delights me about what some of Catarina’s point of view is very pragmatic, but it’s – I think one of the things that you said, Catarina, is when you’re interacting with the people on the shop floor, you’ve got to show the value to them directly. Right? So if it’s – I was thinking about the expression you have. It’s not only simplifying their lives, but it’s as easy as paper. It’s got to be. Yeah.

     

    Interviewee 1:             Exactly. With our biggest competitor, so in the end it’s really difficult to compete with, and that was really a key, it plays a key role that we really have the interest of the people. And if people feel ownership in the sense, oh, I asked for this feature. Two days later it was there, it’s so much more important. They understand. And in the beginning I had to do a lot of push to say, “No, please give me your feedback. Bring me your problems. That’s exactly why I am here. I’m contacting you every day.” Until the problem today that is I get my inbox flooded with all the requests, and I don’t know where to turn to. But I think it’s much, much more – it’s a much better environment.

     

    Interviewee 2:             Yeah. So that’s actually interesting, Catarina, ’cause you’ve reached that sort of tipping point where it’s actually, instead of being push, it becomes a pull –

     

    Interviewee 1:             Exactly, and that –

     

    Interviewee 2:             – from the factories, which is tremendous, and I think you were also telling me where they’re actually saying now is, you know, we want these features and we want more iPads. Right?

     

    Interviewee 1:             Yeah, and that’s a big pull from the company as well, but I think it’s, I see it as a very positive insight into the program. Just building on the previous point, for example we are trying to build now a product, also app-based, but the idea is that it’ll be a company-wide product, so be for all the functions within the factory. And especially in the beginning I was a little bit unsure. I was thinking maybe this is too much. And then one of the factories just told me, “Hey, if you add these two little things, I can push this all over the factory.” Like okay. One week later, they were implementing in all functions, and I got, wow, that’s amazing. I didn’t even need to do marketing because their, it was one of their biggest needs, and we are really cooperating with HCL to really take this to the next level, and I think it will be a very awesome product.

     

    Interviewer:                What’s interesting is over so much time people have gotten conditioned when requesting technology applications, systems, you know, they don’t get what they want very quickly, at least they haven’t historically, and so I imagine it’s a big shift, a big mind – initially they didn’t expect you to be able to deliver as quickly as you are, and now that they are, of course, they flood your inbox. Right? Be careful what you ask for, too, right?

     

    Interviewee 2:             Yeah. Yes, exactly.

     

    Interviewee 1:             _____.

     

    Interviewer:                I’m curious, how many people do you have working on the project? And is this inside IT? Is this outside of IT? How’s it considered –

     

    Interviewee 1:             No, it’s inside IT. So we have in this moment four developers sitting in two places, two kind of scrum masters, say it like this. I act as product owner as well, so I have a lot of hats during the development of the products, so from end to end of the products, but that’s basically the core of the team. So very, very small team, and we really need – it’s like I said, like almost a mini startup, and we have ideas and we say, “Okay, find a way to do it. Let’s do it. Let’s put this into the ground and let’s make people happy with what we do.”

     

    Interviewer:                Are you doing sort of an agile two-week sprint type approach?

     

    Interviewee 1:             One-week sprint –

     

    Interviewer:                Are you doing more DevOps release it as it’s ready, it’s tested, it’s good to go?

     

    Interviewee 1:             In this moment we are doing one-week sprints, so really we – especially because we have a lot of apps simultaneously. So we have in this moment around ten apps that are part of our major ecosystem that all need some kind of maintenance or they have new requests from the guys on the shop floor, or I have new ideas that I want to implement. They are based obviously in customers’ feedback. So it’s really very, very fast. We don’t release in all of the streams of course, but we try always to be very based on customer requests and superuser centric.

     

    Interviewer:                So how would you say using low-code, using Volt MX low-code kind of tools, how does that – has it fundamentally changed your ability to deliver that quickly? Is it that revolutionary? Is it sort of an evolution of a journey you’ve been on to get to this point? How would you describe it?

     

    Interviewee 1:             I think it certainly helps, and especially with the connection with HCL that provides a lot of support so that we can also take advantage of this low-code product, that we can create things that are repeatable. Right? That we don’t have to reinvent the wheel every time that we build something. And here really the size of the market decreases, yes.

     

    Interviewer:                Interesting. And something Andrew and I have talked about is the citizen developer, the professional developer, inside, sometimes both inside IT, can also be external. Would you consider your team more of a professional development team as what people – that’s their jobs is being developers, or are these citizens, business people sort of performing the development functions?

     

    Interviewee 1:             In this moment a little bit more towards the professional developers here, because we really are not that big and we really have a lot of apps, so we really need to be a little bit more focused on that.

     

    Interviewer:                Interesting. I’m curious, Andrew, what do you see – you see some commonalities between things that are contributing to the success that Catarina is having at Henkel that you maybe have seen with other customers?

     

    Interviewee 2:             Yeah, absolutely. Yeah. I mean our focus, Mitch, is predominantly in enabling people like Catarina and Henkel with the professional development teams, and they don’t need to be big teams. I mean you can tell they’re a very agile team, a very responsive team. It’s very impressive to hear that. In our world, it’s really that idea if they’ve got the vision around the digital transformation and a willingness to be able to do that, we can help facilitate to do that very quickly with them, and I think it’s really that partnership. Sometimes that’s simply just being able to sit down, train, work with the customer, train them, build some prototypes, and sometimes it’s a little bit more of a discussion around a business process that they want to re-engineer. And we have a, what we call a studio process where we can bring them in, we can reimagine or think about what that would look like, build a prototype, and then get the feedback from the people on the ground about whether that would work. And sometimes either of those approaches works. it just really depends, I think, on the maturity of the organization.

    But what I also find interesting, which is embedded in what Catarina was saying about the only if you add that couple of thing, you know, we’re seeing that – we did a session recently with Jarrod from VELCO which is up in Vermont, the Vermont Electric Company, and they’re like the nation’s first purely distribution network, and they’ve got about 15 apps out there and they’re starting to think about how can they sort of consolidate some of those apps and build some super apps in the area of field service. So we’re seeing the folding in on some of those developments to go in new directions, but one of the impressions and the feelings I get talking to the customers, where they start and where they end up are two different places. I mean like the old adage, right? There’s always new ideas that come from customers that take them in different directions. In the case of VELCO, they have a scientific application which is part of the government reporting to say, you know, in times of hot temperature, what happened on the loading of the transmission lines. So that required them to integrate with MATLAB software and lets you do some heavy computational analytics.

    So I mean what we’re seeing is people are asking the questions, and we’re sitting down with them and figuring out how to do it, so it’s an exciting time.

     

    Interviewer:                It definitely is. And Catarina, sorry for stumbling on your name. I’m curious, success breeds more success, or certainly brings a lot of attention, and one of the things that’s happening in this whole COVID time acceleration of digital transformation projects is as people had success other parts of the organization started looking at that and say, “Well, how come they can deliver in a week, and we deliver every two months,” or every whatever. Are you getting some attention from the rest of the organization? Is that part of why you’re adding more apps, or are other groups looking at potentially spinning up and doing low-code kind of work?

     

    Interviewee 1:             A little bit of both. So from our organization, I would say yes because we are really working, maybe we are even extreme agile because we are one-week sprint. But the mindset shift of delivering products to the shop floor that are not extremely ready, that are still to be improved, that are lending pages in apps that then are created with the people, I think it’s an almost new paradigm shift that we are starting to see more and more and more, and people are also requesting things that are more useful for them for their daily lives.

    And one of the things that we are also doing is we are going into this exact idea of having less mini apps and have one core that connects our backbone to different modules, and the apps worked basically as modules and puzzle pieces. And that’s more or less type of ecosystems that we want to have, one thing that connects everything that’s basically our core, this big problem that I was talking about, and then having the different workflows that the guys have to do every day, just piece in in order to make the complete puzzle.

     

    Interviewer:                Wonderful. This has been fascinating. Thanks for sharing your story with us, and congratulations on your success, and congratulations also to the HCL software team with a very apparent, a happy customer and productive team using your technology and leading digital transformation. Catarina Pinto, thank you for joining us from Henkel, and Andrew Manby, thank you of course from HCL Software.

     

    [End of Audio]

  • Techstrong TV: The Use of AI in Low-Code

    Techstrong TV: The Use of AI in Low-Code

    In this talk, Dave Wright, Chief Innovation Officer of ServiceNow, talks about how low-code is accelerating organizations’ AI journeys and is expanding into new, scalable use cases as we move into a post-COVID-19 world. The video and a transcript of the conversation are below.

    Recorded Voice:         This is Digital Anarchist.

     

    Charlene O’Hanlon:   Hey, everybody. Welcome back to TechStrong TV. I am Charlene O’Hanlon and I’m here now with Dave Wright, who is the chief innovation officer over at ServiceNow. Dave, thanks so much for taking a couple minutes and talking with me today. Always appreciate it.

     

    Dave Wright:              No, thanks for the opportunity.

     

    Charlene O’Hanlon:   Okay, great. So first, I’m really interested in your title, chief innovation officer. What’s that all about? Tell me.

     

    Dave Wright:              So it has multiple roles I suppose. Part of it is looking at how we understand what customers are doing with the products, so looking at customer stories, building out reference cases. Some of it is looking at what we do around the world of evangelism and looking at how we talk about what the technology does.

    And a lot of it is around looking at new technology and trying to understand, is that new technology gonna impact us in any way, or do we need to potentially look at some of these new areas of areas that we can move into to as well. So, it’s pretty cool. I get to spend a lot of time researching things. I get to speak to people, everyone from psychiatrists and sociologists all the way through to technologists. So it’s a pretty cool job.

     

    Charlene O’Hanlon:   Yeah, sounds pretty nifty. All right. Well, I wanna talk to you about low-code and it’s something that – We’ve been talking a lot about low-code over the last 18 months or so. It seems to have – I almost kind of feel like we’ve jumped the shark on the topic, but I wanna talk to you about artificial intelligence and the use of AI in low-code as organizations are swiftly adopting it and recognizing the real value that low-code has for the business.

    Obviously, AI is kind of icing on the cake, if you will, if it’s done correctly. So, interested in getting your thoughts on the role of AI in low-code and maybe kind of see what’s going on in the industry, what you’re seeing there.

     

    Dave Wright:              So I think a lot of times when people produce low-code applications, one of the things they’re really trying to drive is adoption of those applications. So when you build something, it’s gotta be better than whatever people were using before. And I think that when people start to integrate artificial intelligence into those low-code apps, what actually does is it starts to elevate the experience a little bit.

    So, it makes sure that the application you create actually delivers smarter outcomes. And this can be anything from ease of use of the application. So how do you start to process data and collect data in a different way? Or it can be the actions that the application then takes. So how does it learn from more and more people using the system to gradually improve and modify the experience to make it easier to use?

    So I think those are elements that you see people building in conversationally, or you see people building in with ML models. I think there’s probably a second part of the conversation, and maybe we’re not quite there yet, but I think in the future, you’ll actually start to see artificial intelligence influence the coding side of low-code. So actually helping people develop those applications as well, but we can go into that a bit more later.

     

    Charlene O’Hanlon:   Yeah. Well, that’s actually kind of one of the things that I was thinking about, because if we’re talking about low-code as a business enabler, so obviously we’ve got a lot of folks out there creating code or creating applications using low-code, and who don’t really have that experience in coding.

    So I imagine AI is kind of like a tutor to – That’s how I view it as AI within the low code application being used as kind of maybe the conscience of the voice of reasons. Like, “Are you really sure you wanna do that in that application?” Or just kind of helping them build a better application and user experience as part of that.

    So I guess we’re kind of talking about two different things. We’re talking about low-code and AI, because we could be building AI application using low-code technologies, or we could be using AI within the low-code application.

    So, are both of them kind of happening right now? And then, do we really need to distinguish exactly what we’re talking about in our conversation? And we could be talking about both of them, which is fine. I’m totally okay with that, but –

     

    Dave Wright:              So I think the both happening, the one that’s happening the most is people using AI within low-code applications. So that’s gonna happen on multiple levels. So it could be I’m building an application where part of it is collecting data or it’s interfacing to a person. So that might be the inclusion of things like virtual agents.

    And this is where you start to get into the real benefit of low-code developments. When you’ve got pro-code developments, you go out there and you build something, you’ve got a program of entirely skill that can build out exactly the interface you want, can build out the data structure.

    When it comes to something like that, building a national language understanding conversation, , it’s not the programming that’s hard, it’s the subject matter expertise, it’s knowing what to ask and what to ask next.

    So if you can put that capability to build those conversations into the hand of the SMA without them having to be some programming god, then it means that the conversations flow more naturally and you get what you want. So I think being able to enable people to build those types of interfaces when they haven’t got the programming skills, really speeds up what happens in the world of low-code development.

    And then I think you have the second part of it, where perhaps it’s using machine learning algorithms to then simplify processes. So, a great example of that is, let’s say you build an application and in that application, you’re gonna describe a certain type of request that you’ve got or something that you need.

    And what you do in a traditional non-AI powered system is, then you walk the user through some system where they had to categorize what type of issue it was. And then based on the categorization, you’d pass it to someone to execute. But if you can put, let’s say a machine learning step in that, where it looks at the description, and it goes, “Okay, based on this, I know what type of request this is, so I’m gonna categorize it.”

    Then you start to, A, remove the potential for human failure, where someone miscategorizes, but you also start to think about how you design your interfaces, because now you don’t need drop-down lists.

    So you merge and you take that app, you mobilize it, you put it on a mobile device. You can have a much more cleaner, simpler interface, because a lot of the work around data collection and data determinations being done by ML algorithms sitting in the background.

     

    Charlene O’Hanlon:   That’s interesting. I hear so much about low-code actually being used within an organization to create kind of those secondary internal business applications or internal business processes, and then kind of leaving the big stuff, the customer-facing stuff out to the developers themselves. But it sounds like, with this infusion of AI into the low-code applications, that may not necessarily be true forever?

     

    Dave Wright:              Probably not. I mean, I think the use case that you talked about them, where people are doing it for business applications, or maybe not business applications, the way I see people building them are applications for core operations. And it depends which area of business you go to.

    So you might go to a financial Institute and they’re looking at how they do loan processing, or you might go to a hospital and they might be looking at how they do clinician onboarding or how they set own emergency medical centers. So it tends to be something that’s very close to your core business, what you’re all about, that things don’t necessarily come off the shelf and that you need that specialist knowledge to build. So that’s where you see it now.

    I think moving forward, perhaps we start to see this concept of people using it for much wider use cases and starting to build bigger and bigger applications, or perhaps even more interesting, starting to chain the applications together. So there is also wrong application is actually driving something in another.

    And then we have concepts like the bigger AI models that we start to see emerging now. So some of these large language learning models, the GCP three-type concepts where you are starting to look at the capability to be able to describe an application and then have AI build that application based on the description. That’s an interesting development, and it’ll be interesting to see where that goes in the next two or three years.

     

    Charlene O’Hanlon:   Yeah, that is definitely something that I think is fascinating, but it’s also slightly frightening if you just tell the robot to go build something or the machine to go build it. So, with that in mind though, are we starting to see a shift in the way developers, their roles moving forward, because we are in effect kind of taking away at least some of the remote or the rote tasks that they do these days, kind of the lower through low-code and AI. So how do you see that changing, how developers view their jobs and what they actually do?

     

    Dave Wright:              So I think a lot of the things with artificial intelligence in the role of developments will be the same that we’ve seen the way that artificial intelligence works in the regular world. So what most people use artificial intelligence for is to either improve the accuracy or remove the mundaneness to try and take some of the stuff that people just don’t wanna focus on away.

    And I think that’s where you’ll start to see the first AI use cases in the world of developments where people are looking at standard routines that they use, or they’re looking at tasks that they just – They wanna focus on the complex side of it and have the simple side of the stuff just built from –

    So that coordination and that orchestration of being able to take what you need to be able to build the application. I think it’ll be it more AI as an assistant to programmers. I did a presentation a few weeks ago and someone said, “Does this mean AI is gonna replace all the programmers in the world?” And that’s not true. It’s no more than it’s gonna replace all the artists in the world, so that [crosstalk] in the thought process still sits in a program’s mind.

     

    Charlene O’Hanlon:   Yeah. And there’s also a level of experience and expertise that developers bring that low-code never could. If you’ve got somebody working with a low-code technology who is not a developer, they might not see the things that might trip up the program the way a developer might see.

    So I firmly believe that obviously there will always be a place for developers in the development environment, but I do certainly see the value of low-code. Even though I was joking at the top of our conversation that I kind of feel like low-code may have jumped the shark, but I think that there are so many different and practical use cases for low-code technology in organizations that are technology organizations, or they just happen to build sneakers or something like that.

    There’s always gonna be an application there where a part of what they do, whether it’s customer-facing or internal, they won’t necessarily have to even bother the developers or the IT part of the organization to get those things done. So yeah, I think low-code is actually going to kind of permeate the entire organization moving forward. It’s a matter of time. And I think AI is gonna be a huge enabler for that.

     

    Dave Wright:              I think so. I mean, if I look at our world, if I look at ITS ServiceNow’s world and how people build up on the platform there, we’ve done things like introduced the concept of app engine studio to make it simple for people to build apps if they can’t code. But then even on top of that, more and more people have said, “Hey, can we have standard templates?”

    Because a lot of people are gonna say, “Well, I’m gonna build an application.” And all the application really is, is an approval process, the way to track something being approved, or it’s a way to track leave, or it’s a way to track something that’s really simple that people do every day. “Can you just give me a template that allows me to go in and be able to do that?”

    So we’ve seen that concept already start to emerge, but the thing that always surprises me is, I’ll speak to businesses and some people say, “Well, even though you call it low-code people still need a bit of skill to be able to build these things. But I always think the irony of that is I’ve seen people do things in Excel that I couldn’t do in a million years.

    The complexity of the stuff they’ve got in the background, it’s like, “Wow, I don’t know if I can build a low-code app.” We’ve moved on quite a bit now, the concept of low code is available to everyone.

     

    Charlene O’Hanlon:   I think it’s amazing and I think it’s great technology. And we’ve been covering low-code on devopsy.kinsta.cloud for, going on five years now. So, it’s obviously been a technology that’s kind of been waiting in the wings for its moment. And the pandemic really highlighted its value to organizations.

    And I firmly believe it is here to stay and I’m excited about seeing how it can be extended in an organization and really bring a lot more business value than it is currently. So Dave, thank you so much for having the conversation with me, always enjoyable. And hopefully, maybe this time next year, we can have another conversation on the same topic and see where we are compared to where we are today.

     

    Dave Wright:              I would love to do that. All right. Thanks so much.

     

    Charlene O’Hanlon:   It sounds great. All right. All right. Well, thanks again, Dave, for your time. I really do appreciate it. All right, everybody, please stick around. We’ve got lots more TechStrong TV coming out. So stay tuned.

     

    [End of Audio]