A couple of days ago I was at the Dutch PHP Conference where I went to a talk about [Content Security Policies by Matt Brunt. Although we follow the OWASP top ten list, I never dived into them that much. We have written a bit about them before, but I want to go a little further since they are really handy when trying to prevent XSS attacks.
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.
Every year Ibuildings organises an international conference on PHP technology: the Dutch PHP Conference (DPC). Last week was already the 11th edition of our successful conference where some 630 developers, software architects and community members come together in the Amsterdam RAI.
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.
In order to focus on core activities, organisations often know very well which tasks they have to do themselves or can outsource. But as soon as it comes to the software that supports the same core business, there is strikingly less straightforward thinking about it.
Now that organisations are consciously making the transition from ‘business’ to ‘online business’, web applications and other software are becoming more and more decisive for their success. When choosing between ‘custom or standard software’, a mix is becoming more and more interesting, but how do you find the perfect balance?