What problem are we trying to solve? JavaScript runs in a single thread per web-page in the browser. This limitation prevents CPU intensive work on client side (encoding/decoding, complex calculations, etc…). Let’s see how WASM and WebWorkers help pull through these problems by porting native C/C++ libraries to the web and interact with them concurrently. […]
Most of our projects use codecov.io to check code coverage and improve review process. But high code coverage value itself is not telling anything about quality of the code and tests, so we always try to improve the way we test our products. You can read about our mutation testing practices and in this article […]
What is Mutation Testing? Mutations are automatically seeded into your code Tests are run If your tests fail -> the mutation is killed pass -> the mutation lived The quality of your test suite can be measured by the percentage of mutations lived. In other words, your application code is automatically modified. When the production […]
Every time we start a new project we do a retrospective and look back at our previous projects and try to evaluate which technical choices were good and where we might have gone wrong. Usually we are pretty happy with our Kotlin + Spring Boot + Postgres based backend, but at least I personally have constantly re-evaluated React/Redux: is this the best […]