GDPR is a massive topic in the tech community with lots of work being required as well as limitations on what you can do to be compliant with it. We believe that it will have a massive effect on the tech landscape in the upcoming years as more and more court cases decide what is and what is not allowed.
Single Responsibility Principle (SRP) is probably one of the most well-known principles from SOLID. At its core is a desire to prevent classes from becoming overwhelming and bloated. While enabling the ability to change how a single thing works by only changing a single class. So the benefits of the Single Responsibility Principle are that you have an easier codebase to maintain since classes are less complex and when you wish to change something you only have to change a single class. In this blog, I will go through some ways to try and help avoid breaching the Single Responsibility Principle while doing code review.
As a non-technical founder, you can be worried when you're having a project built but do not know if it's good or not. We want to help non-technical founders better understand what is happening so they can make informed decisions.
Logging is a very important part of operating an application if you're unaware of what happened in your system you're unable to quickly and efficiently identify the issue. However, logging can open up some potential pitfalls. One of them being including secrets and other sensitive information within the logs accidentally. Twitter and Github both accidentally logged people's passwords in plain text. To help protect our users we've made it so that we automatically filter passwords out of the logs created via monolog. And we're going to share how we did it so you can also ensure your logs are also secret free.
In software development, free open-source software (FOSS) has always been important and without FOSS, IT would not be the same as it is today. It is hard to think of a company in this world today that isn’t relying on FOSS for part of its tech stack. For many developers, FOSS is a major part of being a developer and they feel like contributing to FOSS is something they, as a good developers, must do. Some loath the idea of commercial software. So it’s with this in mind, we feel like we should explain why we choose not to use the FOSS model. Instead, we have gone for commercial licensing.