CTO at Mews, sportsman (basketball, streetball, squash, bike, swimming), energy-drink lover, currently on-hold due to high blood pressure.
In December 2021, our tech team reached 100 people. That's almost one-third of Mews. Nine years ago, when I started at Mews, I could hardly imagine not only such a big team, but also product surface that we'd be working on. One might rightfully ask why we need such a big team?
If I were a software engineer nowadays, I'd surely want to know how the company I'm about to join stands in this test. We participated in the survey, but it might be valuable to elaborate on our answers and give more details so that it is not just a single number.
It is duty of a manager to treat everyone fairly and in timely manner. Compensation should be given for the work and contribution that the person delivers to the company. It should not depend on negotiation skills and boldness of the employee to ask for more. Unless their job is a negotiator :).
Everybody in tech world understands CI as continuous integration, but the other and maybe even more important meaning of this abbreviation is continuous improvement. It is easy to say that we encourage progress and learning, but as people get overwhelmed with daily tasks, these more abstract goals are pushed to
In Mews, on our journey towards continuous product delivery, we faced an unanticipated, but really important issue for our customers; promptly informing them about updates and new features of the system, also known as "release notes". Solving this became a precondition for us going full steam ahead with continuous delivery.
In Mews, we are big fans of code review. Not only because it prevents bugs, but also it serves as a natural place for information sharing. For newcomers, it's the easiest way how to quickly get a picture of what's currently being worked on and how other developers solve their
