In our online age, the time of serverless computing has also come in recent years. This offers great advantages for working in the cloud. Especially if the software for your organisation is designed and developed for this purpose. For new applications, the development of cloud native software should certainly also be a consideration. I would be happy to explain why.
No matter what kind of business software you’re working with, updating to keep up to date is always necessary. Also with custom software. Although you can make choices in your update and upgrade policy. But do this consciously, because the consequences vary greatly. And you notice that in the extent to which business software supports your users and business. And it also strongly determines how securely your organization works. Have you already made a choice?
Using APIs and SaaS solutions in the cloud offers organizations many opportunities. But there is also a downside to this development. Many companies and organizations lose sight of their software architecture. This can lead to proliferation of (emergency) solutions and fragmented data. Prevent this by reversing the development process. Start again with your own software architecture.
Nowadays there is a lot of talk about “Headless” and “Decoupled” Content Management Systems. It seems to be a new trend, but what is the difference with a traditional CMS and why should you choose for a headless or decoupled CMS?
You develop software together, as a software engineer and customer. This involves a series of translations from the business to the final software. The trick is to limit the number of translation steps, because with every translation you lose nuances. This is possible by bringing software engineers and clients closer together and actually having them develop together. With Gherkin, they can speak the same language and describe software behaviour (BDD). And build even more intensively together.
Are you already in need of technical ‘debt assistance’ for your business software? With the development of almost all software, a technical debt is built up, mainly to achieve results quickly. That doesn’t have to be a problem, as long as you handle it well and consciously.
Mobile apps are useful, but also a growing problem. More and more organizations, events, services and locations have their own app and they all want you to install their app on your smartphone or iPhone. That approach and proliferation is untenable. Fortunately, the Progressive Web App (PWA) offers a solution.
In software development we can learn a lot from production companies. Especially to make software development better and more efficient and to use it more purposefully for the success of organisations. The per piece production model offers a solution, also for software.
Because of the digital transformation that organizations make, they often unlock information via beautifully designed websites and applications. Those who look and think further, sometimes take the next step: access via an API (Application Programming Interface). This offers many opportunities, but organizations often see it as a difficult step.
When custom business software becomes obsolete, many organizations choose almost automatically to have completely new software built. Renovation is often not considered. While in 70 percent of the cases it is more successful and cheaper. It is an interesting option, which I would always consider. Because that old application often has great treasures hidden in it.