Podcasts about Aalto University

Juni Sun Neyenhuys (*1997) arbeitet an der Schnittstelle von Materialwissenschaft, Zirkularität, konzeptionellem Design und Storytelling. In ihren Projekten nutzt sie natürliche Ressourcen für neue Anwendungen in ökologischen Kreisläufen. In Zusammenarbeit mit Stakeholdern aus Industrie, Forschung und Bildung entwickelt Juni Materialien, Produkte und Konzepte, die im Einklang mit der Natur stehen und darauf abzielen, ungeschlossene Produktkreisläufe zu schließen. Sie studierte Produktdesign an der Universität der Künste Berlin sowie Textil- und Materialdesign an der Kunsthochschule Weißensee und entdeckte dort ihre Faszination für Algen und ihr Potenzial. Seit 2018 arbeitet Juni Sun Neyenhuys an algenbasierten Materialien, unterstützt durch ein Studienstipendium der Studienstiftung des deutschen Volkes sowie ein Startup-Stipendium der DesignFarm Berlin. Im Frühjahr 2020 unternahm sie eine Forschungsreise nach Japan, um verschiedene Handwerksbetriebe zu besuchen und tiefer in die Materialkultur und traditionelle Handwerkskunst einzutauchen. Der Einsatz vergänglicher Materialien inspirierte sie tief und führte dazu, dass sie das Materialinnovations-Startup mujō (jap. = Sinn der Vergänglichkeit) mitgründete, das sich auf die Entwicklung von biologisch abbaubaren Verpackungsmaterialien auf Algenbasis konzentriert. Nach ihrem Bachelorabschluss im Jahr 2021 gewann mujō den „make tomorrow new award“, was die Weiterentwicklung der Technologie und des Produkts ermöglichte – mit dem Ziel, die Verpackungsindustrie zu revolutionieren. Aktuell studiert Juni Sun Neyenhuys im Masterstudiengang Contemporary Design an der Aalto University in Helsinki und ist Mitgründerin des Disruptive Materials Institute in Berlin. 2025 wurde sie vom Rat für Formgebung als Newcomerin des Jahres ausgezeichnet.

Sebastian Pfeiffer, Managing Director @ Impossible Cloud NetworkSebastian Pfeiffer is the Senior Director of web3 Growth at Impossible Cloud Network, where he is responsible for developing and implementing the company's growth strategy. His focus includes designing decentralized business architecture, tokenomics, legal frameworks, and stakeholder alignment.Before joining Impossible Cloud, Sebastian was a Consultant at Boston Consulting Group (BCG), specializing in strategy development and execution for globally recognized companies across various industries, with a focus on social impact and industrial goods. He holds dual Master of Science degrees in Strategy and Corporate Development from Aalto University and Universität zu Köln.LinkedIn:https://www.linkedin.com/in/sebastian-pfeiffer/

Sebastian Pfeiffer, Managing Director @ Impossible Cloud NetworkSebastian Pfeiffer is the Senior Director of web3 Growth at Impossible Cloud Network, where he is responsible for developing and implementing the company's growth strategy. His focus includes designing decentralized business architecture, tokenomics, legal frameworks, and stakeholder alignment.Before joining Impossible Cloud, Sebastian was a Consultant at Boston Consulting Group (BCG), specializing in strategy development and execution for globally recognized companies across various industries, with a focus on social impact and industrial goods. He holds dual Master of Science degrees in Strategy and Corporate Development from Aalto University and Universität zu Köln.LinkedIn:⁠https://www.linkedin.com/in/sebastian-pfeiffer/

In this wonderfully esoteric yet very important episode of Guerrilla History, we bring on Alejandro Pedregal to discuss his marvelous co-authored historical article The Early Socio-ecological Dimensions of Tricontinental (1967–1971) : A Sovereign Social Metabolism for the Third World.  This piece was published in one of our favorite journals, a resource that you really should all be utilizing, Agrarian South: Journal of Political Economy.  In this discussion, we talk about OSPAAAL, the Cuban Third World solidarity institution and in particular its magazine Tricontinental, the way it framed sovereignty and the implicit ecological messaging within.  A fascinating conversation, and one which we think you will find a lot of use in! Alejandro Pedregal is a Research Council of Finland Fellow, and is based at Aalto University.  You can keep up to date with Alejandro's work by checking out his institutional page from Aalto University, and by following him on twitter @AlejoPedregal Help support the show by signing up to our patreon, where you also will get bonus content: https://www.patreon.com/guerrillahistory 

Welcome to The Spark—your weekly creative pick-me-up from The Creative Boom Podcast. Every Thursday, we bring you a shorter, snappier episode filled with inspiration, creative news, and practical tips to carry you through the week. Whether you need motivation or insights, we've got you covered! This week, we welcomed Joseph Parsons to the podcast. By day, Joseph is a freelance graphic designer, and by night, he takes to the stage as a stand-up comedian. His dual career path sparked a fascinating discussion about balancing two passions: navigating the challenges of freelancing and the unexpected parallels between pitching design ideas and performing stand-up comedy. This episode is for you if you've ever juggled different roles in your creative journey. Joseph shared his thoughts on how the industry is changing, including the impact of the Government's IR35 legislation on freelancers and small businesses. We also explored how comedy has evolved, with platforms like social media offering new opportunities for comedians to find success outside traditional routes. Joseph's upcoming tour, Re-Designed, is a brilliant blend of his experiences in comedy and design—be sure to check it out for a good laugh and some relatable industry insights. This week's creative news takes us on a journey of nostalgia and innovation. In Finland, Aalto University is unveiling Nokia's design archive on 15 January, celebrating the brand that defined the mobile world in the '90s. From the iconic 8110 "banana phone" to the customisable 3210, the archive is a treasure trove of design sketches, marketing materials, and audio recordings, offering a rich blend of inspiration and history. Meanwhile, Cornish landscape artist Dianne Griffiths has won the 2024 People's Choice Award for her atmospheric painting Driving Home. This evocative depiction of a Texaco petrol station under a starry sky captivated voters and has even been purchased by the petrol station itself. In tech news, Apple is rumoured to be working on its thinnest phone yet, the iPhone 17 Air. Combining sleek design with advanced technology, it's shaping up to be a bold step forward in minimalist tech. Our Spotlight segment this week celebrates the 25 most admired graphic designers of 2024, as voted for by the design community. From bold innovators like Jessica Walsh to typographic legends like Astrid Stavro, these creatives are shaping the future of visual culture and leaving a lasting impact on the industry. The full list is a testament to the diversity and brilliance of today's graphic design scene. Our Book of the Week is Beyond the Wall: East Germany, 1949–1990 by Katja Hoyer. It offers a fresh look at life behind the Iron Curtain. This detailed history reveals the complexities of the GDR, from its Marxist roots to its collapse, blending personal stories with political insights. A must-read for history buffs! For our Tip of the Week, we look at networking and why it should be your priority in 2025. Networking is about building real connections. Start small—ask simple questions like, "What brought you here?" Follow up afterwards to keep the relationship alive. Authenticity is key. Networking isn't about selling yourself—it's about making new friends. On Monday, our guest will be Jessi Brattengeier, creative director at The New York Times. She will share her inspirations, processes, and aspirations and give us a really interesting look behind the scenes at one of the world's most prestigious publications. And then, instead of The Spark on Thursday, we've got a Christmas Special for you, featuring ten former guests of The Creative Boom Podcast, all helping us get into the festive spirit. Until then!

Today, you'll learn about an ancient diagnostic tool getting an AI upgrade, the world's slipperiest surface, and some insight into the minds of everyone who loves this show! Healthy Tongue•“Eyes may be the window to your soul, but the tongue mirrors your health.” University of South Australia. 2023. •“Ancient tongue diagnosis for the 21st century dental hygienist.” by Kathryn Gilliam. 2023. •“Analysis of Tongue Color-Associated Features among Patients with PCR-Confirmed COVID-19 Infection in Ukraine.” by Liudmyla Horzov. 2021. Slippery Surface•“Droplet slipperiness despite surface heterogeneity at molecular scale.” by Sakari Lepikko, et al. 2023. •“Slippery Science: Crafting the World's Most Water-Repellent Surface.” by Aalto University. 2023. Curious for Answers•“Curiosity evolves as information unfolds.” by Abigail Hsiung, et al. 2023. •“Unraveling Curiosity: Why We Savor the Suspense and Shun Spoilers.” Neuroscience.com. 2023. Hosted on Acast. See acast.com/privacy for more information.

In this podcast, Dr. Valentin Fuster introduces a state-of-the-art review on "Sudden Death in Obesity," exploring its mechanisms and management. Expert contributors from Cedars-Sinai Medical Center and Aalto University discuss key concepts, clinical characteristics, arrhythmia mechanisms, and therapeutic implications of this critical health issue.

Suzanne Mooney is a visual artist originally from Ireland, working with photography, moving image and found objects. She is currently a lecturer at the Academy of Fine Art, Helsinki, and a Doctoral candidate at Aalto University, delving into the connections between photography and glass.Watch the video of the episode on youtube @thevisitpodcast Hosted on Acast. See acast.com/privacy for more information.

Academics from everywhere experiment, collaborate, and even interpret our stories of "This one time at Burning Man."In this episode, Stuart talks with people from Burning Nerds, an annual gathering of academics in Black Rock City. They keep it light, though; not too many unnecessarily fancy words. Dr Jukka-Pekka Heikkilä shares about the Open Strategy management technique used by Burning Man Project that gives more power to the people. Bryan Yazell and Patricia Wolf of University of Southern Denmark report on using Flash Fiction in BRC to develop a new subgenre of sci-fi called climate fiction (‘cli-fi'), stories that are less dystopian, even less utopian, more protopian (fancy word) about society that improves over time, rather than transcending all it's problems or descending into dysfunction.Professor Matt Zook of University of Kentucky extols the unique aspects of Black Rock City, from materiality to temporality, to being a place apart. He and Stuart explore the interplay between digital and physical spaces, and what about community actually makes it good.Then Jukka-Pekka Heikkilä returns to reveal how the Burning Stories project, now in its 6th year of tracking tales, is now a cultural repository, and is training a gifted AI on how Burners be Burning.jukkapekka.comsdu.dk/en/persons/yazellsdu.dk/en/persons/pawogeography.as.uky.edu/users/zookburningman.org/programs/philosophical-center/academicsregionals.burningman.org/european-leadership-summitburning-stories.comkk.org/thetechnium/protopiasdu.dk/en/paca-at-burning-man-festival-2024 LIVE.BURNINGMAN.ORG

How do our brains respond to love? Guest: Dr. Pärttyli Rinne, Researcher in the Department of Neuroscience and Biomedical Engineering at Aalto University in Finland Scott's Thoughts: Who won the debate last night? Guest: Scott Shantz, CKNW Contributor View From Victoria: Leader's have their say and debate the issues We get a local look at the top political stories with the help of Vancouver Sun columnist Vaughn Palmer Why is Hurricane Milton so concerning? Guest: Dr. Sean Waugh, Research Meteorologist for the National Oceanic and Atmospheric Administration's Severe Storms Laboratory and Storm Chaser The risks of texting and walking Guest: Scott Shantz, CKNW Contributor Battling to be the MLA for Surrey-Cloverdale? Guest: Mike Starchuck, BC NDP Candidate for Surrey-Cloverdale Guest: Elenore Sturko, BC Conservative Candidate for Surrey-Cloverdale Learn more about your ad choices. Visit megaphone.fm/adchoices

How do our brains respond to love? Guest: Dr. Pärttyli Rinne, Researcher in the Department of Neuroscience and Biomedical Engineering at Aalto University in Finland Learn more about your ad choices. Visit megaphone.fm/adchoices

Mikko Silliman, Assistant Professor, Aalto University, Department of Economics, joins Paul E. Peterson to discuss Silliman's latest research, which looks at the impacts on students who choose a vocational academic path. "Labor Market Returns to Vocational Secondary Education," co-written with Hanna Virtanen, is available now. https://pubs.aeaweb.org/doi/pdfplus/10.1257/app.20190782

The Aesthetics of Martial Arts, by Dr Max Ryynänen (Aalto University, Espoo, Finland). Paper given at the 2024 Martial Arts Studies Conference at Cardiff University.

Roberto Peña Castro es un emprendedor mexicano y fundador. Estudió Negocios Internacionales en el Tec de Monterrey y cuenta con estudios en Aalto University y Harvard Business School. Durante su trayectoria, ha sido parte de empresas como Elica, Proméxico y Toilet Board Coalition. En 2019, entró a trabajar en Google como Account Manager, al mismo tiempo que lanzó MØBAR, una empresa de barras de mixología para eventos. En 2019, Roby combinó su experiencia como PYME y su conocimiento en tecnología para fundar Leadsales, un CRM diseñado para aumentar ventas a través de WhatsApp, Instagram y Facebook. Su visión es simplificar y mejorar la comunicación empresarial mediante soluciones digitales. A la fecha, Leadsales cuenta con más de 2500 clientes y ha levantado capital de inversionistas como Berkeley SkyDeck, Ulu Ventures y Blue Pointe Ventures. Roby es un emprendedor que nos enseña que, picando piedra, se pueden construir negocios enormes.

Tuomo Laine is the CEO and co-founder of Twice Commerce, which provides software to help its clients unlock a range of circular business models. Tuomo is known for being straightforward and action-oriented, and for his dedication to using entrepreneurship for societal good. He is a member of the Unreasonable Group Fellowship, and is occasionally invited to lecture at Aalto University, to share his venture building experiences. Twice Commerce's mission is to uncouple economic growth from the extraction of new materials, and it helps a broad spectrum of clients, from large retailers to individual sellers. The platform aims to enhance the value of any kind of object – by extending product lifecycles, unlocking more usage and sales from each item, conserving resources, improving value chain gross margin and reducing the need for new manufacturing. This is all about creating more value through circularity, not finding ways to reduce quality or reduce the pay for workers. Twice Commerce's clients include Decathlon, Rab Outdoors, Intersport, Motonet and many others, covering clothing, outdoor equipment, tools and much more, and by enabling improvements to the bottom line, Twice Commerce helps clients align profitability with environmental stewardship. Tuomo and his colleagues are getting to the crux of how to redesign the typical one-way commerce software to facilitate circular solutions and to address the elements that are adding cost, complexity or dysfunctionality. This is all about unlocking productivity – not just labour productivity, but thinking about how to leverage more value from the inputs you've invested in every unit that comes off the production line.

Welcome to the 71th episode of Decode Quantum, and a new one in English after Jay Gambetta from IBM. This time, Fanny Bouton and Olivier Ezratty host Jan Goetz, the CEO of IQM, the famous Finish superconducting qubits startup.Jan Goetz is the CEO and cofounder of IQM which was launched in 2019. Before that, he got his PhD at TUM (Technical University of Munich) in 2016. He conducted his work as a researcher at Walther-Meissner-Institute (WMI) in Germany (Garching, near Munich) working on the characterization of superconducting circuits.  After that, he was a post-doc at Aalto University, Finland, from 2017 to 2019 and a Marie Curie fellow. All his history in research is around superconducting qubits as we'll discover.

Welcome to the 71th episode of Decode Quantum, and a new one in English after Jay Gambetta from IBM. This time, Fanny Bouton and Olivier Ezratty host Jan Goetz, the CEO of IQM, the famous Finish superconducting qubits startup.Jan Goetz is the CEO and cofounder of IQM which was launched in 2019. Before that, he got his PhD at TUM (Technical University of Munich) in 2016. He conducted his work as a researcher at Walther-Meissner-Institute (WMI) in Germany (Garching, near Munich) working on the characterization of superconducting circuits.  After that, he was a post-doc at Aalto University, Finland, from 2017 to 2019 and a Marie Curie fellow. All his history in research is around superconducting qubits as we'll discover.

Researchers at Aalto University in Finland have discovered that believing an artificial intelligence is helping us can significantly boost our performance, even if the AI is unreliable or doesn't exist. In an experiment, participants who thought they were receiving AI assistance showed improved performance in a letter recognition task, regardless of whether the AI was reliable or not. This "artificial intelligence placebo effect" has profound implications for evaluating AI systems, as it's hard to discern whether improvements stem from the AI itself or people's belief in its effectiveness. --- Send in a voice message: https://podcasters.spotify.com/pod/show/tonyphoang/message

A Finnish startup has developed a nutrient catcher that is installed in wastewater management systems. The wastewater treatment equipment is able to separate and collect all excess nutrients from concentrated wastewaters, which can then be recycled and sold back to the fertilizer industry, making businesses more profitable, mitigating eutrophication, and enhancing local food security. NPHarvest, a spin-off from Aalto University, has raised €2.2M to take its proprietary nutrient catcher machine to the market. The round was led by Nordic Foodtech VC, with participation from Stephen Industries and Maa- ja vesitekniikan tuki ry. The round consists of a €1.3M equity investment and a €900.000 grant from the Finnish Ministry of the Environment and their RAKI program. NPHarvest to tackle wastewater NPHarvest has developed a novel and soon patented hardware solution for collection and recycling of nutrients from wastewater. With the new funding, NPHarvest is going to build the first commercially ready Nutrient Catcher, ready to be installed in their clients' facilities. Thanks to the process' modular design, the Nutrient Catcher can scale to different use cases and fit different facilities while keeping the production costs as low as possible. "Our process is much more energy and cost-efficient and easier to operate than the current solutions. Our end product is ammonia salt, which is commonly used in the fertilizer industry. We are very excited about bringing this technology to the market after years of research and development, bringing sustainable and affordable recycled nutrients and fertilizers to the market," says Juho Uzkurt Kaljunen, CEO and founder of NPHarvest. Nutrient fertilizers are vital for securing food production. However, excessive amounts of fertilizers, such as nitrogen and phosphorus, end up in the environment via wastewater or through nutrient leaching from agricultural areas. Both cause pollution of the ground and eutrophication in seas and lakes, which in turn causes overgrowth of algae and weeds, especially toxic blue-green algae, depleting oxygen and killing animal life. Wastewater is also responsible for around five percent of all greenhouse gas emissions. Losing valuable nutrients in wastewater is a missed opportunity for the whole agricultural ecosystem. Fertilizer prices are volatile and they need to be imported from abroad, decreasing self-sufficiency. The inability to remove excess nutrients from the ecosystem will also gradually lead to soil contamination, as farmers prefer using fossil-based mineral fertilizers or nutrient-rich manure. However, too much nutrients might actually result in nutrient deficiencies in plants. NPHarvest's hardware can catch up to 90 percent of the excess but valuable nutrients from wastewater. Once the technology has separated the nutrients, they can be taken back to the fertilizer companies. NPHarvest's process also uses very little energy, as it doesn't require heating or pressure increase, reducing the costs of the process even further. "No one has done nutrient catching on a real commercial level, which made us as foodtech investors impressed with NPHarvest and its unique technology. Ensuring food security while protecting the environment is one of the top priorities in the food system. NPHarvests technology has what it takes to combine these aspects in a very interesting business model," says Mika Kukkurainen, Partner at Nordic Foodtech VC. NPHarvest has two patents pending and is gearing up towards building its first products, ready to be installed at wastewater management facilities. Their main customers are wastewater management plants, biogas plants, and livestock farms that are trying to cut their costs, reduce their carbon footprint, or earn extra income from recycled fertilizer sales. Antti Myllärinen CEO of Doranova Oy, says: "Nutrient recovery stands as a critical component within the biogas industry, yet frequently encounters bottlenecks during the processin...

Lucas Käldström is a CNCF Ambassador, Kubernetes contributor and expert. Lucas Co-led SIG cluster lifecycle, ported Kubernetes to ARM and shepherded kubeadm from inception to GA. Today Lucas runs three meetup groups in Finland, studies at Aalto University, and, when time allows, contributes to cloud native software as a contractor.   Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod News of the week Weaveworks shutdown their operations Weavwork CEO Alexis Richardson post on Linkedin kubetrain.io Bytedance KubeAdmiral on GitHub Bytedance KubeAdmiral Announcement on InfoQ Strimzi joins the CNCF Incubator Microsoft new Cost Management tools for Azure Links from the interview Lucas Käldström LinkedIn Twitter/X Kubernetes as a dishwasher Understanding Kubernetes Through Real-World Phenomena and Analogies - Lucas Käldström Lucas research thesis Paper - Large-scale cluster management at Google with Borg API Machinery Dr. Stefan Schimanski KCP - Kubernetes-Like Control Plane Kubernetes API Conventions SIG Architecture Ingress2gateway - Ingress to Gateway Migrator Promise Theory: Principles and Applications (Mark Burgess, Jan Bergstra) In Search of Certainty: The Science of Our Information Infrastructure (Mark Burgess) Sweden Finns Links from the post-interview chat Keynote: Reperforming a Nobel Prize Discovery on Kubernetes - Ricardo Rocha & Lukas Heinrich Why Service Is the Worst API in Kubernetes, & What We're Doing About It - Tim Hockin Gateway API TCP Routes Community-Powered Kubernetes LTS: Ensuring Stability and Compatibility While Driving Innovation Jeremy Rickard https://github.com/yannh/kubeconform

Featuring Paul Savage, a Visiting Faculty at UAE University in Al Ain, United Arab Emirates, and a faculty member at Aalto University in Helsinki, Finland.   (Recorded 1/31/24)      

Today, you'll learn about an ancient diagnostic tool getting an AI upgrade, the world's slipperiest surface, and some insight into the minds of everyone who loves this show! Healthy Tongue “Eyes may be the window to your soul, but the tongue mirrors your health.” University of South Australia. 2023. “Ancient tongue diagnosis for the 21st century dental hygienist.” by Kathryn Gilliam. 2023. “Analysis of Tongue Color-Associated Features among Patients with PCR-Confirmed COVID-19 Infection in Ukraine.” by Liudmyla Horzov. 2021. Slippery Surface “Droplet slipperiness despite surface heterogeneity at molecular scale.” by Sakari Lepikko, et al. 2023. “Slippery Science: Crafting the World's Most Water-Repellent Surface.” by Aalto University. 2023. Curious for Answers “Curiosity evolves as information unfolds.” by Abigail Hsiung, et al. 2023. “Unraveling Curiosity: Why We Savor the Suspense and Shun Spoilers.” Neuroscience.com. 2023. Follow Curiosity Daily on your favorite podcast app to get smarter with Calli and Nate — for free! Still curious? Get exclusive science shows, nature documentaries, and more real-life entertainment on discovery+! Go to https://discoveryplus.com/curiosity to start your 7-day free trial. discovery+ is currently only available for US subscribers. Hosted on Acast. See acast.com/privacy for more information.

In the spirit of the season, here's a true gift from Aalto University in Finland in the form of an introduction to a framework called systems intelligence (SI). While the name might feel a even a bit cerebral, this work has deeply changed my personal overlook on life and relationships some ten years ago. It's also the practice to which I root my sisu to raise it from only a quality of surviving hardship to an expression of leadership with a hope of creating something of higher good around us.SI was originally developed by professor Raimo Hämäläinen and professor emeritus Esa Saarinen at Aalto University. They highlight that SI is a key competence we all possess as humans. It begins with "thinking about our thinking," as Saarinen puts it, to understand what actually drives our habits, patterns and actions. SI is about better thinking - not only about thinking or thinking more (that's why it is an update to systems thinking). Thinking about our thinking takes us to 'the source' of our action to illuminate a path toward better actions and when we place this understanding within a system, it becomes a dynamic inquiry towards excellence with regards to everything we connect with - within and outside.Below are four points from Hämäläinen ja Saarinen (2007, p. 59-60) that I mention in the episode (I've added a question to each point to use for self-reflection) & further reading.With this... thank you for your support in 2023 and may we both have a steady, strong year of sisu of the heart and love deep in the bones ahead!***1.     Acknowledging that one's action and behaviour is the result of one's thinking. (“What constitutes my mental models, beliefs, assumptions, and interpretations?”)2.     Acknowledging that one's thinking is likely to be one-sided and a far cry from an accurate grasp of the bigger picture; the holistic system around self is likely to be reflected in one's thinking only partially and possibly in a distorted form. (“How well do I know what I don't know?”)3.     To act more intelligently in systemic environments, one must engage in meta-level thinking regarding their thinking. (“How do I use my thinking?”)4.     One's framing of the environment and its interconnected systems is likely to reflect their subjective assumptions. Reflection on how I frame and look at things is an intelligent path to life in systems. (“How do my beliefs guide my thinking?”)Further material: Systems Intelligence Research Group, Aalto Universityhttp://systemsintelligence.aalto.fi/Systems intelligence: A key competence in human action and organizational life. Hämäläinen, R. P. & Saarinen, E. (2007). https://www.researchgate.net/publication/240789681_Systems_Intelligence_A_Key_Competence_in_Human_Action_and_Organizational_LifePerceived systems intelligence and performance in organizations, J. Törmänen, R.P. Hämäläinen and E. Saarinen (2021), https://www.emerald.com/insight/content/doi/10.1108/TLO-04-2021-0045/full/htmlBeing Better Better - Living with Systems Intelligence (2014) https://sal.aalto.fi/publications/pdf-files/being_better_better_living_with_systems_intelligence.pdfSisu as Guts, Grace, and Gentleness - A Way of Life, Growth, and Being in Times of Adversity (2022). https://aaltodoc.aalto.fi/items/7f407bf0-5a8b-4d38-8ae3-4b70336885e0***Find more about sisu at www.sisulab.com or check my book 'Gentle Power: A Revolution in How We Think, Lead, and Succeed Using the Finnish Art of Sisu' (2023). Sisu is a reserve of inner strength but it is also a way for us to know ourselves and impact the world in a positive way. Cultivating these reserves of inner strength starts with self-care and continues through self-inquiry. its power then extends to the world through our inspired acts of deep courage and compassion.

Jimena Califa (UN Global Pulse), Andrea Botero Cabrera (Aalto University) and Florencia Quesada- Avendaño (Helsinki University) reflect on decolonial practices in design, research and education. The panel took place in Aalto University, in Finland. This panel was an initiative of SUR collective, a group of students and researchers striving for decolonial practices and aiming to respond to the hegemonic narratives of the North. This panel opens a discussion about the issue of decolonizing design education and practices within the Finnish context, with insights from active educators and professionals from the Global South. The central concern revolves around the possibility of integrating decolonial practices into the teaching and designing in Finland. This concern is rooted in the experiences of Latinx students at Aalto University's ARTS school, who have observed a marked absence of Non-Western perspectives, notably in areas such as sustainability. The panel explore the challenges, possibilities, and implications of incorporating decolonial approaches into Finnish university education. This panel is part of the list: Investigación en diseño, Finlandia y diseño, Sin Fronteras and Educación en diseño.

If you dive deep into financial advisor fixed effects, you'll begin to understand that an advisor's own portfolio has a bigger impact on the portfolios of their clients than the characteristics of the clients themselves. To help us make sense of this and to further explain financial values and the cross-section of returns, we are joined by the influential and notorious Professor of Finance, Juhani Linnainmaa. Our conversation begins with a comprehensive analysis of financial values, including a comparison between the trading patterns of advisors and those of their clients, a disquisition of misguided beliefs, an examination of client characteristics, and the ins and outs of portfolio variation and customizations. Canada recently adopted regulations from the Mutual Fund Dealers Association (MFDA), and we discuss how this has affected the use of financial advice in the country before comparing the benefit of increased equity share to the cost of advice, what hiring a new advisor before a financial crisis may mean for clients, and the role of regulation in the industry. We end with the cross-section of returns by examining accounting-based anomalies pre-1963, how profitability and investment relate to data mining, why a financial firm would switch between growth and value, and finally, Professor Juhani Linnainmaa's definition of success.     Key Points From This Episode: (0:00:42) A very warm welcome to the influential Professor of Finance, Juhani Linnainmaa.  (0:03:52) Comparing the trading patterns of advisors to those of their clients.  (0:08:45) How regulators can go about addressing misguided beliefs.  (0:11:08) Client characteristics that advisors base portfolio customizations on.  (0:13:22) Whether the variation in a client's portfolio can be explained by their characteristics.  (0:14:49) Explaining the remaining variation in portfolios.  (0:19:38) Other reasons for the high cost of advising, aside from portfolio customization.  (0:22:03) How the adoption of the MFDA affected the use of financial advice in Canada. (0:26:03)  Comparing the benefit of increased equity share to the cost of advice. (0:31:45) How getting a new advisor before the financial crisis affects ongoing investments. (0:35:46) The role of regulation. (0:37:47) Getting into the cross-section of returns with accounting-based anomalies pre-‘63. (0:40:51) Weather profitability and investment are data-mined factors. (0:44:05) The optimal X-anti mix of factors in a portfolio. (0:46:56) The mechanisms that cause firms to move between growth and value. (0:56:31) Professor Juhani's definition of success.   Links From Today's Episode: Rational Reminder on iTunes — https://itunes.apple.com/ca/podcast/the-rational-reminder-podcast/id1426530582.  Rational Reminder Website — https://rationalreminder.ca/  Rational Reminder on Instagram — https://www.instagram.com/rationalreminder/ Rational Reminder on X — https://twitter.com/RationalRemind Rational Reminder on YouTube — https://www.youtube.com/channel/ Rational Reminder Email — info@rationalreminder.caBenjamin Felix — https://www.pwlcapital.com/author/benjamin-felix/  Benjamin on X — https://twitter.com/benjaminwfelix Benjamin on LinkedIn — https://www.linkedin.com/in/benjaminwfelix/ Cameron Passmore — https://www.pwlcapital.com/profile/cameron-passmore/ Cameron on X — https://twitter.com/CameronPassmore Cameron on LinkedIn — https://www.linkedin.com/in/cameronpassmore/ Juhani Linnainmaa — http://jlinnainmaa.com/  Juhani Linnainmaa on LinkedIn — https://www.linkedin.com/in/juhani-linnainmaa-832134194/  Juhani Linnainmaa on Facebook — https://www.facebook.com/juhani.linnainmaa/  Tuck School of Business — https://www.tuck.dartmouth.edu/   Kepos Capital — https://www.keposcapital.com/  Chicago Booth School of Business — https://www.chicagobooth.edu/  National Bureau of Economic Research — https://www.nber.org/  UCLA Anderson School of Management — https://www.anderson.ucla.edu/  Aalto University — https://www.aalto.fi/en   Mutual Fund Dealers Association — https://mfda.ca/   Michael Roberts on LinkedIn — https://www.linkedin.com/in/prof-michael-r-roberts/ 

I continue my conversation with Jeremy Snyder, the founder and CEO of FireTail.io, an end-to-end API security startup. Towards the end of the first part, I asked Jerermy ‘how a developer should think, when using APIS - with so many moving parts - from security and performance aspects'He answers that and continues to share his story relating to:The extensive experience his co-founder has with API based architectures and implementationsHow APIs can implement business functions or offer specific extracts of data held in applicationsFirst, understanding how APIs could be compromised, to pick the scope for what their company firetail should be addressingHow many breaches are related to authentication and authorizationWhy a zero-trust approach is very critical and the good practice of sharing only minimum data that needs to be sharedThe importance of central loggingHow he manages to get a good night's sleep, while playing a very crucial role in the chain of enterprise security in an API based solutionHis personal practices to handle pressure at work and stay calmThe story behind naming their company firetailHow he developed an interest in learning many languagesJeremy asked me about my linguistic interestsHis career tipsSocial media: https://twitter.com/halffinn , https://www.linkedin.com/company/77663520 , https://www.linkedin.com/in/jeremysnyder/ Jeremy is the founder and CEO of FireTail.io, an end-to-end API security startup. Prior to FireTail, Jeremy worked in M&A at Rapid7, a global cyber leader, where he worked on the acquisitions of 3 companies during the pandemic. Jeremy previously led sales at DivvyCloud, one of the earliest cloud security posture management companies, and also led AWS sales in southeast Asia. Jeremy started his career with 13 years in cyber and IT operations. Jeremy has an MBA from Mason, a BA in computational linguistics from UNC, and has completed additional studies in Finland at Aalto University. Jeremy speaks 5 languages and has lived in 5 countries. Jeremy was once kicked off a train in central Sweden, and another time went several days without seeing another human, but did see lots of reindeer.Link to my podcast: https://podcasts.apple.com/us/podcast/ask-a-ciso/id1596056884

In this conversation, Jeremy Snyder, the founder and CEO of FireTail.io, an end-to-end API security startup, shares his professional journey and perspectives. Specifically, How he got into IT in the late 90s, when technology was coming into businessesEarly experience in Linux, VAX and Unix and implementing solutions for a translation agencyBeing responsible to evaluate, implement and integrate with various systems and thereby increasing the empathy for users and their situationsMoving to work with one of the solution providers and taking up tech support roles and trying his hand at software developmentGetting into and liking the infrastructure related rolesHis experience, as an IT infrastructure professional, of working with software developersThe ‘healthy' struggle between the two roles and how IT teams would specify the environments to develop and deploy intoIT teams wanting to conserve resources and giving very limited capacities for developersDays when 98% availability was taken as acceptable and when crashes occurred, devs and IT teams would work overtime to find fault with the other teamStarting with Amazon AWS in 2010 when cloud computing was just evolvingUnderstanding the power of virtualized environments and why that needs a different way of thinking about data centers, getting away from the server-hugger mentalityThe need for users to develop trust in the cloud model of workingThe experience with gaining customer confidence in the cloud model in terms of stability, security etcThe harder aspect of addressing cultural issues triggered by fear of losing jobs by IT personnelTaking up other roles in smaller companies and understanding the security and vulnerability risks that companies could get exposed toPerimeter controls, endpoint protection, logging and monitoring etcFrom replicating data center structures to auto scaling infrastructure using containers and serverless architecturesThese resulting in more and more API based architecturesSocial media: https://twitter.com/halffinn https://www.linkedin.com/company/77663520 https://www.linkedin.com/in/jeremysnyder/ Jeremy is the founder and CEO of FireTail.io, an end-to-end API security startup. Prior to FireTail, Jeremy worked in M&A at Rapid7, a global cyber leader, where he worked on the acquisitions of 3 companies during the pandemic. Jeremy previously led sales at DivvyCloud, one of the earliest cloud security posture management companies, and also led AWS sales in southeast Asia. Jeremy started his career with 13 years in cyber and IT operations. Jeremy has an MBA from Mason, a BA in computational linguistics from UNC, and has completed additional studies in Finland at Aalto University. Jeremy speaks 5 languages and has lived in 5 countries. Jeremy was once kicked off a train in central Sweden, and another time went several days without seeing another human, but did see lots of reindeer. Link to my podcast: https://podcasts.apple.com/us/podcast/ask-a-ciso/id1596056884

A aplicação das práticas de Lean Construction tem crescido significativamente em diversos ramos da indústria, reduzindo prazos, melhorando a qualidade e prevenindo desperdícios. É por isso que nesse episódio eu trago de volta um grande especialista no assunto: Hylton Olivieri, que já esteve no Capital Projects Podcast, no Episódio #72! Hylton destaca as dores enfrentadas pelas construtoras, os benefícios que podem ser alcançados através do Lean Construction, e como os profissionais podem se preparar melhor para esse desafio! Hylton é graduado em Engenharia Civil, Mestre em habitação pelo IPT, Doutor em construção civil pela Unicamp e Pós-doutorado em planejamento e controle de obras e Lean Construction pela Aalto University, Finlândia. Desde 2022 atua como Diretor de Operações na Scheduler, uma empresa focada no gerenciamento de obras e consultoria no planejamento e controle da produção. É também professor do programa de mestrado profissional do IPT nas disciplinas de planejamento e controle da produção e viabilidade de construções. Ao longo de sua carreira, acompanhou mais de 500 obras de grande porte e visitou diversos países em busca de novas tecnologias de gerenciamento de obras. Atua com Lean Construction desde 2003. Quer se conectar com o Hylton? Acesse o LinkedIn: https://www.linkedin.com/in/hyltonolivieri/ ou então o site da Scheduler: https://www.scheduler.com.br/ Dê um play e vamos juntos! Tem curtido o nosso conteúdo? Que tal tornar-se membro do Capital Projects Podcast, apoiando o canal? Assim, podemos continuar crescendo e ajudando tantos profissionais da Gestão de Projetos! Acesse o link e confira os planos: ⁠⁠https://www.catarse.me/capital_projects_podcast_3c1e?ref=project_link #capitalprojectspodcast #andrechoma #megaprojectmanagement #capitalprojects #megaprojects #megaprojetos #projectmanagement #gestaodeprojetos #sucessoemprojetos #leanconstruction #lean #construcaoenxuta #hyltonolivieri

People often say that they “feel the love” but where exactly do we feel love? Well, researchers from Aalto University in Finland set out to do exactly that. The study at Aalto categorised 27 different types of love from true love to self love and the love for religion. Sean was joined by Pärttyli Rinne, Researcher at Aalto University to discuss...

This month we were delighted to be joined by Niti Bhan, who is a part-time doctoral researcher focusing on trans-disciplinary innovation at Aalto University in the Department of Mechanical Engineering. Niti came to research after almost 30 years of situated practice. Niti specializes in human-centered design/innovation planning. This field asks question like, how can we understand people in their own lives, the way they live and operate as a starting point for design and innovation. In practice this means understanding the lived experience of people in place as a means to create a landscape of the operating environment within a product, service, or business model is introduced. This approach highlights that we cannot make the same kind of assumptions about people in different situated contexts. It is never just a product being introduced, but also how can it be paid for, how it would be distributed in place, and many other things that need to be taken into consideration before even starting to bring something to a particular market. AND this was just the beginning of our wide ranging and mind-expanding conversation! Check out Niti's Aalto Profile here Niti Bhan — Aalto University's research portal If you are interested to learn more about Jan Chipchase's work, check out his Ted Talk https://youtu.be/Qn2NR901NMY?si=E7TlvyvViiFo60gw  --- Send in a voice message: https://podcasters.spotify.com/pod/show/exalt-initiative/message

Heli Rantavuo is an applied cultural studies and social sciences researcher based in Helsinki. For the past 15 years, she has worked in the technology industry in London, Stockholm and Helsinki, contributing and leading research in product and market strategy at Spotify, eBay, Microsoft and Nokia. Before working in the industry, she was a researcher at Aalto University, School of Media and Art where she graduated as Doctor of Arts, and at the Center of Welfare and Health in Finland. Heli is a founding member of the Human Sciences in Strategy association in Finland which brings together applied anthropologists and other human scientists who practise their craft outside academia.We are happy to have Heli with us speaking to her background and her experience and thoughts on isolation. She shares some of the lenses she is considering to use to explore the topic of isolation, such as temporality, embodiment and capitalism. Lastly, she talks about what excites her the most about coming to the conference as well as her advice to those considering to attend. Listen to the episode to hear more about it.

Join Matt for a special episode discussing the new government immigration proposal of 2023 with: Shreyas Ramachandran Srinivasan (originally from India, has both studied and worked in Finland), Nick J. Walters (Founder of Helsinki LEFT that represents immigrants and other minority groups and overcomes knowledge gaps and the language barrier to integrate them into Finnish politics), Sam Spilsbury (Doctoral Researcher at Aalto University), and Elsa Kivinen (Finn who spent most of her life abroad and studied politics, now back in Finland).

With the Transformation Conference in Stockholm just around the corner, we revisit a talk from the Helsinki edition held in May of this year. In this live panel talk, we speak about academia and the EU's role in fashion's imminent need for transformation. Talking points are:How big the new EU legislations actually areWhat organisations and academia can do to help prepare the industry for this upcoming transformationAnd where you will find the best resources for understanding what's happening in the EU right nowSpeakers: Mauro Scalia, Director of Sustainable Businesses at European Apparel and Textile Federation, Marika Ollaranta, head of decarbonizing industries, Business Finland, Kirsi Niinimäki, associate professor of design and fashion research at Aalto University, and Emilia Gädda, chief advisor, sustainability and circular economy, Finnish Textile and Fashion.Don't miss the upcoming Stockholm edition of the Transformation Conference!Date: 31 August 2023Time: 09.00–13.00Location: Snickeriet, Augustendalstorget 6, 131 52 Nacka strandConference entry is free of charge. Limited seats.Register here. Hosted on Acast. See acast.com/privacy for more information.

Yannis Paniaras is an accomplished Principal Level Director and Designer with extensive experience in leading multidisciplinary product development and design management teams across the United States, Europe, and China. Currently, Yannis is a founding member of Microsoft Digital's AI Center of Excellence, where he spearheads AI investments and experiences for various employee experiences within Microsoft. He has also transformed the creative direction for Microsoft Employee Experiences (EE) through close collaboration with the UX Strategy team in the Employee Experience Studio, setting a new standard for user-centric design and innovation. Yannis holds a Master of Arts degree from Aalto University in Helsinki, Finland, and has received comprehensive education in Italy, the United States, Finland, Sweden, and China.

Jeremy Snyder, Founder of FireTail, joins Corey on Screaming in the Cloud to discuss his career journey and what led him to start FireTail. Jeremy reveals what's changed in cloud since he was an AE and AWS, and walks through how the need for customization in cloud security has led to a boom in the number of security companies out there. Corey and Jeremy also discuss the costs of cloud security, and Jeremy points out some of his observations in the world of cloud security pricing and packaging. About JeremyJeremy is the founder and CEO of FireTail.io, an end-to-end API security startup. Prior to FireTail, Jeremy worked in M&A at Rapid7, a global cyber leader, where he worked on the acquisitions of 3 companies during the pandemic. Jeremy previously led sales at DivvyCloud, one of the earliest cloud security posture management companies, and also led AWS sales in southeast Asia. Jeremy started his career with 13 years in cyber and IT operations. Jeremy has an MBA from Mason, a BA in computational linguistics from UNC, and has completed additional studies in Finland at Aalto University. Jeremy speaks 5 languages and has lived in 5 countries. Once, Jeremy went 5 days without seeing another human, but saw plenty of reindeer.Links Referenced: Firetail: https://firetail.io Email: jeremy@firetail.io TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. My guest today is Jeremy Snyder, who's the founder at Firetail. Jeremy, thank you for joining me today. I appreciate you taking the time from your day to suffer my slings and arrows.Jeremy: My pleasure, Corey. I'm really happy to be here.Corey: So, we'll get to a point where we talk about what you're up to these days, but first, I want to dive into the jobs of yesteryear because over a decade ago, you did a stint at AWS doing sales. And not to besmirch your hard work, but it feels like at the time, that must have been a very easy job. Because back then it really felt across the board like the sales motion was basically responding to, “Well, why should we do business with you?” And the response is, “Oh, you misunderstand. You have 87 different accounts scattered throughout your organization. I'm just here to give you visibility, governance, and possibly some discounting over that.” It feels like times have changed in a lot of ways since then. Is that accurate?Jeremy: Well, yeah, but I will correct a couple of things in there. In my days—Corey: Oh, please.Jeremy: —almost nobody had more than one account. I was in the one account, no VPCs, you know, you only separate your workloads by tagging days of AWS. So, our job was a lot, actually, harder at the time because people couldn't wrap their heads around the lack of subnetting, the lack of workload segregation. All of that was really, like, brand new to people, and so you were trying to tell them like, “Hey, you're going to be launching something on an EC2 instance that's in the same subnet as everybody else's EC2 instance.” And people were really worried about lateral traffic and sniffing and what could their neighbors or other customers on AWS see. And by the way, I mean, this was the customers who even believed it was real. You know, a lot of the conversations we went into with people was, “Oh, so Amazon bought too many servers and you're trying to sell us excess capacity.”Corey: That legend refuses to die.Jeremy: And, you know, it is a legend. That is not at all the genesis of AWS. And you know, the genesis is pretty well publicized at this point; you can go just google, “how did AWS started?” You can find accurate stuff around that.Corey: I did it a few years ago with multiple Amazon execs and published it, and they said definitively that that story was not true. And you can say a lot about AWS folks, and I assure you, I do, but I also do not catch them lying to my face, ever. And as soon as that changes, well, now we're going to have a different series of [laugh] conversations that are a lot more pointed. But they've earned some trust there.Jeremy: Yeah, I would agree. And I mean, look, I saw it internally, the way that Amazon built stuff was at such a breakneck pace, that challenge that they had that was, you know, the published version of events for why AWS got created, developers needed a place to test code. And that was something that they could not get until they got EC2, or could not get in a reasonably enough timeframe for it to be, you know, real-time valid or relevant for what was going on with the company. So, you know, that really is the genesis of things, and you know, the early services, SQS, S3, EC2, they all really came out of that journey. But yeah, in our days at AWS, there was a lot of ease, in the sense that lots of customers had pent-up frustrations with their data center providers or their colo providers and lots of customers would experience bursts and they would have capacity constraints and they would need a lot of the features that AWS offered, but we had to overcome a lot of technical misunderstandings and trust issues and, you know, oh, hey, Amazon just wants to sniff our data and they want to see what we're up to, and explain to them how encryption works and why they have their own keys and all these things. You know, we had to go through a lot of that. So, it wasn't super easy, but there was some element of it where, you know, just demand actually did make some aspects easy.Corey: What have you seen change since, well I guess ten years ago and change now? And let's be clear, you don't work in AWS sales, but you also are not oblivious to what the market is doing.Jeremy: For sure. For sure. I left AWS in 2011 and I've stayed in the cloud ecosystem pretty much ever since. I did spend some time working for a system integrator where all we did was migrate customers to AWS. And then I spent about five, six years working on cloud security primarily focused on AWS, a lot of GCP, a little bit of Azure.So yeah, I mean, I certainly stay up to date with what's going on in the state of cloud. I mean, look, Cloud has evolved from this kind of, you know, developer-centric, very easy-to-launch type of platform into a fully-fledged enterprise IT platform and all of the management structures and all of the kind of bells and whistles that you would want that you probably wanted from your old VMware networks but never really got, they're all there now. It is a very different ballgame in terms of what the platform actually enables you to do, but fundamentally, a lot of the core building block constructs and the primitives are still kind of driving the heart of it. It's just a lot of nicer packaging.What I think is really interesting is actually how customers' usage of cloud platforms has changed over time. And I always think of it and kind of like the, going back to my days, what did I see from my customers? And it was kind of like the month zero, “I just don't believe you.” Like, “This thing can't be real, I don't trust it, et cetera.” Month one is, I'm going to assign some developer to work on some very low-priority, low-risk workload. In my days, that was SharePoint, by the way. Like, nine times out of ten, the first workload that customers stood up was a SharePoint instance that they had to share across multiple locations.Corey: That thing falls over all the time anyway. May as well put it in the cloud where it can do so without taking too much else down with it. Was that the thinking or?Jeremy: Well, and the other thing about it at the time, Corey, was that, like, so many customers worked in this, like, remote-first world, right? And so, SharePoint was inevitably hosted at somebody's office. And so, the workers at that office were so privileged over the workers everywhere else. The performance gap between consuming SharePoint in one location versus another was like, night and day. So, you know, employees in headquarters were like, “Yeah, SharePoint's great.” Employees in branch offices were like, “This thing is terrible,” you know? “It's so slow. I hate it, I hate it, I hate it.”And so, Cloud actually became, like, this neutral location to move SharePoint to that kind of had an equal performance for every office. And so, that was, I think, one of the reasons and it was also, you know, it had capacity problems, and customers were right at that point, uploading tons of static documents to it, like Word documents, Office attachments, et cetera, and so they were starting to have some of these, like, real disk sprawl problems with SharePoint. So, that was kind of the month one problem. And only after they get through kind of month two, three, and four, and they go through, “I don't understand my bill,” and, “Help me understand security implications,” then they think about, like, “Hey, should we go back and look at how we're running that SharePoint stuff and maybe do it more efficiently and, like, move those static Office documents onto S3?” And so on, and so on.And that's kind of one of the big things that I've changed that I would say is very different from, like, 2011 to now, is there's enough sophistication around understanding that, like, you don't just translate what you're doing in your office or in your data center to what you're doing on cloud. Or if you do, you're not getting the most out of your investment.Corey: I'm curious to get your take on how you have seen cloud adoption patterns differ, specifically tied to geo. I mean, I tend to see it from a world where there's a bifurcation of between born-in-the-cloud SaaS-type companies where one workload is 80% of their bill or whatnot, and of the big enterprises where the largest single component is 3%. So, it's a very different slice there. But I'm curious what you would see from a sales perspective, looking across a lot of different geographic boundaries because we're all, on some level, biased based upon where we tend to spend our time doing business. I'm in San Francisco, which is its very own strange universe that has a certain perspective about itself that is occasionally accurate, but not usually. But it's a big world out there.Jeremy: It is. One thing that I would say it's interesting. I spent my AWS days based in Singapore, living in Singapore at the time, and I was working with customers across Southeast Asia. And to your point, Corey, one of the most interesting things was this little bit of a leapfrog effect. Data centers in Asia-Pac, especially in places like the Philippines, were just terrible.You know, the Philippines had, like, the second highest electricity rates in Asia at the time, only behind Japan, even though the GDP per capita gap between those two countries is really large. And yet you're paying, like, these super-high electricity rates. Secondarily, data centers in the Philippines were prone to flooding. And so, a lot of companies in the Philippines never went the data center route. You know, they just hosted servers in their offices, you know, they had a bunch of desktop machines in a cubicle, that kind of situation because, like, data centers themselves were cost prohibitive.So, you saw this effect a little bit like cell phones in a lot of the developing world. Landline infrastructure was too expensive or never got done for whatever reason, and people went straight to cell phones. So actually, what I saw in a lot of emerging markets in Asia was, screw the data center; we're going to go straight to cloud. So, I saw a lot of Asia-Pac get a little bit ahead of places like Europe where you had, for instance, a lot of long-term data center contracts and you had customers really locked in. And we saw this over the next, let's say between, like, say, 2014 and 2018 when I was working with a systems integrator, and then started working on cloud security.We saw that US customers and Asia-Pac customers didn't have these obligations; European customers, a lot of them were still working off their lease, and still, you know, I'm locked into let's just say Equinix Frankfurt for another five years before I can think about cloud migration. So, that's definitely one aspect that I observed. Second thing I think is, like, the earlier you started, the earlier you reached the point where you realize that actually there is value in a lot of managed services and there actually is value in getting away from the kind of server mindset around EC2.Corey: It feels like there's a lot of, I want to call it legacy thinking, in some ways, except that's unfair because legacy remains a condescending engineering term for something that makes money. The problem that you have is that you get bound by choices you didn't necessarily realize you were making, and then something becomes revenue-bearing. And now there's a different way to do it, or you learn more about the platform, or the platform itself evolves, and, “Oh, I'm going to rewrite everything to take advantage of this,” isn't happening. So, it winds up feeling like, yeah, we're treating the cloud like a data center. And sometimes that's right; sometimes that's a problem, but ultimately, it still becomes a significant challenge. I mean, there's no way around it. And I don't know what the right answer is, I don't know what the fix is going to be, but it always feels like I'm doing something wrong somewhere.Jeremy: I think a lot of customers go through that same set of feelings and they realize that they have the active runway problem, where you know, how do you do maintenance on an active runway? You kind of can't because you've got flights going in and out. And I think you're seeing this in your part of the world at SFO with a lot of the work that got done in, like, 2018, 2019 where they kind of had to close down a runway and had, like, near misses because they consolidated all flights onto the one active runway, right? It is a challenge. And I actually think that some of the evolution that I've seen our customers go through over the last, like, two, three years, is starting to get away from that challenge.So, to your point, when you have revenue-bearing workloads that you can't really modify and things are pretty tightly coupled, it is very hard to make change. But when you start to have it where things are broken down into more microservices, it makes it a lot easier to cycle out Service A for Service B, or let's say more accurately, Service A1 with Service A2 where you can kind of just, like, plug and play different APIs, and maybe, you know, repoint services at the new stuff as they come online. But getting to that point is definitely a painful process. It does require architectural changes and often those architectural changes aren't at the infrastructure level; they're actually inside the application or they're between things like applications and third-party dependencies where the customers may not have full control over the dependencies, and that does become a real challenge for people to break down and start to attack. You've heard of the Strangler Methodology?Corey: Oh, yes. Both in terms of the Boston Strangler, as well—Jeremy: [laugh]. Right.Corey: As the Strangler design pattern.Jeremy: Yeah, yeah. But I think, like, getting to that is challenging until, like, once you understand that you want to do that, it makes a lot of sense. But getting to the starting point for that journey can be really challenging for a lot of customers because it involves stakeholders that are often not involved on infrastructure conversations, and organizational dysfunction can really creep in there, where you have teams that don't necessarily play nice together, not for any particular reason, but just because historically they haven't had to. So, that's something that I've seen and definitely takes a little bit of cultural work to overcome.Corey: When you take a look across the board of cloud adoption, it's interesting to have seen the patterns that wound up unfolding. Your career path, though, seem to have gotten away from the selling cloud and into some strange directions leading up to what you're doing now, where you founded Firetail. What do you folks do?Jeremy: We do API security. And it really is kind of the culmination of, like, the last several years and what we saw. I mean, to your point, we saw customers going through kind of Phase One, Two, Three of cloud adoption. Phase One, the, you know, for lack of a better phrase, lift-and-shift and Phase Two, the kind of first step on the path towards quote-unquote, “Enlightenment,” where they start to see that, like, actually, we can get better operational efficiency if we, you know, move our databases off of EC2 and on to RDS and we move our static content onto S3.And then Phase Three, where they realize actually EC2 kind of sucks, and it's a lot of management overhead, it's a lot of attack surface, I hate having to bake AMIs. What I really want to do is just drop some code on a platform and run my application. And that might be serverless. That might be containerized, et cetera. But one path or the other, where we pretty much always see customers ending up is with an API sitting on a network.And that API is doing two things. It front-ends a data set and at front-ends a set of functionality, and most cases. And so, what that really means is that the thing that sits on the network that does represent the attack surface, both in terms of accessing data or in terms of let's say, like, abusing an application is an API. And that's what led us to where I am today, what led me and my co-founder Riley to, you know, start the company and try to make it easier for customers to build more secure APIs. So yeah, that's kind of the change that I've observed over the last few years that really, as you said, lead to what I'm doing now.Corey: There is a lot of, I guess, challenge in the entire space when we bound that to—even API security, though as soon as you going down the security path it starts seeming like there's a massive problem, just in terms of proliferation of companies that each do different things, that each focus on different parts of the story. It feels like everything winds up spitting out huge amounts of security-focused, or at least security-adjacent telemetry. Everything has findings on top of that, and at least in the AWS universe, “Oh, we have a service that spits out a lot of that stuff. We're going to launch another service on top of it that, of course, cost more money that then winds up organizing it for you. And then another service on top of that that does the same thing yet again.” And it feels like we're building a tower of these things that are just… shouldn't just be a feature in the original underlying thing that turns down the noise? “Well, yes, but then we couldn't sell you three more things around it.”Jeremy: Yeah, I mean—Corey: Agree? Disagree?Jeremy: I don't entirely disagree. I think there is a lot of validity on what you just said there. I mean, if you look at like the proliferation of even the security services, and you see GuardDuty and Config and Security Hub, or things like log analysis with Athena or log analysis with an ELK stack, or OpenSearch, et cetera, I mean, you see all these proliferation of services around that. I do think the thing to bear in mind is that for most customers, like, security is not a one size fits all. Security is fundamentally kind of a risk management exercise, right? If it wasn't a risk management exercise, then all security would really be about is, like, keeping your data off of networks and making sure that, like, none of your data could ever leave.But that's not how companies work. They do interact with the outside world and so then you kind of always have this decision and this trade-off to make about how much data you expose. And so, when you have that decision, then it leads you down a path of determining what data is important to your organization and what would be most critical if it were breached. And so, the point of all of that is honestly that, like, security is not the same for you as it is for me, right? And so, to that end, you might be all about Security Hub, and Config instead of basic checks across all your accounts and all your active regions, and I might be much more about, let's say I'm quote-unquote, “Digital-native, cloud-native,” blah, blah, blah, I really care about detection and response on top of events.And so, I only care about log aggregation and, let's say, GuardDuty or Athena analysis on top of that because I feel like I've got all of my security configurations in Infrastructure as Code. So, there's not a right and wrong answer and I do think that's part of why there are a gazillion security services out there.Corey: On some level, I've been of the opinion for a while now that the cloud providers themselves should not necessarily be selling security services directly because, on some level, that becomes an inherent conflict of interest. Why make the underlying platform more secure or easier to use from a security standpoint when you can now turn that into a revenue source? I used to make comments that Microsoft Defender was a classic example of getting this right because they didn't charge for it and a bunch of antivirus companies screamed and whined about it. And then of course, Microsoft's like, “Oh, Corey saying nice things about us. We can't have that.” And they started charging for it. So okay, that more or less completely subverts my entire point. But it still feels squicky.Jeremy: I mean, I kind of doubt that's why they started charging for it. But—Corey: Oh, I refuse to accept that I'm not that influential. There we are.Jeremy: [laugh]. Fair enough.Corey: Yeah, I just can't get away from the idea that it feels squicky when the company providing the infrastructure now makes doing the secure thing on top of it into an investment decision.Jeremy: Yeah.Corey: “Do you want the crappy, insecure version of what we build or do you want the top-of-the-line secure version?” That shouldn't be a choice people have to make. Because people don't care about security until right after they really should have cared about security.Jeremy: Yeah. Look, and I think the changes to S3 configuration, for instance, kind of bear out your point. Like, it shouldn't be the case that you have to go through a lot of extra steps to not make your S3 data public, it should always be the case that, like, you have to go through a lot of steps if you want to expose your data. And then you have explicitly made a set of choices on your own to make some data public, right? So, I kind of agree with the underlying logic. I think the counterargument, if there is one to be made, is that it's not up to them to define what is and is not right for your organization.Because again, going back to my example, what is secure for you may not be secure for me because we might have very different modes of operation, we might have very different modes of building our infrastructure, deploying our infrastructure, et cetera. And I think every cloud provider would tell you, “Hey, we're just here to enable customers.” Now, do I think that they could be doing more? Do I think that they could have more secure defaults? You know, in general, yes, of course, they could. And really, like, the fundamentals of what I worry about are people building insecure applications, not so much people deploying infrastructure with bad configurations.Corey: It's funny, we talk about this now. Earlier today, I was lamenting some of the detritus from some of my earlier builds, where I've been running some of these things in my old legacy single account for a while now. And the build service is dramatically overscoped, just because trying to get the security permissions right, was an exercise in frustration at the time. It was, “Nope, that's not it. Nope, blocked again.”So, I finally said to hell with it, overscope it massively, and then with a, “Todo: fix this later,” which of course, never happened. And if there's ever a breach on something like that, I know that I'll have AWS wagging its finger at me and talking about the shared responsibility model, but it's really kind of a disaster plan of their own making because there's not a great way to say easily and explicitly—or honestly, by default the way Google Cloud does—of okay, by default, everything in this project can talk to everything in this project, but the outside world can't talk to any of it, which I think is where a lot of people start off. And the security purists love to say, “That's terrible. That won't work at a bank.” You're right, it won't, but a bank has a dedicated security apparatus, internally. They can address those things, whereas your individual student learner does not. And that's how you wind up with open S3 bucket monstrosities left and right.Jeremy: I think a lot of security fundamentalists would say that what you just described about that Google project structure, defeats zero trust, and you know, that on its own is actually a bad thing. I might counterargue and say that, like, hey, you can have a GCP project as a zero trust, like, first principle, you know? That can be the building block of zero trust for your organization and then it's up to you to explicitly create these trust relationships to other projects, and so on. But the thing that I think in what you said that really kind of does resonate with me in particular as an area that AWS—and really this case, just AWS—should have done better or should do better, is IAM permissions. Because every developer in the world that I know has had that exact experience that you described, which is, they get to a point where they're like, “Okay, this thing isn't working. It's probably something with IAM.”And then they try one thing, two things, and usually on the third or fourth try, they end up with a star permission, and maybe a comment in that IAM policy or maybe a Jira ticket that, you know, gets filed into backlog of, “Review those permissions at some point in the future,” which pretty much never happens. So, IAM in particular, I think, is one where, like, Amazon should do better, or should at least make it, like, easy for us to kind of graphically build an IAM policy that is scoped to least permissions required, et cetera. That one, I'll a hundred percent agree with your comments and your statement.Corey: As you take a look across the largest, I guess, environments you see, and as well as some of the folks who are just getting started in this space, it feels like, on some level, it's two different universes. Do you see points of commonality? Do you see that there is an opportunity to get the individual learner who's just starting on their cloud journey to do things that make sense without breaking the bank that they then can basically have instilled in them as they start scaling up as they enter corporate environments where security budgets are different orders of magnitude? Because it seems to me that my options for everything that I've looked at start at tens of thousands of dollars a year, or are a bunch of crappy things I find on GitHub somewhere. And it feels like there should be something between those two.Jeremy: In terms of training, or in terms of, like, tooling to build—Corey: In terms of security software across the board, which I know—Jeremy: Yeah.Corey: —is sort of a vague term. Like, I first discovered this when trying to find something to make sense of CloudTrail logs. It was a bunch of sketchy things off GitHub or a bunch of very expensive products. Same thing with VPC flow logs, same thing with trying to parse other security alerting and aggregate things in a sensible way. Like, very often it's, oh, there's a few very damning log lines surrounded by a million lines of nonsense that no one's going to look through. It's the needle in a haystack problem.Jeremy: Yeah, well, I'm really sorry if you spent much time trying to analyze VPC flow logs because that is just an exercise in futility. First of all, the level of information that's in them is pretty useless, and the SLA on actually, like, log delivery, A, whether it'll actually happen, and B, whether it will happen in a timely fashion is just pretty much non-existent. So—Corey: Oh, from a security perspective I agree wholeheartedly, but remember, I'm coming from a billing perspective, where it's—Jeremy: Ah, fair enough.Corey: —huh, we're taking a petabyte in and moving 300 petabytes between availability zones. It's great. It's a fun game called find whatever is chatty because, on some level, it's like, run two of whatever that is—or three—rather than having it replicate. What is the deal here? And just try to identify, especially in the godforsaken hellscape that is Kubernetes, what is that thing that's talking? And sometimes flow logs are the only real tool you've got, other than oral freaking tradition.Jeremy: But God forbid you forgot to tag your [ENI 00:24:53] so that the flow log can actually be attributed to, you know, what workload is responsible for it behind the scenes. And so yeah, I mean, I think that's a—boy that's a case study and, like, a miserable job that I don't think anybody would really want to have in this day and age.Corey: The timing of this is apt. I sent out my newsletter for the week a couple hours before this recording, and in the bottom section, I asked anyone who's got an interesting solution for solving what's talking to what with VPC flow logs, please let me know because I found this original thing that AWS put up as part of their workshops and a lab to figure this out, but other than that, it's more or less guess-and-check. What is the hotness? It's been a while since I explored the landscape. And now we see if the audience is helpful or disappoints me. It's all on you folks.Jeremy: Isn't the hotness to segregate every microservice into an account and run it through a load balancer so that it's like much more properly tagged and it's also consumable on an account-by-account basis for better attribution?Corey: And then everything you see winds up incurring a direct fee when passing through that load balancer, instead of the same thing within the same subnet being able to talk to one another for free.Jeremy: Yeah, yeah.Corey: So, at scale—so yes, for visibility, you're absolutely right. From a, I would like to spend less money giving it directly to Amazon, not so much.Jeremy: [unintelligible 00:26:08] spend more money for the joy of attribution of workload?Corey: Not to mention as well that coming into an environment that exists and is scaled out—which is sort of a prerequisite for me going in on a consulting project—and saying, “Oh, you should rebuild everything using serverless and microservice principles,” is a great way to get thrown out of the engagement in the first 20 minutes. Because yes, in theory, anyone can design something great, that works, that solves a problem on a whiteboard, but most of us don't get to throw the old thing away and build fresh. And when we do great, I'm greenfielding something; there's always constraints and challenges down the road that you don't see coming. So, you finally wind up building the most extensible thing in the universe that can handle all these things, and your business dies before you get to MVP because that takes time, energy and effort. There are many more companies that have died due to failure to find product-market fit than have died because, “Oh hey, your software architecture was terrible.” If you hit the market correctly, there is budget to fix these things down the road, whereas your code could be pristine and your company's still dead.Jeremy: Yeah. I don't really have a solution for you on that one, Corey [laugh].Corey: [laugh].Jeremy: I will come back to your one question—Corey: I was hoping you did.Jeremy: Yeah, sorry. I will come back to the question about, you know, how should people kind of get started in thinking about assessing security. And you know, to your point, look, I mean, I think Config is a low-ish cost, but should it cost anything? Probably not, at least for, like, basic CIS foundation benchmark checks. I mean, like, if the best practice that Amazon tells everybody is, “Turn on these 40-ish checks at last count,” you know, maybe those 40-ish checks should just be free and included and on in everybody's account for any account that you tag as production, right?Like, I will wholeheartedly agree with that sentiment, and it would be a trivial thing for Amazon to do, with one kind of caveat—and this is something that I think a lot of people don't necessarily understand—collecting all the required data for security is actually really expensive. Security is an extremely data-intensive thing at this day and age. And I have a former coworker who used to hate the expression that security is data science, but there is some truth in it at this point, other than the kind of the magic around it is not actually that big because there's not a lot of, let's say, heuristic analysis or magic that goes into what queries, et cetera. A lot of security is very rule-based. It's a lot of, you know, just binary checks: is this bit set to zero or one?And some of those things are like relatively simple, but what ends up inevitably happening is that customers want more out of it. They don't just want to know, is my security good or bad? They want to know things like is it good or bad now relative to last week? Has it gotten better or worse over time? And so, then you start accumulating lots of data and time series data, and that becomes really expensive.And secondarily, the thing that's really starting to happen more and more in the security world is correlation of multiple layers of data, infrastructure with applications, infrastructure with operating system, infrastructure with OS and app vulnerabilities, infrastructure plus vulnerabilities plus Kubernetes configurations plus API sitting at the edge of that. Because realistically, like, so many organizations that are built out at scale, the truth of the matter is, is just like on their operating system vulnerabilities, they're going to have tens of thousands, if not millions of individual items to deal with and no human can realistically prioritize those without some context around it. And that is where the data, kind of, management becomes really expensive.Corey: I hear you. Particularly the complaints about AWS Config, which many things like Control Tower setup for you. And on some level, it is a tax on using the cloud as the cloud should be used because it charges for evaluation of changes to your environment. So, if you're spinning things up all the time and then turning them down when they're not in use, that incurs a bunch of Config charges, whereas if you've treat it like a big dumb version of your data center where you just spin [unintelligible 00:30:13] things forever, your Config charge is nice and low. When you start seeing it entering the top ten of your spend on services, something is very wrong somewhere.Jeremy: Yeah. I would actually say, like, a good compromise in my mind would be that we should be included with something like business support. If you pay for support with AWS, why not include Config, or some level of Config, for all the accounts that are in scope for your production support? That would seem like a very reasonable compromise.Corey: For a lot of folks that have it enabled but they don't see any direct value from it either, so it's one of those things where not knowing how to turn it off becomes a tax on what you're doing, in some cases. In SCPs, but often with Control Tower don't allow you to do that. So, it's your training people who are learning this in their test environments to avoid it, but you want them to be using it at scale in an enterprise environment. So, I agree with you, there has to be a better way to deliver that value to customers. Because, yeah, this thing is now, you know, 3 or 4% of your cloud bill, it's not adding that much value, folks.Jeremy: Yeah, one thing I will say just on that point, and, like, it's a super small semantic nitpick that I have, I hate when people talk about security as a tax because I think it tends to kind of engender the wrong types of relationships to security. Because if you think about taxes, two things about them, I mean, one is that they're kind of prescribed for you, and so in some sense, this kind of Control Tower implementation is similar because, like you know, it's hard for you to turn off, et cetera, but on the other hand, like, you don't get to choose how that tax money is spent. And really, like, you get to set your security budget as an organization. Maybe this Control Tower Config scenario is a slight outlier on that side, but you know, there are ways to turn it off, et cetera.The other thing, though, is that, like, people tend to relate to tax, like, this thing that they really, really hate. It comes once a year, you should really do everything you can to minimize it and to, like, not spend any time on it or on getting it right. And in fact, like, there's a lot of people who kind of like to cheat on taxes, right? And so, like, you don't really want people to have that kind of mindset of, like, pay as little as possible, spend as little time as possible, and yes, let's cheat on it. Like, that's not how I hope people are addressing security in their cloud environments.Corey: I agree wholeheartedly, but if you have a service like Config, for example—that's what we're talking about—and it isn't adding value to you, and you just you don't know what it does, how it works, than it [unintelligible 00:32:37]—or more or less how to turn it off, then it does effectively become directly in line of a tax, regardless of how people want to view the principle of taxation. It's a—yeah, security should not be a tax. I agree with you wholeheartedly. The problem is, is it is—Jeremy: It should be an enabler.Corey: —unclea—yeah, the relationship between Config and security in many cases is fairly attenuated in a lot of people's minds.Jeremy: Yeah. I mean, I think if you don't have, kind of, ideas in mind for how you want to use it or consume it, or how you want to use it, let's say as an assessment against your own environment, then it's particularly vexing. So, if you don't know, like, “Hey, I'm going to use Config. I'm going to use Config for this set of rules. This is how I'm going to consume that data and how I'm going to then, like, pass the results on to people to make change in the organization,” then it's particularly useless.Corey: Yeah. I really want to thank you for taking the time to speak with me. If people want to learn more, where's the best place for them to find you?Jeremy: Easy, breezy. We are just firetail.io. That's ‘fire' like the, you know, flaming substance, and ‘tail' like the tail of an animal, not like a story. But yeah, just firetail.io.And if you come now, we've actually got, like, a white paper that we just put out around API security and kind of analyzing ten years of API-based data breaches and trying to understand what actually went wrong in most of those cases. And you're more than welcome to grab that off of our website. And if you have any questions, just reach out to me. I'm just jeremy@firetail.io.Corey: And we'll put links to all of that in the [show notes 00:34:03]. Thank you so much for your time. I appreciate it.Jeremy: My pleasure, Corey. Thanks so much for having me.Corey: Jeremy Snyder, founder and CEO at Firetail. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry comment pointing out that listening to my nonsense is a tax on you going about your day.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Neil Koenig, former BBC Series Producer, now ideaXme board advisor and interviewer, in conversation with Dr Jan Goetz, Co-founder IQM at The St Gallen Symposium. Proponents of quantum computing claim that the technology has much to offer, saying that it promises to revolutionise many aspects of our lives such as scientific research, finance, healthcare and much more. So far, the field has been dominated by US-based giants like IBM, but now a new wave of start-ups is emerging in Europe. One of these is IQM Quantum Computers, based in Finland. At the recent Symposium at the University of St Gallen in Switzerland, I caught up with IQM's CEO, Dr. Jan Goetz. In this interview with me for ideaXme, Jan Goetz talks how he first became in quantum computing, the incredible benefits he believes that the field can offer, and how best to navigate the risks and challenges that lie ahead.  JAN GOETZ - BIOGRAPHY  Jan Goetz is a quantum physicist and co-founding CEO of IQM Quantum Computers (IQM), building next-generation quantum computers. He is on the Board of the European Innovation Council (EIC), the European Quantum Industry Consortium QuIC, a member of the German Federal Economic Senate (Bundeswirtschaftssenat), and a Digital Leader and Global Innovator at the WEF. In 2020, Capital magazine selected him as one of 40 under 40 in Germany, and he received the prestigious entrepreneurship award from the KAUTE Foundation. Mr. Goetz holds a PhD from TU Munich, where he did his doctorate on superconducting quantum circuits, and worked as a Marie-Curie Fellow in Helsinki at Aalto University, where he holds the title of docent. IMAGE CREDITS: Portrait of Jan Goetz: courtesy of IQM Quantum Computers. Jan Goetz: https://fi.linkedin.com/in/jan-goetz/en https://twitter.com/jangoetz6?lang=en https://twitter.com/meetIQM?ref_src=t... www.meetiqm.com Interview credits, Neil Koenig:  https://www.linkedin.com/in/neilkoenig/ https://twitter.com/neilkoenig?lang=en ideaXme links: ideaXme https://radioideaxme.com ideaXme founder: Andrea Macdonald https://uk.linkedin.com/in/andrea-mac... ideaXme is a global network - podcast on 12 platforms, 40 countries, mentor programme and creator series. Mission: To share knowledge of the future. Our passion: Rich Connectedness™!

On this episode of the Scouting For Growth podcast, Sabine VdL talks to Stephen Lathrope, a seasoned executive and proven business leader who has worked as a partner, CEO, and executive director, of private equity-backed financial services and technology businesses. Stephen has also lead large teams within a very well known consulting firm. Today Stephen leads the insurance practice at ICEYE, a geospatial data provider to the insurance and government sector. According to a report produced by MarketsandMarkets, the global geospatial analytics market is estimated to grow at a CAGR of 12.2% from $68 billion dollars in 2022 to $120 billion dollars by 2027. One of the main drivers is the increasing demand for location-based services across various industries, including transportation, construction, and agriculture but also for urban planning and management, disaster response, and environmental monitoring. Over the course of the podcast, they explore what is geospatial data used for? How does geospatial inform the future underwriting and claims? Deep dive into examples as to where geospatial data is best used, and Stephen to give us some advice for insurance companies looking to incorporate geospatial data into their underwriting and claims processes. KEY TAKEAWAYS          ICEYE has been around since 2014 as an organisation that is one of the growth ion new space technologies. The founders miniaturised synthetic aperture radar technology and were able to put them onto miniaturised satellites. The first use case for that for monitoring ice flows in the northern seas for freight planning, hence the ‘ICE' part of ICEYE. What it does today is build and operate its own constellation of radar-enabled satellites, and for insurance we use those to observe hazard and damage related to natural catastrophe and we can also monitor assets on the ground. We can measure very small movements in vehicles, buildings, the surface of the Earth. The opportunities around catastrophe events like that for insurers are really significant. What we can do with new technology is provide a much more rapid insight into where the water is and where the high-water mark has been very quickly within an event. We can provide our customers with an initial view of where the water is within a few hours, we provide a very detailed reports of flood depth and the depth of water with a very useful degree of accuracy. Our customers associate that with the perimeter of individual buildings and that enables them to very quickly identify which of their customers need assistance most urgently, how much water is likely to be around a property causing how much damage and where to allocate resources on the ground. The kind of data we provide is used to size the overall cost of an event and the individual potential damage cost associated with individual buildings. One of the very common challenges that we have to work through with our customers is to ask “do you really know where the properties that you're insuring are?” It's a factor just how often we can say the water is at 1 metre depth at a particular latitude and longitude and the insurer is trying to work out where that is relative to the properties that they know they have that are affected by the event.   BEST MOMENTS ‘ICEYE is bringing wholly new technology to bear in an industry that has got loads of opportunity to do things differently and better for customers and stakeholders using the insights that we can provide from space and with data and analytics.'‘The majority of what we're doing in insurance, and with government, is around natural catastrophe: response, and near-term preparation for events that look like they're about to happen.'‘There's only going to be more frequent, more severe flooding. As we speak there's a fairly major even happening in Mississippi which we're capturing images of from our satellites and reporting upon right now.'‘We've just launched our beta for insurance and wildfire that's similar. Again, the ability of the radar to see through smoke, cloud, day or night and report while the fire's still burning means insurers can have data that's really detailed, really rapidly.' ABOUT THE GUEST Stephen Lathrope is a proven technology / financial services business leader with 10 years' experience in CEO and executive director roles on boards of Private Equity backed, international financial services / technology businesses, and 20 years' experience in business and technology consulting. Sales / growth specialist, with track record of delivering sales-driven growth in software / services across UK and international markets. Linkedin: https://www.linkedin.com/in/stephen-lathrope-8128046/ About ICEYE ICEYE is a Finnish microsatellite manufacturer. ICEYE was founded in 2014 as a spin-off of Aalto University's University Radio Technology Department, and is based in Espoo. Website: https://www.iceye.com/ ABOUT THE HOST Sabine is a corporate strategist turned entrepreneur. She is the CEO and Managing Partner of Alchemy Crew, a venture lab that accelerates the curation, validation, and commercialization of new tech business models. Sabine is renowned within the insurance sector for building some of the most renowned tech startup accelerators around the world working with over 30 corporate insurers and accelerating over 100 startup ventures. Sabine is the co-editor of the bestseller The INSURTECH Book, a top 50 Women in Tech, a FinTech and InsurTech Influencer, an investor & multi-award winner.  Twitter: SabineVdL LinkedIn: Sabine VanderLinden Instagram: sabinevdLofficial Facebook: SabineVdLOfficial TikTok: sabinevdlofficial Email: podcast@sabinevdl.com Website: www.sabinevdl.com  This show was brought to you by Progressive Media

This week on Making Data Simple, we have Dima Syrotkin, founder of Pandatron.  Dima Syrotkin is the CEO of Pandatron and a PhD researcher at Aalto University in Helsinki. With clients like SAP, Universal Pictures & Skanska, Pandatron is a startup that supports change management. They do it by scaling AI-driven coaching 1-on-1s to every manager, which also allows them to measure change.Show Notes1:49 – Dima's history5:35 – Where does the coaching come in?16:39 – Have you ever had a case where there is no model or exercise?19:28 – Is there any follow up?20:58 – What's your most profound use case?25:49 – Empathy 33:35 – What models are used?36:25 – How does bias work?37:29 – How do you measure progress?39:07 – Describe your business modelPandatronDima on MediumConnect with the TeamProducer Kate Brown - LinkedIn.Host Al Martin - LinkedIn and Twitter. 

Join us for an enlightening episode of The Legal Creatives Podcast as we delve into the world of contract design and simplification with industry experts Stefania Passera and Paula Doyle. In this episode, we explore the challenges of traditional contracts and how simplification can create agreements that foster strong business relationships and outcomes. We delve into the benefits, processes, and future prospects of contract simplification, while sharing insights on best practices for creating legally sound and business-friendly agreements and the role of technology Here's what you will learn:

Ville Pulkki's fame reached the techno avant garde with the adoption of his ingenious VBAP (vector-base amplitude panning) a tool for creating spatial sound. When I met him in Helsinki, I was delighted to discover that behind the techie who developed VBAP, a charming jokester. Since then, I've enjoyed his warmth and his efficient organizing of the Acoustics Department at Aalto University, including the 2023 convention of the Audio Engineering Society of Europe. Maija-Leena Remes and I interviewed Ville in his lab where he was studying the acoustic layers of the Earth's atmosphere. He also talked about his learning to dance at the age of 40 and performing on television for commercials and musical events, where the delight of performance must compete with his delight of invention.   Ville Pulkki is a professor in the Department of Information and Communications Engineering  at Aalto University, Helsinki, Finland who has worked in the field of spatial audio for over 25 years. He developed VBAP for his PhD. in 2001 and later, directional audio coding with his research group. He has also made contributions to the perception of spatial sound, laser-based measurement of room responses, and binaural auditory models. He received the Samuel L. Warner Memorial Medal Award from the Society of Motion Picture and Television Engineers and the AES Silver Medal Award. He enjoys being with his family, building his summer house, playing various musical instruments, and acting, dancing and singing in musical ensembles. Playlist of samples: Score The World contest STW2618 • Ville Pulkki Songs of Flowers and Stones • Charlie Morrow Chorale bounce 1 • Charlie Morrow Soundflake orchestral version • Ville Pulkki Musical fractal Kuusi Soundflake instrumental • Ville Pulkki Tous les Matins du Monde (Marin Marais) • Jordi Savall Ella (1960) • Charlie Morrow Ultrasonic spatial superhearing • Ville Pulkki A Future Harvest • Charlie Morrow ScruTiny in the Great Round • Charlie Morrow Daydream musical composition • Ville Pulkki Binary sequences Six variations for orchestra • Ville Pulkki Wave Music III - 60 Clarinets and a Boat • Charlie Morrow  Sun Chant (1975) • Charlie Morrow Bat Sounds Themes discussed: VBAP, perception of spatial sound, early immersive experiences in Finland, experiencing silence, bat sounds, ultrasonic super hearing, physics vs music, esoteric inventions, ambisonics, performing music live. 

This month on the podcast we are really excited to try something new…by revisiting something old! Christopher and I open the podcast with a short chat and some life updates. Then we turn our attention to one of the first EXALT podcasts, “Exploring the Pluriverse” featuring Maria Ehrnstrom-Fuentes, an associate professor at Hanken School of Business. In this amazing conversation she explores themes of decoloniality, degrowth, and reflections on what researchers do and raises questions about how we should do it! Hope you all enjoy revisiting this conversation as much as we did! If you want to find out more about about Maria and her work here is a link to her researcher profile and publication list. Sophia is now working as the coordinator for Sustainability Science Days, which is co-organized by University of Helsinki and Aalto University. This exciting conference will be taking place on May 23-26, 2023. It will be in-person in Helsinki and there is a limited hybrid programme available on Zoom. There is no charge for joining us online, however registration is required. For more information about the programme, or to register, please visit www.sustainabilitysciencedays.fi --- Send in a voice message: https://podcasters.spotify.com/pod/show/exalt-initiative/message

This episode’s guest is David Derichs, who is a senior lecturer in the Accounting dept. at Aalto University. In this interview, David discusses the importance of enterprise performance management in bridging strategy & execution, key financial & non-financial measures, as well as lagging & leading indicators. Accessibility transcripts for podcast episodes can be found from … Continue reading "Episode 15: Bridging Strategy & Execution with Enterprise Performance Management"

In episode 59 of The Gradient Podcast, Daniel Bashir speaks to Professor Kyunghyun Cho.Professor Cho is an associate professor of computer science and data science at New York University and CIFAR Fellow of Learning in Machines & Brains. He is also a senior director of frontier research at the Prescient Design team within Genentech Research & Early Development. He was a research scientist at Facebook AI Research from 2017-2020 and a postdoctoral fellow at University of Montreal under the supervision of Prof. Yoshua Bengio after receiving his MSc and PhD degrees from Aalto University. He received the Samsung Ho-Am Prize in Engineering in 2021.Have suggestions for future podcast guests (or other feedback)? Let us know here!Subscribe to The Gradient Podcast:  Apple Podcasts  | Spotify | Pocket Casts | RSSFollow The Gradient on TwitterOutline:* (00:00) Intro* (02:15) How Professor Cho got into AI, going to Finland for a PhD* (06:30) Accidental and non-accidental parts of Prof Cho's journey, the role of timing in career trajectories* (09:30) Prof Cho's M.Sc. thesis on Restricted Boltzmann Machines* (17:00) The state of autodiff at the time* (20:00) Finding non-mainstream problems and examining limitations of mainstream approaches, anti-dogmatism, Yoshua Bengio appreciation* (24:30) Detaching identity from work, scientific training* (26:30) The rest of Prof Cho's PhD, the first ICLR conference, working in Yoshua Bengio's lab* (34:00) Prof Cho's isolation during his PhD and its impact on his work—transcending insecurity and working on unsexy problems* (41:30) The importance of identifying important problems and developing an independent research program, ceiling on the number of important research problems* (46:00) Working on Neural Machine Translation, Jointly Learning to Align and Translate* (1:01:45) What RNNs and earlier NN architectures can still teach us, why transformers were successful* (1:08:00) Science progresses gradually* (1:09:00) Learning distributed representations of sentences, extending the distributional hypothesis* (1:21:00) Difficulty and limitations in evaluation—directions of dynamic benchmarks, trainable evaluation metrics* (1:29:30) Mixout and AdapterFusion: fine-tuning and intervening on pre-trained models, pre-training as initialization, destructive interference* (1:39:00) Analyzing neural networks as reading tea leaves* (1:44:45) Importance of healthy skepticism for scientists* (1:45:30) Language-guided policies and grounding, vision-language navigation* (1:55:30) Prof Cho's reflections on 2022* (2:00:00) Obligatory ChatGPT content* (2:04:50) Finding balance* (2:07:15) OutroLinks:* Professor Cho's homepage and Twitter* Papers* M.Sc. thesis and PhD thesis* NMT and attention* Properties of NMT, * Learning Phrase Representations* Neural machine translation by jointly learning to align and translate * More recent work* Learning Distributed Representations of Sentences from Unlabelled Data* Mixout: Effective Regularization to Finetune Large-scale Pretrained Language Models* Generative Language-Grounded Policy in Vision-and-Language Navigation with Bayes' Rule* AdapterFusion: Non-Destructive Task Composition for Transfer Learning Get full access to The Gradient at thegradientpub.substack.com/subscribe

Often times gentleness and power can be seen as opposites, ideas or ways of being that may not go together. Today's guest, Dr. Emilia Elisabet Lahti invites us to rethink this. Sharing a number of insights from her new book Gentle Power: A Revolution in How We Think, Lead and Succeed Using the Finnish Art of Sisu she argues that the intersection of these two qualities can be a catalyst for unlocking some of our greatest potential as people, and as leaders. In this episode:We dive into more of Elisabet's journey including reflections from Sisu Not Silence, a 2400km run across the country of New Zealand which she did to help end the silence around domestic and interpersonal violence. Check out part one with Dr. Lahti (episode 69) for more much more of the backstory on this.She will share key discoveries she gained during the run as well as her martial arts training over the years, and how these insights and revelations were a key part of her research on Gentle Power as an elevated expression of SISU. We will also take a deep dive into gentleness (what it is, what it's not, and why it matters)Being nice vs. being kind and why being kind is a training ground for gentle powerHow gentleness can transform into strength when it meets difficultyElisabet's in the moment practices for cultivating gentle power in difficult conversationsQuestions to help cultivate self-awareness that may be the first step toward unlocking true powerThe importance of humility and how it relates to true powerAnd more!Pick up your copy of Gentle Power now and learn more about Dr. Lahti at sisulab.comAbout Dr. Emilia Elisabet Lahti:Emilia Elisabet Lahti, who goes by her second name Elisabet, is an awarded educator, applied psychology researcher, published author, and international presenter on topics of inner strength in times of adversity and transformation through self-leadership. Elisabet studied applied positive psychology at the University of Pennsylvania under the guidance of Dr. Martin Seligman and completed a PhD at Aalto University in Finland in which she pioneered the research on the Finnish construct of sisu (a psychological strength potential referring to extraordinary determination, courage and resoluteness in the face of extreme adversity). She is passionate about the study of human flourishing and cultivation of virtues, and to determine how these can be leveraged on a systemic level to promote worldwide change. Founder of Sisu Lab which builds communities and organizational cultures based on everyday leadership as expression of courage and compassion. Her work has been featured in The New Yorker, Business Insider, BBC, and Forbes. Originally from Finland, she's taught internationally and given talks at Fortune 500 companies. You can find more more information and resources at www.sisulab.com.Enjoying the show? Please rate it on iTunes! For more episodes, podcast updates, and Joshua's event schedule visit: joshuasteinfeldt.comSupport the show

Stephania is the founder at Passera Design and the co-founder of the Legal Design Alliance. She is also the inventor of the Legal Design Jam, a sought-after keynote speaker, trainer, and published author. She holds a doctoral degree from Aalto University, where her empirical dissertation focused on how visualization can improve contract user experience and foster better business relationships. During our time together we discussed how the use of diagrams, images, and visually structured layouts can make contracts more understandable and engaging for their day-to-day users, why following a user-centered approach is so important when it comes to contract design and so much more!

Today we are revisiting a panel talk that we hosted together with Polestar in Helsinki, Finland a few weeks ago. This time we sat down with Tomek Rygalik, founder of Studio Rygalik and Design Nature and professor at Aalto University's architecture department, as well as Petteri Masalin, the Chief Design Officer at Fiskars Group.Together they discuss:The importance of values in design.What responsibilities do they have as designers with regard to sustainability?Their advice to young designers entering the business.This podcast is produced in collaboration with Polestar. Hosted on Acast. See acast.com/privacy for more information.

Cindy Kohtala is a researcher, teacher, and writer in Design-for-Sustainability. Her focus is especially on everyday design, maker culture, and urban activism in sustainability transformation. She is a Professor in Design for Sustainability at Umeå Institute of Design in Sweden. She previously worked at Aalto University, Finland, in the INUSE Users and Innovation Research group and was PI of the postdoctoral research project Making the Next (Sustainable) Industrial Revolution from the Grassroots, funded by the Nessling Foundation. Here, you can read her doctoral dissertation Making Sustainability, awarded with Distinction, from Aalto ARTS books. Her areas of expertise as a Science & Technology Studies scholar include qualitative research (mainly Symbolic Interactionism, the social worlds framework, ethnographic and participant/non-participant in documenting and analyzing technology subculture). As a design researcher and teacher, she has published on and taught sustainable product-service system design, design for social innovation, design for a circular economy, design for distributed economies, values-in-design in the design of products and technologies, and collaborative- and co-design. Mentioned in the interview: o2 global network; Open Source Circular Economy Days; International Fab Lab network; Koppelting; O2 Finland and Pixelache. This interview is part of the lists: Diseño sostenible, Diseño en transición, FABLABS, Diseño y activismo, Canada y diseño, Finlandia y diseño, Suecia y diseño y D&D in English.

Could building more homes and offices out of wood instead of concrete help tackle climate change? We travel to Finland, where growing numbers of homes and offices are being built using wood, and the industry is booming. We'll hear how it can help improve sustainability in cities and take a look at the challenges and benefits of using more wood inside our offices and homes. And we'll also hear concerns about the impact on the country's famous forests. Presenter Maddy Savage speaks to Miimu Airaksinen - vice president of development at Finnish building company SRV, about the construction process and the technology being used. Mai Suominen, a senior forest expert for the World Wildlife fund explains the benefits of using wood to make buildings, because they can store carbon that's already been removed from the atmosphere by trees for decades. Ali Amiri from Aalto University has been exploring the costs and benefits of using wood for building - and the impact of the war in Ukraine which has increased interest in wood as a building material. And Maddy gets a tour from Linda Helen of an eight story wooden office block in Helsinki that's home to one of Finland's biggest gaming companies Supercell. Produced and presented by Maddy Savage. (Image - wooden building in Helskini. Credit: BBC)

As the pandemic recedes, a battle is slowly brewing in American companies: bosses want their employees back in person, and workers are resisting a return to the office. Is that dynamic happening in other countries? Not in Finland, a country that has long fostered a highly flexible work culture. In the second installment of our four-episode bonus series, we speak with Hertta Vuorenmaa, Research Director for the Future of Work program at Aalto University, and Tuomas Syrjanen, co-founder of the Finland-based digital innovation company Futurice, in an effort to discover the connection between Finland's working culture and its status as the happiest nation on earth.

You know when you have friends who wrote a book and pressure you to come on your podcast? That's super annoying, right? Well that's not what happened with https://twitter.com/canyon289 (Ravin Kumar), https://twitter.com/aloctavodia (Osvaldo Martin) and https://twitter.com/junpenglao (Junpeng Lao) — I was the one who suggested doing a special episode about their new book, https://bayesiancomputationbook.com/welcome.html (Bayesian Modeling and Computation in Python). And since they cannot say no to my soothing French accent, well, they didn't say no… All of them were on the podcast already, so I'll refer you to their solo episode for background on their background — aka backgroundception. Junpeng is a Data Scientist at Google, living in Zurich, Switzerland. Previously, he was a post-doc in Psychology and Cognitive Neuroscience. His current obsessions are time series and state space models.  Osvaldo is a Researcher at CONICET in Argentina and the Department of Computer Science from Aalto University in Finland. He is especially motivated by the development and implementation of software tools for Bayesian statistics and probabilistic modeling. Ravin is a data scientist at Google, living in Los Angeles. Previously he worked at Sweetgreen and SpaceX. He became interested in Bayesian statistics when trying to quantify uncertainty in operations. He is especially interested in decision science in business settings. You'll make your own opinion, but I like their book because uses a hands-on approach, focusing on the practice of applied statistics. And you get to see how to use diverse libraries, like PyMC, Tensorflow Probability, ArviZ, Bambi, and so on. You'll see what I'm talking about in this episode. To top it off, the book is fully available online at https://bayesiancomputationbook.com/welcome.html (bayesiancomputationbook.com). If you want a physical copy (because you love those guys and wanna support them), go to CRC website and enter the code FMQ13 at checkout for a 20% discount. Our theme music is « Good Bayesian », by Baba Brinkman (feat MC Lars and Mega Ran). Check out his awesome work at https://bababrinkman.com/ (https://bababrinkman.com/) ! Thank you to my Patrons for making this episode possible! Yusuke Saito, Avi Bryant, Ero Carrera, Brian Huey, Giuliano Cruz, Tim Gasser, James Wade, Tradd Salvo, Adam Bartonicek, William Benton, Alan O'Donnell, Mark Ormsby, James Ahloy, Robin Taylor, Thomas Wiecki, Chad Scherrer, Nathaniel Neitzke, Zwelithini Tunyiswa, Elea McDonnell Feit, Bertrand Wilden, James Thompson, Stephen Oates, Gian Luca Di Tanna, Jack Wells, Matthew Maldonado, Ian Costley, Ally Salim, Larry Gill, Joshua Duncan, Ian Moran, Paul Oreto, Colin Caprani, George Ho, Colin Carroll, Nathaniel Burbank, Michael Osthege, Rémi Louf, Clive Edelsten, Henri Wallen, Hugo Botha, Vinh Nguyen, Raul Maldonado, Marcin Elantkowski, Adam C. Smith, Will Kurt, Andrew Moskowitz, Hector Munoz, Marco Gorelli, Simon Kessell, Bradley Rode, Patrick Kelley, Rick Anderson, Casper de Bruin, Philippe Labonde, Matthew McAnear, Michael Hankin, Cameron Smith, Luis Iberico, Tomáš Frýda, Ryan Wesslen, Andreas Netti, Riley King, Aaron Jones, Yoshiyuki Hamajima, Sven De Maeyer, Michael DeCrescenzo, Fergal M and Mason Yahr. Visit https://www.patreon.com/learnbayesstats (https://www.patreon.com/learnbayesstats) to unlock exclusive Bayesian swag ;) Links from the show: Website of the book: https://bayesiancomputationbook.com/welcome.html (https://bayesiancomputationbook.com/welcome.html) LBS #1 -- Bayes, open-source and bioinformatics, with Osvaldo Martin: https://www.learnbayesstats.com/episode/1-bayes-open-source-and-bioinformatics-with-osvaldo-martin (https://www.learnbayesstats.com/episode/1-bayes-open-source-and-bioinformatics-with-osvaldo-martin) Osvaldo on Twitter: https://twitter.com/aloctavodia (https://twitter.com/aloctavodia) LBS #26 -- What you'll learn & who you'll meet at the PyMC Conference, with Ravin...