Business Application Development

Business Application Development
What opportunities can low-code offer developers?

Top Answer : Low-code provides a way to optimize productivity for developers. I think the fundamental issue we are facing today is while software creating the differentiators and competitive advantage for companies in every business domain, there is a lack of skilled developers to cater the demand. . Whomever we can recruit and retain, we need to find ways to make them more productive.  The problem is that current low-code platforms are built for semi-technical users, or “citizen developers.” So we are trying to make low-code interesting for professional developers to then make them more productive in our low-code platform ‘Choreo’. Because when it comes to development, there are interesting tasks involved but there are also boring tasks like accessing a database or doing data mapping. So we’re looking at how we can offload some of those repetitive, less interesting tasks onto low-code.

What are your thoughts on SaaS management platforms (SMP)?

Top Answer :

Related Tags
Business Application Development
Architecture & Strategy
Requirements & Design
Testing, Deployment & QA
Mobile Development
Selection & Implementation
Business Analysis
Applications Vendor Landscapes
Data Center
Public and Hybrid Cloud
Business Applications
Crisis Management
Data & Business Intelligence
Artificial Intelligence
Business Intelligence Strategy
Data Management
Enterprise Integration
Machine Learning
Data Lake
Big Data
Data Warehouse
Disruptive & Emerging Technologies
Virtual Reality
Digital Innovation
Augmented Reality
End-User Services & Collaboration
Collaboration solutions
End User Equipment
End-User Computing Devices
Endpoint management
Productivity tools
Document Management
End-User Computing Applications
End-User Computing Strategy
Voice & Video Management
Continuous Integration
Technical Product Management
Continuous Deployment
Quality Assurance
Customer Relationship Management
Enterprise Content Management
Customer Success
Enterprise Information Management
Enterprise Resource Planning
Marketing Solutions
Human Resource Systems
Product Recommendation
Risk Management
SOX Compliance
Governance, Risk & Compliance
Infrastructure & Operations
Cloud Strategy
I&O Finance & Budgeting
Operations Management
Network Management
DR and Business Continuity
Server Optimization
Attract & Select
Cost & Budget Management
Manage Business Relationships
Organizational Design
Program & Project Management
Train & Develop
Talent management
Performance Measurement
Organization Structure
Manage & Coach
Availability Management
Financial and Vendor Management
Service Desk
Management Tools
Enterprise Service Management
People & Process
Process Management
Asset Management
Project & Portfolio Management
Portfolio Management
Project Management Office
Confidentiality, Integrity, Availability
Secure Cloud & Network Architecture
Endpoint Security
Data Privacy
Identity and Access Management
Security Operations Center
Security Strategy & Budgeting
Security Vendor Landscapes
Threat Intelligence & Incident Response
Threat & Vulnerability Management
Vendor Management
Infrastructure Vendor Landscapes
Strategy & Operating Model
Business Continuity
Architecture Domains
Tool Recommendation
Where do you see the industry evolving when it comes to developing or deploying secure products from the start?

Top Answer : At the end of the day, balancing security with user experience is what we want to do. And I think the only real good example of that today is Apple with touch ID and face ID. Everyone is used to that: you look at your phone and it automatically unlocks. So I think that's going to continue to evolve, whether it's some sort of biometrics or fingerprints, etc. I'm sure someday it will be some chip embedded in you, that's probably the future. I could see passwordless authentication where you’re just getting Azure MFA notifications on your Apple watch and you just have to click okay to authenticate.

How do you prevent your hardware from containing any unintended loopholes or access points upon shipment?

Top Answer : We're doing the same basic stuff everybody else is doing as far as code testing. And we do basic apps security, penetration testing code reviews, we get someone to look at it and do background, etc., so I think everyone feels comfortable with the code itself. The issue is that we have such a narrow focus on whether the CI/CD pipeline is good. If you're just looking at that then what happens when you don't have any dev/prod segmentation or something? That's more the issue I see: "The code is great and we pushed it to dev and then it sat there. But the dev systems are not segmented from prod and now port 22 is open to the world because someone didn’t put a rule in to close it."

As Shadow IT is exacerbated by low-code, how do the most successful security teams get ahead of the risks involved?

Top Answer : If you have a certified platform to build low-code applications, then the central enterprise architecture team and security architect can coordinate and incorporate the relevant security policies into that particular platform. The danger lies in people using standalone low-code tools and then building applications here and there. Even writing an Excel macro can be treated as a Shadow IT application. The other issue with the Shadow IT applications is there's no maintenance. If someone writes a Shadow IT application that is not part of the corporate standard or deployment guidelines, and then that person leaves the organization, then it's an issue. Now nobody knows how to maintain that code. We have to find the source codes and figure out how to enhance it. That's where building things outside the standard corporate guidance becomes an issue in addition to the security issues involved. Having a good platform will solve most of these issues and standardize the way individual groups build applications and make it part of the enterprise architecture—a standard bill system, standard deployment system, as well as documentation of most Shadow IT applications and their capabilities.

In your experience, how do the most successful organizations overcome the low-code/pro-code chasm?

Top Answer : There's no proper solution. For most organizations, these two teams are working in silos. Some smart organizations are using Application Programming Interfaces (APIs) as a way for these teams to communicate, but it is not that successful. And if you've talked to developers, they’ll tell you about the frustration.  Most of the time low-code platforms are picked by technology leadership and the developers are asked to use them, it’s not their choice. Then the developers end up spending a lot of time. For example, one development team told me they had to click and wait for a certain amount of time. The efficiency is really low, as everybody is now discovering. That's why as a company we are trying to build a platform for our customers first and then make it a commodity and community after that.