Complete gig history
All talks by Michelle Michel-Mitchell
5 talks·5 with video·2 years
Loading talks…
For updates and more, join our community 👉 https://www.linkedin.com/company/devoxx-united-kingdom AI governance is no longer just for lawyers and policymakers– it’s now in the hands of developers, designers, and product teams. With the newer laws like the EU’s AI Act, Biden’s AI Executive Order, and emerging state regulations, the rules of the game are changing, and technologists are on the front lines of making them work. But what does “governance” even mean when you’re debugging an algorithm or shipping a new feature? And why should you care? In this talk, we’ll cut through the legal jargon and get real about what these regulations mean for the people actually building AI systems. How do these laws impact your day-to-day work? How can you design systems that align not just with regulatory requirements but also with your organization’s values? And how can you stay creative and innovative while navigating a growing web of rules? We will also zoom out to look at how legislation fits into the bigger picture of AI governance, from frameworks like NIST’s AI Risk Management Framework to corporate guidelines like Microsoft’s Responsible AI Standards. By the end of this session, you’ll have a better understanding of what’s ahead, a set of practical tools for evaluating governance requirements, and strategies to balance innovation with accountability. Whether you’re writing code, managing projects, or making strategic decisions, this session will help you build AI systems that are not just cutting-edge, but also responsible, mindful, and ready for the future.
How do you select features for inclusion in a new programming language? You certantly won't skip something that every other programming language already has. But, how did it work when there weren't so many languages to look at? and how did it work if a language was not designed by a single author or a small team, but by an international committee? If the collective noun for a group of programmers is a "merge conflict", the noun for a group of people with the same goal is "team". "Committee", on the other hand, is a group of people that say to have the same goal, but has a personal idea of what it means. Let's know a little history least we repeat it. I'll give you intrigue, academy vs industry politics, subterfuge, international phonecalls, philosophycal debate and semantic differences: all of that and more in The Amsterdam Plot! 🎤 WHO IS MICHELE MAURO A passionate developer from more years that I'm willing to admit, I've seen computers, software, tools and methods of many different sizes. Some of them I recall fondly, some I try to stay very away from. Since I love to talk and hear others talk about computer science and programming, I've been to many conferences, user groups, university classes and meetups, and spoke in some of them about my experiences and opinions. I usually work in Java and Kotlin, and had the luck of writing some Scala in the past. I am happy the most when my work makes others work less and better. Browncoat, Kitsune, ☂, He/Him. 🦩Info about Voxxed Days Trieste: https://trieste.voxxeddays.com