Tag: Low Code

  • Newgen Recognized in 2023 Gartner® Magic Quadrant™ for Enterprise Low-Code Application Platforms for Third Year in a Row

    NewgenONE digital transformation platform recognized for its ability to execute and completeness of vision

    McLean, VA, January 17, 2023 – Newgen Software, a global provider of digital transformation platform, announced that NewgenONE has been positioned as a Niche Player in the 2023 Gartner® Magic Quadrant™ for Enterprise Low-Code Application Platforms. The report evaluated 17 low code application platform providers and recognized Newgen for the third time in a row.

    “An Enterprise Low-Code Application Platform is an application platform that is used to rapidly develop and deploy custom applications by abstracting and minimizing or replacing the coding needed in development. At a minimum, an LCAP must include low-code capabilities (such as a model-driven or graphical programming approach with scripting) to develop a complete application, support for developing applications consisting of user interfaces, business logic, workflow and data services, and simplified application test, deployment and management,” per Gartner.

    “We believe this recognition from Gartner further validates our capabilities to empower enterprises by automating complex process and managing content at scale. Using Newgen’s Low Code Platform based on a modern architecture of microservices and AI/ML, we will continue to innovate for customers.” said Virender Jeet, CEO, Newgen Software.

    Download the complimentary copy of the Gartner report to know more.
    Disclaimer: Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.

    Gartner and Magic Quadrant are registered trademarks of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved.

    About Newgen Software Technologies Limited
    Newgen is the leading provider of a unified digital transformation platform with native process automation, content services, and communication management capabilities. Globally, successful enterprises rely on Newgen’s industry-recognized low code application platform to develop and deploy complex, content-driven, and customer-engaging business applications on the cloud. From onboarding to service requests, lending to underwriting, and for many more use cases across industries. Newgen unlocks simple with speed and agility.
    For more details, visit www.newgensoft.com

  • The Time for Automated Testing is Now

    The Time for Automated Testing is Now

    Skilled software testers continue to be in high demand, and it appears that trend won’t change any time soon. The current labor shortage and a looming recession is giving software development leaders good cause to think about how to attract and keep qualified personnel and, more importantly, enable them to work as efficiently as possible. Added to this scenario is a trend in the software development cycle toward shift left testing, which has put increased pressure on developers to take on testing responsibilities that often require taking on new perspectives and using new tools. Automated testing solves these problems by making it easier to learn how to build a consistent, reliable testing program in less time, requiring less maintenance.

    Add to this the future promise of artificial intelligence or AI-augmented testing platforms and current machine learning (ML) capabilities, such as self-repairing of test scripts, and you have a platform that both levels the learning curve and accelerates efficiency. The sooner organizations can transition from manual to automated testing, the better they can withstand internal and external market fluctuations.

    A Developer and a Tester Walk Into a Bar …

    Traditional software testing is a manual process in which testers are employed to replicate users and are expected to bring that perspective to their work. As such, software testers have a very different mindset than software developers. Where developers are protective of their creative output, software testers are driven by a curiosity to probe the limitations of a system. It stands to reason that the qualities that make someone excel at either of these roles is, likewise, not the same. And yet, with the trend toward shift left testing and continuous integration/continuous development (CI/CD), the industry has blurred the distinction between coder and tester to the dismay of both sides.

    Automated testing removes much of the monotonous work associated with repetitious test plans. It allows testers to focus on writing better scripts, extending the scope of their testing plans and scheduling more powerful load tests. From the organization’s perspective, once you have established a library of reusable test scripts, your testing program will be protected from future turbulence in the employment market, including recession and attrition.

    Low-Code/No-Code

    Regardless of the tool you use, code will be created if you are creating software — even test scripts. Ideally, however, a low-code/no-code tool can hide some of the complexity and promote best practices. Using a low-code/no-code tool can relieve a tester from creating test scripts from scratch by recording manual interactions and offering suggestions. In the case of shift left testing, a low-code tool can eliminate the need to learn entire testing frameworks while still enabling a developer to access code when desired. Automating testing also eliminates the human error inherent in repetitive manual tests. In short, test automation does not diminish the value of skilled software testers and developers; it increases it.

    Placed in the hands of skilled testers, automated testing will only become more powerful, more effective and more critical to your development cycle. It elevates the skills of testers and makes them more productive, accurate and thorough. Test automation also makes for a smoother transition to shift left testing, allowing developers to spend less time testing their software and more time doing the creative work that makes them thrive. In a market where attracting and keeping top talent is only going to get more difficult, anything you can do to lighten the burden on your employees and make them more productive will be a big win for your business. So, the question is not whether you should transition from manual to automated testing but when.

  • Techstrong TV: Recruiting Developers with the Right Skills

    Techstrong TV: Recruiting Developers with the Right Skills

    The biggest challenge facing the software industry is recruiting developers with the right skills, according to a Reveal’s third annual “Top Software Development Challenges for 2022” survey. Jason Beres, SVP of Developer Tools at Infragistics, and Charlene discuss how organizations can address these and other challenges effectively. The video is below followed by a transcript of the conversation.

    Charlene O’Hanlon: Hey everybody. Welcome back to TechStrong TV. I’m Charlene O’Hanlon and I’m here now with Jason Beres, who is the Senior Vice President of Developer Tools at Infragistics. Jason, thank you so much for taking a couple minutes and getting on the Zoom with me. I appreciate it. 

    Jason Beres: Thanks for having us, Charlene. Thank you.

    O’Hanlon: So I’m interested in talking with you a little bit about what you guys have seen over the last, I would say, year, year and a half of so, as it relates to developers, the great resignation, and the lack of qualified developers filling the roles these days, and the impact that that’s having on developer organization, especially as it relates to tools and tooling. So I wonder if we can set the stage a little bit, though. So, let’s talk about what you guys have seen in the market over the last year or so, as it pertains to the developer ranks. Are we seeing a lot of folks moving around?

    Beres: Yeah. It’s interesting, and the impetus to this interview is we just got a survey results back that we did. It went over a six week period, and we asked a lot of questions about what’s been going on in the last 18 months with developers. And this is a huge issue. It’s a huge issue for everyone, this lack of skills needed to move digital transformation forward. So developers are maybe looking at other career opportunities, maybe there’s new thing in the development space they want to do vs. what they did in the past. Maybe they don’t want to be a full staff web developer anymore, they want to get into AI, machine learning. And so there’s pockets that we see which are really having a hard time hiring. And you’re looking at numbers of 50 to 60 percent of companies having trouble finding skilled developers for positions. And Infragistics is no different. We’ve had positions open for almost a year for some job openings, and we have offices globally. We’ll hire anywhere. It’s a huge challenge, and I think it’s shifting the way organizations think about application development and tooling, and what they really need to move forward.

    O’Hanlon: I keep hearing about the great resignation, and the fact that everybody … not everybody … but a lot of people are rethinking where they want to be in life. And so they’re moving on to doing different things. But I almost feel like there’s got to be someplace where these people are going. So, is it really the great resignation, or do you think it’s just the great reshuffling? 

    Beres: Oh, wow. That’s a good way of putting it. I do think it’s a great reshuffling more than resignation. I think there’s pockets of the economy where it’s no doubt the great resignation. My brother is CFO of a trucking company. And they see that a lot of the truckers who couldn’t truck during the pandemic just retired. Or they’re like, “Man. Trucking’s really hard. I’m gonna go do something different, where I’m not on the road 60 hours a week.” So I think certain pockets of the economy are more affected than software developers, but I think software developers are the type of folks that need a challenge. So they’re always looking to be having the next big thing that maybe is not necessarily resume padding. It’s more about I need to be challenged more, and I’m looking at other options. And, by the way, I can get a 25 percent raise doing it. That’s … I think what’s driving it is you see big tech … The interesting thing is, right now what you see is, in terms of Meta, for example, the Metaverse, big tech is just … they’re taking people from each other now with ridiculous salaries. So where a guy might have made X amount, they’re offering three times that amount to go between Facebook, Google, Microsoft.

    So, in a smaller business, I don’t think it’s as bad as that, but it really depends where you’re at. Infragistics happens to be headquartered in New Jersey, or a 45 minute train ride into New York City. There’s a lot of big tech in New York City, so folks are really, “Hey. Should I take the risk? Can I still work from home?” Now work from home is a big benefit, and I think one of the risks that big tech sees is, “Well is that … hey we’re gonna make folks start coming in the office.” And a lot of people are like, “No, please don’t make us do that, or I will look elsewhere.” So I think the great reshuffle maybe is a better way of putting it, as you’ve described, in software development specifically.

    O’Hanlon: And I also see that a lot of developers, over the course of the pandemic, they used a lot of their … I won’t say free time, ’cause I don’t think anybody really had free time, but they were using some of their down time to really up level their skills. And so they’re shifting now into newer areas of development where, to your point earlier, maybe they’re more interested in AI. So they now have that skill set to be able to do that. So are you guys seeing that there are certain levels of developers, or certain areas that are seeing larger pockets of open positions over others? Are we looking at more entry level positions that are not being filled these days?

    Beres: I think what we’re seeing, and again, we have offices all over the place, in the US, in South America, in Eastern Europe and Western Europe, in Japan, and in India. And each one of those offices has unique problems. So, for example, in South America, I think we’re seeing just the development skill levels are continuing to rise. So maybe five years ago you could hire a lot of really junior people, and you could get them for less money. Now you’re hiring more senior people who are looking for a little bit more money, but they’re looking for more of a challenge. I think there’s more junior people maybe in locations in Eastern Europe that we didn’t see before, but the risk there is you hire someone who’s junior, and then they’re gonna jump ship relatively quickly, maybe in a year, maybe in 18 months, once they feel like, “Hey, wait a minute. I can go make life changing money, which might be a 20 percent raise when you’re in your early 20s just out of school, but that’s like a big stepping stone for you moving forward.

    So I do see that it’s challenging in each location. But at the same time, I think everyone up leveled. If you’re serious about your career, you did have more time last year, and the year before. You weren’t on the road for an hour, hour and a half. Folks that used to work in New York, as you know, would spend maybe two to three hours in a train, jammed together with other people, and they couldn’t even read a book. 

    O’Hanlon: Yeah. Been there, done that.

    Beres: So now they’re at home, and they’re taking free courses. And so you look at some of these training companies, even LinkedIn Learning, they’ve exploded in the last couple years, among others. And there’s training companies that ten years ago were nothing. Now they’re billion dollar companies, because of online training. And so I think if you’re serious about your career, you did up level, and you’re looking for other opportunities. Another one I didn’t mention before is Data Science. Data Science happens to be just exploding, of course, and maybe three to five years ago there were no data scientists. They were so hard to find. They were all career switchers. Maybe I was a really analytical guy, so I’m gonna try out this data science. Now, they’ve learned. Data Scientists are there, but they’re making still the bigger money. So it’s interesting how salaries have just shifted with the market over time as well.

    O’Hanlon: We’re seeing such upheaval everywhere. We think about the supply chain. We think about the people who are shifting jobs, and there’s so much in flux these days. It’s hard to pin things down. It’ll be interesting to see how things settle out over the next year or so. I think we are gonna see some settling over the next 12 months as, quote/unquote, things get back to normal, or somewhat sense of normal.

    Beres: We hope.

    O’Hanlon: Yeah. As we are seeing all of these things happening, all of these different forces at play, that’s gotta have an impact on the organization as a whole, beyond the human element. So what are you guys seeing with respect to tool sprawl, and other ways in which maybe the DevOps tool chain is being impacted, or just the whole developer experience is changing from an organizational point of view.

    Beres: I think what we do see is that the business is moving forward, no matter what. So businesses, and even in our survey, they’re looking at 10 percent growth, 20 percent growth. No one reported that they expect negative growth. They expect positive growth. And I think so many businesses … and it’s not just small businesses. It’s medium size businesses, and even like maybe silos in big tech realize that they were behind. So the pandemic said, or it really told them that they need to catch up. And so the business wants to grow, they want to move forward. So that’s when we start recognizing these gaps in skill sets and training, and things that we really wanted to do but we really can’t do ’cause we don’t have the people to do it, or we don’t have the right skill sets to do it, we waited too long. We didn’t move to the cloud. Well, why didn’t you move to the cloud? Gartner’s been saying move to the cloud for ten years, but you didn’t move to the cloud.

    So what happens is there’s more pressure put on dev teams, the backlogs get longer. So the way that affects the tool chain, the way that we see it affecting the tool chain in a typical enterprise, and even in SMB, is that tools like low code, no code tools are becoming more adopted, more trusted maybe. Organizations, IT is opening things up a little bit where maybe they’ll allow some APIs that maybe a marketing or sales team can use to do self service BI, or to create apps that aren’t business mission critical, but will help them be more productive. So we’ve seen a little bit of a shift there, and I think we see market growth there as well, in the last couple years, where the business of embedded analytics and low code, no code, were still in the billions of dollars, but billions of dollars in that upper scale, big tech. Now it’s being more widely adopted across the board and pushed down in SMB as well.

    O’Hanlon: Like I said before, I think we’re gonna see a lot of changes happening over the year as things settle down. Do you think that we’re going to see changes as it relate to how organizations actually choose their tools, and make the big decisions around that? How do you think that’s gonna be changing?

    Beres: So again, the pandemic taught everyone, you can’t be … you’re not beholden by the resources of IT as it is today. Or else you will be left behind. Digital transformation needs to happen, teams need to be more productive. You look at Microsoft and the explosion of Microsoft Teams, and this workspace collaboration. So, we see a growth in these types of tools. We see a growth of the number of people that are just gonna remain as a remote workforce, and then management, IT management and executive management at software companies is realizing that we need productivity. So how can we inject tooling that still give us what we need in terms of security, capabilities, user experience, but can move us forward in how we’re delivering applications internally and externally. So we see a lot of … before the pandemic there was a lot of talk about UX. So UX is top of mind in every executive meeting. But, did they really care about UX? Well now that everyone is, the consumerization has happened, your internal applications experience is just as important as your customer basing experiences. You need tooling that helps you do that more. So bringing in better user experience, tooling that can help deliver applications that look better, feel better, have a better experience, that are gonna drive internal growth, and obviously, external customer growth, really becomes critical and important. And in the next 12 months, in the next 18 months when things are starting to flesh out, these tools are here to stay.

    And again, there’s just not enough skilled workers. And if, for example, we can bring in a low code, no code tool to automate process and the super power user in the marketing or sales team, or even a junior dev can do it, vs. having to hire a team to build something from scratch, that’s where we see the savings, and that’s where we see this acceleration of the digital transformation in the enterprise.

    O’Hanlon: I really, really like the fact that over the past couple years, we’ve seen this whole democratization of just technology in general. And the fact that, to your point, somebody in finance or marketing or someplace an actually go in and make these changes, and in nine times out of ten actually get it done faster than if they had sent it over to the IT team to get it done. I think there’s really been a sea change, and it’s going to continue. How it ultimately impacts IT organizations, right now is pretty much anybody’s guess. But with the great resignation happening, and still happening, or the great reshuffling … I just like that word better … the great reshuffling happening, we’re gonna see a lot of changes, I think, to the way organizations view how they … not just how they utilize technology, but also maybe how they utilize their employees. That may be another conversation for another time.

    But Jason, thank you so much for having the conversation with me today.

    Beres: Thank you.

    O’Hanlon: And we look forward to having future conversations with you.

    Beres: Absolute. Thank you very much.

    O’Hanlon: Alright. Great.

    Alright everybody. Please stick around. We’ve got lots more TechStrong TV coming up, so stay tuned.

  • 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]

  • Front-End Frameworks Enable Better Dev Collaboration

    Front-End Frameworks Enable Better Dev Collaboration

    The general public often thinks about software development in terms of a lone software developer hacking away tirelessly at their keyboard. Of course, that is an anachronism, at best. What is true is that collaboration among software engineers, especially with their colleagues in IT operations which evolved into DevOps, has become the norm for rolling out better code faster.

    We are on the cusp of the next big evolution as software development becomes more of a ‘team sport’ than ever before. Now, collaboration is extending beyond IT (developers and operations) to cross-functional areas across various business teams. Product development, marketing and others also are providing input and feedback into the software development process and, most significantly, becoming part of the process.

    Front-End Frameworks are Driving Collaboration

    Historically, software programming, including front-end programming, happened in local IDEs. However, the rise of modern front-end web frameworks has led to an entire class of developer tools that speed up the build process and allow applications to be deployed more quickly.

    There are a number of front-end frameworks that do this: Netlify, Vercel and Appsmith, an open source internal app builder, are three examples. These tools are getting widespread adoption, because, in a world where front ends are becoming more complex, they make things like hosting, deployment, authentication and serverless functions much simpler. The other reason for adoption is also because many of these tools are built on top of popular open source frameworks such as React, which already has a vast user base.

    This is enabling a new kind of collaboration that is unlocking a lot of value for all the stakeholders involved. Inspired by how Figma reshaped the design process by allowing real-time commenting back in 2016 or how Google’s suite allowed real-time editing, there is a similar phenomenon taking place over the last year in software engineering.

    Visual, Real-Time and On the App

    The most obviously striking feature is that collaboration is happening on the app (or the app prototype) and is becoming increasingly visual. Writing or editing code in the command line is great, but it doesn’t necessarily help the developer to visualize what is happening. Vercel’s Next.js Live, for example, allows teams to chat, draw and edit.

    collaboration

    This also means that collaboration is happening on the app instead of through tools like email, Slack and Jira, leading to targeted feedback without having to toggle between multiple tools.

    Collaboration and Feedback Loops Become More Inclusive

    While developers often collaborate at the code level, non-developers’ feedback is often given at the design level. This is more often the case for internal tools (or apps), which typically account for anywhere from 20% to 40% of engineering bandwidth in organizations.

    For example, Appsmith today has thousands of developers self-hosting and deploying internal applications for users who are often business or operational teams like support, sales and/or finance, for example. Often, these business users don’t even know who has built the application. Real-time commenting via front-end frameworks facilitates collaboration between software engineering teams and their business counterparts who can now communicate directly, provide feedback and collaborate with their engineering peers. This close collaboration empowers all parties, increases efficiency and saves significant time while improving the overall quality of the software and ensuring that it meets expectations.

    AppSmith

    In addition, non-engineers don’t need to familiarize themselves with a new tool like GitHub or go through a painful replication issue on Jira involving a variety of screenshots or screen recordings. Sharing feedback can be done much more easily.

    Better Version Control and Feedback

    For developers, having the ability to visualize a particular branch of an application and give detailed feedback on it and then track it on GitHub or GitLab speeds up the development cycle. Netlify, for example, pioneered this when it launched Deploy Previews earlier this year. Netlify takes this feedback and integrates it into project management tools like Jira, Trello and many others in addition to GitHub and GitLab.

    collaboration version control

    We are seeing other companies, like Sturdy, building on this much-needed trend of real-time collaboration in app development.

    Collaboration is the Trend

    Great software is the story of teams expanding collaboration beyond developers and there is a lot of good tooling available to help achieve that. This trend should continue to gain traction in the years to come because it taps into a number of other underlying trends in the software development space.

    First, the explosion of alternatives in the backend-as-a-service space, in which Heroku and Firebase were early pioneers, means BaaS is embraced by many more organizations for a variety of use cases. This trend speeds up development because they present a much more tightly integrated ecosystem of services and organizations don’t have to worry about deployment, hosting, content delivery network (CDN) and/or authentication themselves, for instance.

    Second, the proliferation of APIs is driving the emergence of more complex applications built on a variety of data sources. Everything is connected to everything. Of course, this also means that a lot more data is available to support decision-making, and this leads to many different kinds of applications being created both for external as well as internal purposes.

    And finally, the larger low-code/no-code movement is creating millions of new citizen developers and blurring the boundaries between who is and isn’t a developer.

    Summary

    DevOps marked the start of the evolution of software development into a team sport, and collaboration is now accelerating beyond the boundaries of IT. Like DevOps, the result of this collaboration in the software development process will be better software that propels businesses forward created faster than ever before.

  • The Low-Code Tide is Rising

    The Low-Code Tide is Rising

    [pdf-embedder url=”https://devopsy.kinsta.cloud/wp-content/uploads/2022/02/hcl-low-code-tide.pdf”]

  • Low-Code SaaS Solutions Need Security at Their Core

    Low-Code SaaS Solutions Need Security at Their Core

    Faster integrations. Accelerated software delivery. Elevated user experiences. These are only three of the benefits organizations gain by incorporating low-code platforms, apps and solutions into software development and business process management.

    Low-code platforms aren’t new, but demand for the technology soared in the last two years as companies were challenged to meet stakeholder demand for more digital transformation. With low-code tools, companies find they can expand digital transformation efforts through faster business application delivery. In addition, the time it takes to innovate is dramatically reduced with low-code tools.

    Low-code solutions are no passing trend. In their recent report on global cloud revenue, Gartner predicted that by 2025, the use of low-code and no-code will “nearly triple,” adding that “70% of new applications developed by organizations will use low-code or no-code technologies, up from less than 25% in 2020.”

    Low-code solutions give organizations the ability to produce working solutions and integrations with more speed and agility than more traditional on-premises development. Integration used to be a labor-intensive IT process requiring custom development on both sides of the integration. As more organizations adopt a “buy versus build” approach to software development, they are turning to self-service and other solutions with “out of the box” functionality to increase speed and efficiency. In addition, the vendor-developed components of low-code tools also offer a better user experience.

    Rising Demand for Low-Code, Platform-based Solutions

    As organizations expand their product and service offerings, the demand for low-code, platform-based solutions will increase. SaaS and PaaS solutions with a low-code focus can be effective for organizations looking for accelerated functionality. Often these tools include pre-built models and templates that businesses can quickly implement and easily duplicate for flexibility and versatility.

    The ability to create seamless integrations with other applications is a must. Best-of-breed low-code platforms enable intelligent integration between multiple applications using graphical user interfaces (GUI) as well as industry-standard interfaces such as JSON and APIs within vendor-supplied environments. Intuitive visual user interfaces and drag-and-drop features allow businesses to customize the solution to meet their needs and preferences.

    But along with ease of use and rapid functionality, organizations must look for low-code tools with security built-in.

    Security: A Priority for Low-Code Tools

    Security must be a top priority for organizations using low-code tools in any capacity, from using a low-code platform for application development or using a no-code SaaS solution for business process automation.

    Anytime an organization introduces outside applications or any third-party API integration to an environment, the organization is entirely dependent on the vendor’s security implementation. This is especially true when combining various solutions to create a unified product or service. If the vendor doesn’t take security seriously, other parts of a solution could be exposed to risk because of a weakness in another area.

    Problems can get in either intentionally or unintentionally, as demonstrated with the recent Apache Log4j vulnerability. The bug in this commonly used routine was found to have massive potential for cybersecurity attacks. As CNET cautioned, “The vulnerability in the widely used software could be used by cyberattackers to take over computer servers, potentially putting everything from consumer electronics to government and corporate systems at risk of a cyberattack.”

    Ways to Remedy Security Risks of Low-code Tools

    Organizations can’t make assumptions about the security of every tool, solution or platform they bring into their environment. They must complete their own due diligence for security in the software development pipeline or any time a 3rd party app or tool is introduced.

    One critical step to addressing security is incorporating DevSecOps and shifting security left in the software development pipeline. The Log4j vulnerability put the need for DevSecOps in the spotlight. Taking a shift left approach and implementing security earlier and more often in the DevOps process can help to catch more potential vulnerabilities. It’s critical to introduce DevSecOps early in the development cycle, or organizations risk missing a bug or vulnerability. In the development cycle, security isn’t an antivirus scenario; all code must be scanned for vulnerabilities.

    Organizations also need to employ due diligence when exploring options and solutions to bring into their environments. Look for solutions with security at their core. Before integrating any low-code solution, examine the vendor’s approach to security.

    Some security measures to look for when considering vendors or solutions include:

    • All communications should utilize at least TLS 1.2 (transport layer security) and comply with industry standards for certificates and encryption keys.
    • All hashing should be using current accepted standards with HMAC, they should be enforcing security rules on passwords such as only storing password hashes and requiring 2FA if they interact directly with customer accounts.

    Low-code platforms and tools have the ability to accelerate digital transformation efforts without having to rely on hand-coded, on-premises solutions. The potential for time savings and cost savings is significant, but it’s important for organizations to ensure they’re not compromising security when choosing solutions.

  • Low-Code and the Rise of the Citizen Developer

    Low-Code and the Rise of the Citizen Developer

    Low-code technologies have become increasingly popular for helping businesses adapt to ever-changing environments quickly by allowing them to build, customize and deploy apps with little to no coding. At Low-Code/No-Code Virtual Summit, taking place on Nov. 18 at 9 a.m. ET, luminaries of leading organizations in the low-code community will share valuable insights on their digital transformation journeys and the role of low-code/no-code in their digital strategies.

    Attendees will get an intimate look at how organizations are embracing low-code technologies to advance their business while improving user experience. The virtual event explores the vast and growing ecosystem of technologies that are changing the face of application development, featuring sessions on:

    • The rise of the citizen developer
    • Security and compliance in low-code applications
    • How low-code is transforming software development
    • Low-code versus no-code
    • Low-code trends

    Low-Code/No-Code Virtual Summit features an exceptional lineup of low-code and industry experts, including:

    • Derya Sousa, co-founder and COO at Kianda Technologies
    • Venkat Thiruvengadam, CEO at DuploCloud, Inc.
    • Andrew Manby, head of product management at HCL Software
    • Asna Javed, hybrid cloud build team and developer advocacy leader at IBM
    • Eren Akbaba, cloud architect at IBM
    • Charles Kolodgy, cybersecurity strategist, advisor and educator at Techstrong Research
    • Daniel Topham, CEM for digital, strategic solution architect at Everbridge
    • Bala Madhusoodhanan, principal architect at TJX
    • Paul Porter, VP of sales engineering at Everbridge
    • Gunndarr Dotter, regional sales director at HCL Software
    • Amy Hart-Koullapis, communications systems specialist, global marketing and communications at World Vision International

    The virtual environment features an auditorium where attendees can watch the sessions by the experts and an exhibit hall lined with booths showcasing the latest solutions from leading low-code companies. In the exhibit hall, attendees can download resources and interact with partner sponsors.

    To start off the event on a high note, we have scheduled a yoga class at 9 a.m. with a certified instructor.

    Registered attendees will receive a link to access the virtual environment on-demand for up to 30 days after the live event.

    To check out the full agenda and to register for free, visit the Low-Code/No-Code Virtual Summit website.

  • Top Misconceptions About Low-Code Development

    Top Misconceptions About Low-Code Development

    Accelerating the pace of development has become one of the biggest goals in DevOps. After all, having teams speed the creation and modification of applications is supposed to be one of the primary advantages of DevOps pipelines. Yet, far too many DevOps teams run into speed bumps that can derail the process. For some, turning to alternative methods to generate and modify code can slay the beast of project deceleration, and that is where low-code platforms come into play.

    However, the waters are muddied by misconceptions about what low-code is and what it isn’t. Here, three industry experts share their own observations about these common misconceptions.

    Low-Code is Only for Citizen Developers

    “People often confuse low-code with no-code platforms,” said Richard Rabins, CEO, Alpha Software Corporation. “No-code platforms, which are driven by visual modeling and user interface builders, are aimed at citizen developers with little or no coding experience to quickly build applications.” Rabins makes some good points; no-code environments are designed to put the power of application development into the hands of a citizen developer, meaning those no-code platforms are optimized for simple workflows and not for teams. On the other hand, low-code platforms can integrate with deployment platforms, which helps expedite delivery while also enforcing consistency.

    Low-Code Makes Collaboration and Reusability Difficult

    “Over time, many developers have come to believe that low-code platforms were built for a single programmer working on a waterfall project,” said Deepak Anupalli, co-founder and VP of Engineering at WaveMaker, Inc. “Today, low-code platforms, like WaveMaker, offer development environments that integrate with code management tools, as well as APIs, to support the sharing of code and fostering team collaboration.” Anupalli’s point is that the majority of low-code platforms incorporate workflows that support team activities. What’s more, those platforms support scale-up, reuse of code and the ability to work within pipelines.

    Low-Code Prevents Custom Development

    “From the beginning, low-code was all about building applications with little or no code needed, creating the perception that low-code platforms did not lend themselves well to customization,” said Rabins. “However, nothing could be further from the truth. Developers are able to expand the functionality of low-code projects as the need arises. They can insert custom code, call APIs, integrate with other platforms, and so on.” Rabins points out that low-code doesn’t mean no-code, simply that low-code can generate code that can be modified and adapted as needed, supporting pipelines that deliver fully customizable applications.

    Low-Code Platforms are Only a Trend

    Many seem to think that low-code platforms are just a trend that will ultimately fade away as other technologies come to light. However, according to Business Wire, the low-code market will grow 44.4% by 2022 to reach $27.23 billion. Anupalli added that WaveMaker has experienced year-over-year growth since the company was founded.

    Leaders in the market today include Visual LANSA, GeneXus, Appian, Mendix, OutSystems, WaveMaker and Alpha Software. 

    Low-Code Solutions are Proprietary

    One of the leading assumptions about low code platforms is that they all use some type of proprietary programming language. That may be true for a few platforms, but many embrace open source ideologies and use common languages, such as Java, PHP, and C#. Take, for example, the RISE Editor, which enables users to output code based on models in a number of different languages. RISE is not alone in the industry; several other platforms embrace either open source or can create easily accessible code. VisionX and WaveMaker create in Java, allowing generated code to be edited with other Java IDEs.

    Low-code development platforms (LCDPs) have come a long way since the term was first coined by Forrester Research back in 2014. And yet, these numerous misconceptions remain, which may have slowed the adoption of LCDP in enterprises using DevOps pipelines. Dispelling these assumptions goes a long way towards helping application developers realize the benefits that LCDP can offer.