Insights from the Babbel engineering team
There are times during app development when you want to temporarily disable some functionality or enable it only under some conditions. For example, you work on a new feature that is not done yet, and it should not be accessible by everyone. Or you have a particular setting that enables extra functionality that is useful only during testing.
Change that only comes from the top can ultimately only deliver so much. What happens when women in tech drive the process, advocating for themselves? What results does that yield? Babbel is a window into that approach.
In the past, we introduced monitoring and alerting that tracks the technical status of our platform and services. However, we sometimes experience issues that our monitoring cannot detect. This could be team-independent or cross-team issues or even issues that do not have a technical reason. For example, two alerts in different teams might not appear urgent but combined they make an impact. To answer these questions, we have started working on Product Health monitoring.
Here is a short release notice. At Babbel, we’ve been using Code Climate successfully for a while, but we were unhappy about the lack of the Terraform provider for it.
Finally, we’ve decided to build our own provider and now it’s open-sourced.
One year ago I changed my career from a Recruiter to a Junior Software Engineer. The path was long and challenging but it was worth it! I am happy to share my experience by giving the answers to the most popular questions I get.
Companies should encourage and allocate time for their engineers to be able to contribute back to open-source. It does not only improve the product that they are contributing back to, but enhances the feeling of self-worth which in turn has a big positive impact on the well being of the engineers and the company itself.
“In learning you will teach, and in teaching you will learn.” Phil Collins
Although many developers working with React consider it an anti-pattern, occasionally, there is the need to listen and react to an event globally within a React component. As every good developer out there, you probably want to provide a unit test for this functionality. However, while implementing the test, you might face some troubles… Here comes this article trying to help you on your way through.