We’d love to keep sharing a healthy dose of new insights, stories, advice and zero spam with you.
Micro frontends are an architectural pattern that has become a hot topic in recent years for many good reasons. It has helped organisations break complex UI applications into smaller, more manageable pieces, as well as enabling teams to work end-to-end across a well-defined product or business domain whilst maintaining a consistent user experience across the entire app.
In February, our CEO Mark wrote a blog post about what it’s really like to work at Cogent, which described why we’re taking the rather unusual step of publicly sharing our employee engagement survey results. Since then we’ve run another survey so, in the continued spirit of transparency, I wanted to share some of the insights we’ve gained.
At Cogent, we’ve helped businesses grow from pre-seed to scale-up and beyond. We’ve partnered with founders, and even founded businesses ourselves. We know what it takes to grow a business at each of those critical early stages. And, instead of keeping that to ourselves, we’ve done what Cogent does best, created something so scaling business can benefit.
Felienne Hermans recently gave a marvellous talk which relieved one of my lingering insecurities almost immediately – she told me that it was OK to spend time reading code, and that it was in fact a necessary precursor to being able to write code effectively.
It’s been interesting to watch the ways in which software companies are trying to bridge the conceptual and language gaps of designers and developers. There are frameworks, design systems, collaboration tools and so on that are ‘trying to connect designers and developers in a better way’. And, whilst I use these tools regularly, none of them come close to doing the actual work of listening and understanding the needs of ‘the other’.