Fozzy Group

Why is exercise often discussed in relation to brain health and cognition? 🧠 This is something I’ve been reflecting on recently, particularly from both a cognitive neuroscience and physiological perspective. From a physiological standpoint, exercise is known to support processes such as cardiovascular health and blood flow throughout the body. Because the brain relies heavily on oxygen and nutrient supply, researchers have become increasingly interested in how physical activity may also relate to cognitive health and ageing. One brain region often discussed in this area is the hippocampus, which plays an important role in memory formation and retrieval and is known to be sensitive to ageing. Research has suggested that exercise may be associated with factors linked to brain health, including blood flow, neuroplasticity, and broader cognitive wellbeing. However, the relationship between exercise and cognition is complex and likely involves multiple interacting physiological, psychological, and lifestyle-related factors rather than a single direct pathway. What I personally find particularly interesting is that many people describe exercise as influencing not only physical wellbeing, but also aspects of mood, routine, motivation, and mental clarity. In everyday life, habits such as consistency, movement, stress reduction, and overall physical health may indirectly support cognitive wellbeing over time. As someone currently researching memory and cognition, I find this area especially interesting because it highlights how closely connected brain health is to broader physiological and lifestyle-related processes. This post is part of my “Understanding Memory: Brain Series” 🧠, where I explore how different brain regions support memory. Follow for more insights from this series. [Image was designed by Freepik - Magnific.com ] #Memory #Neuroscience #BrainHealth #Exercise #HealthyAgeing

Last week, I attended the Practical AI Upskilling workshop by Women in Tech®UK , hosted by Google London in collaboration with Turing College / Boom Training . What I really valued was that this wasn’t theory - it was real use cases, real challenges, real implementation. 💡 The ultimate takeaway: If you’re just using AI to do your old tasks faster - you’re already behind. The real opportunity isn’t efficiency, it’s reinvention: moving from using tools to embedding AI into how teams think and operate A huge thank you to the fantastic speakers for sharing real, practical examples of AI in action: John Ridpath (Co-Founder of Branch https://www.joinbranch.co/ - a fantastic initiative supporting women through the transition into working motherhood) shared how AI is embedded into their day-to-day work — not as a tool, but as a natural part of how the team operates. Benas S. delivered a brilliant live demo showing how Boom Training automated their entire funnel - AI agents handling 1,000+ calls and 42 interviews, with 0 lines of human-written code! A big thank you to Nina Tumanishvili and the Women in Tech®UK team for bringing together such a high-quality event - the energy in the room was incredible!

Nx monorepo is not a silver bullet ⚠️ In the right conditions, it acts as a multiplier. In the wrong ones, it introduces significant complexity and slows teams down. I’ve seen both scenarios in practice. Nx tends to work well when: - multiple teams share UI components, contracts, and tooling - cross-project changes are frequent enough to justify a single source of truth - domains and ownership are clearly defined - architectural boundaries are actively enforced 👉 In such setups, Nx provides: - consistent tooling and CI processes - simplified cross-application refactoring - a structured platform layer for shared UI and infrastructure Example: We had several Angular applications with identical integrations (auth, API, analytics, UI). Before Nx, this resulted in duplication and divergence of logic. ⚡️ After migrating to Nx: - shared logic was extracted into libraries with enforced boundaries - platform-level changes were implemented once and reused - new applications could be bootstrapped significantly faster - CI pipelines executed only for affected projects At the same time, I’ve seen Nx monorepos become a source of systemic issues: - excessive and uncontrolled dependencies between projects - slow and unreliable CI pipelines - lack of trust in builds near release cycles - unclear ownership of shared code - steep onboarding due to repository scale The issue is not Nx itself. It is adopting a monorepo without the necessary structure and operational discipline. A monorepo amplifies existing practices: well-defined domains, ownership, and CI/CD → improved scalability 📈 unclear boundaries and weak processes → increased complexity 📉 Before deciding on monorepo vs polyrepo, it is worth asking: - Is there a real need for shared change and shared tooling? - Are domains and ownership clearly defined? - Can existing CI/CD and review processes handle tighter coupling? Nx monorepo is a good fit when ⚙️ - there are 3+ teams - multiple applications share domains or platform components - there is a commitment to enforce boundaries and ownership - reuse and standardization are explicit goals It is less suitable when: - teams are small and processes are not yet mature - domains are largely independent - ownership of shared code is unclear - there is limited capacity to maintain CI and architecture If the honest answer to these questions is “not yet”, a monorepo is not a strategy - it is a risk. How do you see it in your experience: are monorepos adopted too early, too late, or for the wrong reasons? #Nx #Monorepo #SoftwareArchitecture #EngineeringManagement