People tend to associate the idea of performing A/B tests to creating a couple of layouts for a company’s landing page and comparing the conversion rates for each one. While this is an important use case, A/B testing is much more than testing web

My blog series dedicated to the use of SOLID principles is back, this time to talk about the interface segregation principle. For reference, here are the five principles once again!

I am pretty sure we have all heard of Transport Layer Security (TLS) at some point. TLS is the protocol that provides security for HTTP (yes, it is the S in HTTPS!). It guarantees a secure communication pipe between a client (being it your browser

Today, I will be talking about availability. More specifically, Denial-of-Service protection. In a nutshell, as a network security guy working for a faster mobile content delivery, I will demystify the idea that DoS attacks are UDP’s fault, even

Measuring the user experience is key to a successful app and a bad user experience can cost a lot of money. Therefore, you should always assume app improvement as a continuous process that includes monitoring and testing.

This is the third post of a series dedicated to the use of SOLID principles at Codavel. As you remember, we're showcasing SOLID principles in the light of a “make it work, make it right, make it fast” philosophy. So, take this post with a little

You have probably heard about QUIC. Even if you haven’t, it’s highly likely that you have already used it: Google services on Chrome have been using QUIC for a few years now. QUIC standardization process is also very close to being completed. QUIC

It wasn’t that long ago that Internet was a repository of information. We would mostly access static content from web pages with small amount of traffic and serving just a few local regions. But that reality quickly changed.

Software must be delivered with high quality to make sure that every iteration with customers and/or users provides valuable feedback. This feedback should be with respect to the features that truly matter for the customer, instead of chasing bugs

Image source You and your team just had a brilliant idea for a software that solves your client's problems and you're ready to start. How do you plan the whole project?