At the time, the term “T-shaped” was starting to become more common in product and engineering conversations. The idea? Someone with deep expertise in one area (say frontend), but with broad working knowledge across many (such as backend, product thinking, security, threat modeling, performance, deployment, etc.). In practice? It meant stepping into ambiguity, learning fast, and finding your own path through it.| Mews Developers
Welcome to the Mews R&D mini podcast series! Bite-sized conversations with the people behind our tech – short interviews, fresh insights, and more guests from across Mews R&D. Stay tuned for stories, ideas, and a peek behind the curtain of how we build. In this episode, our R&D Community Lead, Jan Meissner, talks with Adi […]| Mews Developers
In software development, delivering a high-quality product is a continuous challenge. Despite thorough testing processes, automated checks, and strict acceptance criteria, bugs still find their way into releases.| Mews Developers
Struggling to measure design system adoption? Discover how we built a clear, data-driven metric that really works — with practical tips and code snippets you can use too!| Mews Developers
The Mews way of migrating from Monolith to Microservices, reimagining the entire application from the product POV.| Mews Developers
The Mews way of migrating from Monolith to Microservices, reimagining the entire application from the product POV.| Mews Developers