<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Applied AI Community - Medium]]></title>
        <description><![CDATA[Applied AI - Medium]]></description>
        <link>https://medium.com/applied-ai-community?source=rss----a95c7d08fb02---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Applied AI Community - Medium</title>
            <link>https://medium.com/applied-ai-community?source=rss----a95c7d08fb02---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:08:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/applied-ai-community" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Im a Nvidia Developer Champion!]]></title>
            <link>https://medium.com/applied-ai-community/im-a-nvidia-developer-champion-3233da4513af?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/3233da4513af</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[nvidia]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:05:27 GMT</pubDate>
            <atom:updated>2026-07-31T18:05:29.002Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ZpFHuzPPIj0EeXgT7tPfVQ.png" /></figure><p>I’m excited to share that I’ve been selected as an NVIDIA Developer Champion.</p><p>Over the past few years, a large part of my work has revolved around developers, AI, cloud infrastructure, and technical communities. From working on Power BI and Microsoft Fabric at Microsoft, to machine learning observability projects, hackathons, developer programs, student communities, and technical speaking, I’ve always been drawn to spaces where people are actively building and sharing ideas.</p><p>The NVIDIA Developer Champion program feels aligned with that.</p><p>What I appreciate about the developer ecosystem around NVIDIA is how practical and builder-focused it is. A lot of the conversations are grounded in real systems, real experimentation, and real technical challenges. Whether people are working on AI infrastructure, robotics, accelerated computing, computer vision, simulation, or open-source tooling, there is a strong culture of people sharing what they are learning as they go.</p><p>My background has crossed several areas of technology. I studied computer science at Western University and have worked across product management, cloud infrastructure, and engineering roles. I previously worked on ML and LLM observability at Datadog, and today I work in Azure Engineering Operations at Microsoft. Alongside work, I’ve also spent a lot of time organizing developer events, mentoring students, speaking at conferences, and helping early-career engineers navigate careers in tech.</p><p>Some of the most meaningful opportunities in my career started through communities like these. A hackathon conversation, a meetup, a technical demo, or someone sharing what they were building often opened doors that formal processes never could.</p><p>That’s one reason why I still care deeply about technical communities, even as the industry changes quickly around AI. We are entering a period where the gap between ideas and execution is shrinking fast. Individual developers can now build systems that previously required much larger teams. Open-source projects move quickly. AI tooling is changing how people prototype, research, write code, and learn new domains. Infrastructure and compute are becoming part of everyday developer conversations in a way that felt much more specialized a few years ago.</p><p>I think communities matter even more in environments like this.</p><p>People learn faster when knowledge is shared openly. Developers improve faster when they can see how others approach problems. Early-career engineers benefit tremendously from spaces where experimentation is encouraged and where technical curiosity is taken seriously.</p><p>As part of the NVIDIA Developer Champion community, I’m looking forward to contributing more through technical writing, developer education, projects, demos, events, and community collaboration. I’m especially interested in areas involving AI infrastructure, developer tooling, reliability engineering, machine learning systems, and practical applications of AI in real workflows.</p><p>I’m also excited to learn from other people in the community. One of the best parts of technology is that there is always another domain, system, or perspective to explore.</p><p>Grateful for the opportunity and excited for what’s ahead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3233da4513af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/im-a-nvidia-developer-champion-3233da4513af">Im a Nvidia Developer Champion!</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m a 2026 Alumni Ventures Fellow]]></title>
            <link>https://medium.com/applied-ai-community/im-a-2026-alumni-ventures-fellow-656c223109f3?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/656c223109f3</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[venture]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[vc]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:05:10 GMT</pubDate>
            <atom:updated>2026-07-31T18:05:11.718Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zoJhkUfj76em4ZVx" /></figure><p>I’m excited to share that I’ve been selected as a 2026 Venture Fellow at <a href="https://www.av.vc/?utm_source=chatgpt.com">Alumni Ventures</a>.</p><p>The Venture Fellow Program is a yearlong venture capital fellowship that brings together professionals from across technology, healthcare, research, startups, product, and operations to learn how venture investing works through real exposure to the industry. This year’s cohort was selected from more than 750 applicants for 30 spots, and includes people from organizations like Microsoft, Google DeepMind, Coinbase, Qualcomm, and DoorDash.</p><p>What stood out to me about the program is that it is designed for people who may not come from traditional venture capital backgrounds.</p><p>Venture has historically been a difficult industry to access. A lot of opportunities happen through existing networks, pattern-matching, and prior exposure to investing circles. For many people working in engineering, product, operations, research, or startups, venture can feel close to the technology world while still being surprisingly hard to enter directly.</p><p>I’ve always been interested in the intersection between builders, technology, and long-term industry shifts.</p><p>My background has been fairly interdisciplinary. I studied computer science at Western University and have worked across product management, developer tooling, cloud infrastructure, and reliability engineering roles. I previously worked on ML and LLM observability at Datadog, worked on Power BI and Fabric at Microsoft, and currently work in Azure Engineering Operations at Microsoft.</p><p>Outside of work, I’ve spent a lot of time in technical communities through hackathons, student organizations, conferences, mentoring, and developer programs. Many of the opportunities that shaped my career came from being around people building ambitious things early.</p><p>That environment overlaps heavily with venture capital.</p><p>Venture is about identifying people with strong conviction, technical insight, and the ability to execute in areas that may still look uncertain to most of the market.</p><p>One thing I find particularly interesting right now is how quickly the barriers to building are changing because of AI. Small teams can move much faster than before. Technical founders have access to tools and infrastructure that previously required much larger organizations. Entire categories around AI infrastructure, developer tooling, robotics, healthcare, and scientific computing are evolving in real time.</p><p>Over the next year, the fellowship includes a 52-week curriculum, hands-on work with investment teams, and direct exposure to founders, operators, and investors. I’m looking forward to learning how investors evaluate markets, assess technical products, think about timing, and develop long-term conviction around emerging technologies.</p><p>I’m also excited to learn from the other Fellows in the program. One of the strongest parts of any technical or investing community is the diversity of perspectives people bring from different industries and operating experiences.</p><p>Grateful for the opportunity and excited for the year ahead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=656c223109f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/im-a-2026-alumni-ventures-fellow-656c223109f3">I’m a 2026 Alumni Ventures Fellow</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenAI GPT 5.5 Event]]></title>
            <link>https://medium.com/applied-ai-community/openai-gpt-5-5-event-1f5121c6b456?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/1f5121c6b456</guid>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[gpt]]></category>
            <category><![CDATA[san-francisco]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:04:52 GMT</pubDate>
            <atom:updated>2026-07-31T18:04:54.286Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Zt0GtgQipsr5PVfY.jpg" /></figure><p>Last week I flew from Seattle to San Francisco for the OpenAI GPT-5.5 Event and had a great experience meeting people working across AI infrastructure, research, developer tooling, and startups.</p><p>One of the best parts of the event was getting the chance to talk directly with Members of Technical Staff and engineers about the technical challenges behind building and deploying large-scale AI systems. A lot of the conversations were very practical. People discussed reliability, inference, agents, developer workflows, evaluation, and what they are seeing from builders using these models in production.</p><p>I also enjoyed meeting developers and founders from the broader AI community. There were a lot of interesting side conversations about projects people are building, where the tooling ecosystem is heading, and how quickly the space is moving right now. It was one of those events where you could walk into almost any conversation and learn something useful.</p><p>As someone working in cloud reliability engineering at Microsoft and interested in AI systems and infrastructure, I appreciated hearing different perspectives from people building at different layers of the stack.</p><p>Thanks to the OpenAI team for organizing the event and bringing together such a strong builder community. I left San Francisco with a lot of new ideas and a better understanding of where the ecosystem is heading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fPx_E3NSOZHa2_m9" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*epfSV2QgGWhHhBNB" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*msfHLAF5QxZ-InCT" /><figcaption>Some pictures from the photobooth at the event. Images generated with 5.5</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f5121c6b456" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/openai-gpt-5-5-event-1f5121c6b456">OpenAI GPT 5.5 Event</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Im attending MLSys ’26!]]></title>
            <link>https://medium.com/applied-ai-community/im-attending-mlsys-26-ccd8e91d6641?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/ccd8e91d6641</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[mlsys]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:04:40 GMT</pubDate>
            <atom:updated>2026-07-31T18:04:41.999Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m planning to attend <a href="https://mlsys.org/?utm_source=chatgpt.com">MLSys 2026</a> this year in Bellevue, Washington.</p><p>MLSys, short for the Conference on Machine Learning and Systems, is one of the main conferences focused on the intersection of machine learning and computer systems. The 2026 conference will be held at the Hyatt Regency Bellevue from May 18 to May 22, 2026, with conference sessions running May 19 to May 21 and Industry Day on May 22.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/0*ROulXAaAyhIOzP4g.jpg" /></figure><p>I’m especially interested in attending because MLSys sits close to the work I care about: building reliable, scalable, and efficient AI systems that can move from research into real production environments. As AI systems become more complex, the hard problems are no longer only about model quality. They are also about training efficiency, inference cost, distributed systems, monitoring, debugging, security, reliability, and how these systems behave under real workloads.</p><p>MLSys focuses on exactly that intersection. The conference covers topics such as efficient model training and serving, LLM training and inference, compound AI systems and agent systems, ML compilers and runtimes, distributed and federated learning, privacy and security, testing and monitoring for ML applications, specialized hardware, hardware-efficient ML methods, and benchmarks and tooling for machine learning systems.</p><p>One thing I appreciate about MLSys is that it brings together both academic and industry perspectives. For people working on cloud infrastructure, reliability, developer tooling, or applied AI, that makes the conference especially relevant.</p><p>This year’s conference also includes a Young Professionals Symposium on May 18, designed for undergraduate students, graduate students, and early-career researchers in industry and academia. The symposium includes keynotes, invited talks, panels, and poster sessions, which makes it a useful entry point for people who are still building their research and technical network in ML systems.</p><p>For me, I’m hoping to use MLSys 2026 to learn more about a few areas:</p><ul><li>How teams are improving LLM training, fine-tuning, and inference efficiency</li><li>What the current research says about agent systems and compound AI systems</li><li>How ML systems are being tested, monitored, and debugged in practice</li><li>Where hardware, compilers, and runtimes are changing the cost and performance of AI workloads</li><li>How industry teams are thinking about production ML systems, reliability, and scaling constraints</li></ul><p>I’m also looking forward to meeting researchers, engineers, builders, and operators working on these problems from different angles. Some of the most useful conference conversations happen outside the talks, especially when people compare what works in papers with what breaks in production.</p><p>MLSys feels especially timely in 2026 because the AI ecosystem is moving quickly from model demos to real systems. The next wave of progress will depend on better infrastructure, better evaluation, better observability, and better ways to make AI systems efficient and reliable. That is why I’m excited to attend and learn from the community.</p><p>If you’re also attending MLSys 2026 in Bellevue, I’d love to connect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oZr25_rwCBi3KzOn.jpg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccd8e91d6641" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/im-attending-mlsys-26-ccd8e91d6641">Im attending MLSys ’26!</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upcoming Nvidia Developer Champions Event: Responsible AI Hackathon]]></title>
            <link>https://medium.com/applied-ai-community/upcoming-nvidia-developer-champions-event-responsible-ai-hackathon-e5e9d7ebff98?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/e5e9d7ebff98</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[nvidia]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:04:28 GMT</pubDate>
            <atom:updated>2026-07-31T18:04:29.778Z</atom:updated>
            <content:encoded><![CDATA[<p>Nvidia Developer Champions will be mentoring and supporting the event! Excited to collaborate with Laurence + team on this event and looking forward to seeing hackathon participants building responsible AI projects.</p><p>RSVP at: <a href="https://t.co/UmOeaKo8Ys">https://luma.com/ab2xlas3</a></p><p><a href="https://x.com/hashtag/Nvidia?src=hashtag_click">#Nvidia</a> <a href="https://x.com/hashtag/ResponsibleAI?src=hashtag_click">#ResponsibleAI</a> <a href="https://x.com/hashtag/AISafety?src=hashtag_click">#AISafety</a> <a href="https://x.com/hashtag/Hackathon?src=hashtag_click">#Hackathon</a> <a href="https://x.com/hashtag/NvidiaAI?src=hashtag_click">#NvidiaAI</a> <a href="https://x.com/hashtag/Developers?src=hashtag_click">#Developers</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/0*lmagRcr2L_vH2lyH" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5e9d7ebff98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/upcoming-nvidia-developer-champions-event-responsible-ai-hackathon-e5e9d7ebff98">Upcoming Nvidia Developer Champions Event: Responsible AI Hackathon</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rethinking Open Source Contribution in the Age of AI Agents, featuring vLLM Core Maintainer Roger…]]></title>
            <link>https://medium.com/applied-ai-community/rethinking-open-source-contribution-in-the-age-of-ai-agents-featuring-vllm-core-maintainer-roger-c098a9a1289d?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/c098a9a1289d</guid>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[vllm]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:03:59 GMT</pubDate>
            <atom:updated>2026-07-31T18:04:00.382Z</atom:updated>
            <content:encoded><![CDATA[<h3>Rethinking Open Source Contribution in the Age of AI Agents, featuring vLLM Core Maintainer Roger Wang at MLSys 2026</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GwWUFB7fqfwEIdC5.png" /></figure><p>At MLSys 2026, I attended Roger Wang’s talk on “Rethinking Open Source Contribution in the Age of AI Agents.”</p><p>Roger is a software engineer focused on machine learning research and systems. He is a core maintainer of vLLM and the lead maintainer of vLLM-Omni, where he works on infrastructure for large multimodal and omni-modality models. He also recently co-founded Inferact, a startup focused on making AI inference cheaper and faster while helping grow vLLM as a major AI inference engine.</p><p>The talk was useful because Roger was speaking from direct experience maintaining open source AI infrastructure at a time when AI coding agents are changing how people contribute.</p><p>One of the clearest points was that the maintainer’s inbox has changed. For vLLM, weekly new pull requests increased a lot from early 2025 to 2026, with visible spikes around major model and coding agent releases. More people can now generate code and open pull requests quickly.</p><p>That creates a real burden for maintainers. The hard part is not only reviewing whether the code works. Maintainers also need to understand whether the contributor understands the system, whether the change solves the right problem, and whether the person will stay involved after the pull request is opened.</p><p>A line from the talk captured this well:</p><blockquote><em>Talk and code is cheap, show me you really care.</em></blockquote><p>That was my main takeaway. In open source, a useful contribution is more than a code diff. It requires reading the codebase, understanding the project direction, explaining the design clearly, and taking responsibility for the change.</p><p>Roger highlighted a few things contributors should focus on:</p><ul><li>Understand the system</li><li>Pick the right problem at the right scale</li><li>Communicate clearly</li><li>Have a sense of ownership and responsibility</li></ul><p>These points sound basic, but they matter more now. If AI agents make it easier to submit code, then contributors need to show stronger signals that they understand what they are changing.</p><p>For maintainers of critical infrastructure, Roger also pointed to a few changes that matter. Standards are higher now. Projects need clearer non-goals, including when “fork it as a plugin” is a valid path. Design decisions should be reviewable, not just the code diff. Reliability matters more, which means projects need to invest more in continuous integration. Reviewer time should also be spent carefully, especially on contributors who are learning the system and likely to keep contributing.</p><p>Another point that stood out was the changing pipeline of open source talent. If the new on-ramp to open source is “prompt an agent,” maintainers may see more contributors who have not deeply read the codebase. That creates risk. It also creates an opportunity to be clearer about what good contribution looks like.</p><p>The bar for human contribution is getting higher and clearer. Writing plausible code is less of a signal than it used to be. The stronger signals are system understanding, good judgment, clear communication, and trust.</p><p>I left the talk thinking that AI agents will change open source contribution, but they will not remove the human part. If anything, the human part becomes more important. The best contributors will be the people who can understand the system, communicate with maintainers, and take responsibility for the work beyond the first pull request.</p><p>For anyone trying to contribute to open source now, especially in AI infrastructure, the practical advice is simple:</p><p>Ask real questions.<br> Meet people outside your usual circle.<br> Support other contributors, especially during poster sessions and discussions.<br> Read the codebase before asking an agent to change it.<br> Show that you care about the project, not just the pull request.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c098a9a1289d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/rethinking-open-source-contribution-in-the-age-of-ai-agents-featuring-vllm-core-maintainer-roger-c098a9a1289d">Rethinking Open Source Contribution in the Age of AI Agents, featuring vLLM Core Maintainer Roger…</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Im a mentor with the Technovation AI Ventures Accelerator!]]></title>
            <link>https://medium.com/applied-ai-community/im-a-mentor-with-the-technovation-ai-ventures-accelerator-921888759be7?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/921888759be7</guid>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[mentor]]></category>
            <category><![CDATA[technovation]]></category>
            <category><![CDATA[women-techmakers]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:03:46 GMT</pubDate>
            <atom:updated>2026-07-31T18:03:48.258Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*PVyuDGJ8XcfjQwgd.png" /></figure><p>Im a mentor with the Technovation AI Ventures Accelerator!<br>The AI Ventures Accelerator is a free accelerator from Technovation and Generation Unlimited that fast-tracks teams of young women from idea to investor-ready AI venture with a chance at $10,000 in equity-free seed funding.</p><h3>Who Can Apply to the Accelerator?</h3><p>The AI Ventures Accelerator exists to jumpstart new tech businesses from young women with exciting ideas and an interest in technology and entrepreneurship.</p><h3>The AI Ventures Accelerator is for you if you…</h3><ul><li>Are a team of young women aged 19–24 (teams of 2–4 preferred, solo founders also welcome)</li><li>Are interested in technology and AI</li><li>Have a problem you want to solve</li><li>Are interested in launching an AI based business</li><li>Can commit 10–15 hours per week for 12 weeks</li><li>Currently reside in a UNICEF Program Country (see list)</li><li>The AI Ventures Accelerator will run March to June 2026. Applications are open until March 4, 2026.</li></ul><p>For this 1st round of the AI Ventures Accelerator, we are only accepting applications from candidates in UNICEF Program Country (see list) and the US.<br>More details: <a href="https://www.technovation.org/ai-ventures-accelerator/">https://www.technovation.org/ai-ventures-accelerator/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=921888759be7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/im-a-mentor-with-the-technovation-ai-ventures-accelerator-921888759be7">Im a mentor with the Technovation AI Ventures Accelerator!</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GT AI & Hiring Study: Call for Participants]]></title>
            <link>https://medium.com/applied-ai-community/gt-ai-hiring-study-call-for-participants-e69a437e00a4?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/e69a437e00a4</guid>
            <category><![CDATA[georgia-tech]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:03:36 GMT</pubDate>
            <atom:updated>2026-07-31T18:03:37.297Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jcHbGyEMgChzbHNmCGv4mQ.png" /></figure><p>Hi everyone! I’m a GT student doing research this summer on AI and hiring. We’re looking for volunteer participants in one of two groups:</p><p>1. Job seekers with:<br>- No bachelor’s degree in your target field<br>- No prior paid work experience in that field<br>- Actively seeking your first job in that area<br>- Workforce training graduates encouraged to apply (Year Up, Per Scholas, bootcamps, and similar programs)</p><p>2. Hiring managers (must review or screen applicants for roles that do not require a bachelor’s degree)</p><p>It’s a 45 to 60-minute interview with a researcher and note taker, and as a thank you, participants can opt into a free resume review session with one of our researchers.</p><p>Sign up here: <a href="http://bit.ly/gt-hiring-study">http://bit.ly/gt-hiring-study</a></p><p>Thanks!</p><p>Grace</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e69a437e00a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/gt-ai-hiring-study-call-for-participants-e69a437e00a4">GT AI &amp; Hiring Study: Call for Participants</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICML 2026 in Seoul: A Practical Guide to the Conference on Machine Learning and Traveling in South…]]></title>
            <link>https://medium.com/applied-ai-community/icml-2026-in-seoul-a-practical-guide-to-the-conference-on-machine-learning-and-traveling-in-south-69fee777c806?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/69fee777c806</guid>
            <category><![CDATA[icml]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:03:23 GMT</pubDate>
            <atom:updated>2026-07-31T18:03:24.587Z</atom:updated>
            <content:encoded><![CDATA[<h3>ICML 2026 in Seoul: A Practical Guide to the Conference on Machine Learning and Traveling in South Korea</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lcF3K0xZJ5tj7Vjt.jpeg" /></figure><p>The Forty-Third International Conference on Machine Learning, better known as ICML 2026, will take place from July 6 to July 11, 2026 in Seoul, South Korea. For researchers, engineers, graduate students, founders, and anyone following the direction of modern AI, ICML is one of the most important machine learning conferences of the year.</p><p>This year’s location makes the event especially exciting. Seoul is one of the most dynamic technology cities in Asia, with a mix of deep research culture, global companies, fast public transportation, late-night food, historic palaces, modern architecture, and a strong cafe culture that makes it surprisingly easy to combine conference work with travel.</p><p>I was in San Francisco last week and had a quick chat with my roommate who was from South Korea, so some tips are inspired from this discussion!</p><p>If you are attending ICML 2026, here is a practical guide to the event, the venue, and what to know before visiting South Korea. As always, this is an unofficial guide and Id recommend doing your research as well.</p><h3>About ICML 2026</h3><p>ICML is one of the major international conferences for machine learning research. It brings together researchers and practitioners working across areas such as deep learning, reinforcement learning, optimization, generative models, probabilistic modeling, ML systems, safety, theory, and applied AI.</p><p>ICML 2026 will be held at COEX Convention &amp; Exhibition Center in Seoul.</p><p>For many attendees, the main conference is where the broad research program happens, while workshops are often where emerging subfields and active research communities form. Tutorials can also be valuable if you want a structured introduction to a topic outside your immediate area.</p><p>If you are a student, early-career researcher, or industry engineer, ICML can feel overwhelming at first because there are so many papers, posters, workshops, and side events happening at the same time. My suggestion is to plan around a few themes instead of trying to see everything. Pick two or three areas you care about most, such as LLM inference, agents, evaluation, AI safety, multimodal learning, optimization, or ML systems, and use those themes to guide which posters, talks, and workshops you prioritize.</p><h3>Why Seoul is a strong host city for ICML</h3><p>Seoul is a great city for a conference like ICML because it combines infrastructure, technology, and culture in a way that is convenient for international attendees. Public transportation is reliable, neighborhoods are well connected, food options are available late, and many major areas are easy to reach by subway or taxi.</p><p>The conference venue, COEX, is in Gangnam, one of Seoul’s major business and commercial districts. This matters because it makes the logistics easier. You can stay near the venue and still have access to restaurants, cafes, shopping, subway lines, and nearby attractions without needing to cross the whole city every day.</p><p>COEX is also connected to a large mall, which is useful during a July conference. Seoul in July can be hot, humid, and rainy, so having indoor food, coffee, convenience stores, and transit access nearby is a real advantage.</p><h3>Getting to COEX</h3><p>Most international attendees will arrive through Incheon International Airport. From the airport, there are a few common ways to reach Seoul:</p><p>The Airport Railroad Express, known as AREX, connects Incheon Airport with Seoul Station. From there, you can transfer to the subway or take a taxi to your hotel. This is a good option if you are comfortable with public transit and do not have too much luggage.</p><p>Airport limousine buses can be convenient if there is a route near your hotel or the COEX area. They are usually easier with luggage, but travel time can depend on traffic.</p><p>Taxis are the simplest option after a long flight, especially if you are arriving late or traveling with bags. They are more expensive than transit, but they can be worth it if you want a low-stress arrival.</p><p>For daily conference commuting, the most relevant subway stations are Samseong Station on Line 2 and Bongeunsa Station on Line 9. If you are booking accommodation, staying near COEX, Samseong, Bongeunsa, Seolleung, Gangnam, or Jamsil can make the week easier.</p><h3>What to expect from South Korea in July</h3><p>July is summer in South Korea, and it is usually hot, humid, and rainy. This does not mean you should avoid going, but it does mean you should pack and plan differently.</p><p>Bring lightweight clothes, comfortable shoes, an umbrella, and a portable charger. If you are attending long conference days, you may also want a light layer for air-conditioned rooms. The weather outside can be humid, while indoor conference spaces, cafes, and subway cars can feel much cooler.</p><p>Because rain can change plans quickly, I would keep outdoor sightseeing flexible. Seoul has plenty of indoor options, including museums, cafes, bookstores, malls, galleries, and restaurants. For outdoor sites like Gyeongbokgung Palace, Bukchon Hanok Village, Namsan, or the Han River, try to go early in the morning or later in the evening when the heat is more manageable.</p><h3>Practical travel tips for Seoul</h3><p>For navigation, download local apps before you arrive. Google Maps is not always the best option in South Korea, so many travelers use Naver Map or KakaoMap for directions. For taxis, Kakao T is commonly used. For translation, Google Translate, or Papago might be helpful, especially for menus and signs.</p><p>A transportation card is also useful. Tmoney cards can be used on subways, buses, and some taxis. You can usually buy and reload them at convenience stores or transit stations.</p><p>Credit cards are widely accepted in Seoul, but it is still useful to carry a small amount of Korean won for markets, transit card reloads, or smaller shops. Convenience stores are everywhere and are very useful for quick meals, drinks, umbrellas, chargers, and snacks.</p><p>For connectivity, consider an eSIM, SIM card, or pocket Wi-Fi. Having reliable data makes it much easier to navigate, translate, and coordinate meetups during a busy conference week.</p><h3>Food and coffee near the conference</h3><p>One of the best parts of visiting Seoul is the food. Around Gangnam and COEX, you can find Korean barbecue, bibimbap, cold noodles, soups, bakeries, cafes, convenience store meals, and international food. If you are attending ICML, you will probably have limited time between sessions, so it is worth saving a few restaurants and cafes near the venue before the trip.</p><p>Seoul is also a great city for cafes. This is helpful during a conference because you may need places to catch up on email, review papers, meet people, or decompress after a long day. Many cafes are designed for lingering, but popular ones can get crowded, especially in the evening.</p><p>For a low-effort plan, use COEX and the surrounding Gangnam area for weekday meals, then explore other neighborhoods when you have more time.</p><h3>What to see if you have extra time</h3><p>If you are staying before or after ICML, Seoul has enough to fill several days. A few classic first-time visitor areas include:</p><p>Gyeongbokgung Palace for history and traditional architecture.</p><p>Bukchon Hanok Village for old Seoul streets and hanok houses.</p><p>Insadong for tea, crafts, galleries, and souvenirs.</p><p>Myeongdong for shopping, skincare, and street food.</p><p>Hongdae for music, cafes, nightlife, and a younger creative scene.</p><p>Seongsu for design shops, cafes, pop-ups, and a more modern creative district.</p><p>Jamsil and Lotte World Tower if you want city views and easy access from the east side of Seoul.</p><p>The Han River for an evening walk, picnic, or relaxed break from conference intensity.</p><p>If you have more time in South Korea, consider a short trip to Busan, Jeju, Gyeongju, or the DMZ. For a first conference trip, though, I would avoid overpacking the schedule. ICML days can be long, and some of the most valuable moments happen through spontaneous conversations, poster sessions, dinners, and meetups.</p><h3>How I would plan the week</h3><p>For ICML, I would treat July 6 as an orientation day. Get familiar with COEX, pick up your badge if available, attend tutorials or expo sessions, and learn the venue layout.</p><p>From July 7 to July 9, I would prioritize the main conference. Each morning, choose the papers, talks, or poster sessions most relevant to your interests. Leave space for unexpected conversations because the best conference moments are often not the ones you planned.</p><p>For July 10 and July 11, I would choose workshops based on specific research communities I want to learn from or contribute to. Workshops are often more focused and easier for meeting people who care about the same problems.</p><p>Outside the conference, I would keep travel plans simple during the week. A good pattern is conference during the day, dinner or a cafe meetup in the evening, and one or two flexible sightseeing blocks if the weather is good.</p><h3>Final thoughts</h3><p>ICML 2026 in Seoul is more than a research conference. It is a chance to learn where machine learning is going, meet people working on the frontier of AI, and experience one of Asia’s most energetic cities.</p><p>For attendees, the biggest advice is to plan enough to reduce stress, but not so much that every hour is booked. Choose your research themes, prepare for humid and rainy July weather, stay somewhere with easy access to COEX, and leave room for the conversations and discoveries that make conferences memorable.</p><p>Seoul is a city that rewards curiosity. ICML is a conference that rewards focus. Together, they make ICML 2026 a trip worth preparing for carefully.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69fee777c806" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/icml-2026-in-seoul-a-practical-guide-to-the-conference-on-machine-learning-and-traveling-in-south-69fee777c806">ICML 2026 in Seoul: A Practical Guide to the Conference on Machine Learning and Traveling in South…</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nvidia Dev Champions & RAI Hackathon: Brev Product Feedback Session]]></title>
            <link>https://medium.com/applied-ai-community/nvidia-dev-champions-rai-hackathon-brev-product-feedback-session-252f54d87e9d?source=rss----a95c7d08fb02---4</link>
            <guid isPermaLink="false">https://medium.com/p/252f54d87e9d</guid>
            <category><![CDATA[nvidia]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[brev]]></category>
            <dc:creator><![CDATA[Grace]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 18:03:11 GMT</pubDate>
            <atom:updated>2026-07-31T18:03:12.449Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ThFr-n_h2JemHaE9P1bDmg.png" /></figure><p>You spent days building with the NVIDIA Dev Champions &amp; Responsible AI Hackathon. You shipped something real. But the deadline passing doesn’t mean the conversation has to stop.</p><p>On <strong>Wednesday, July 1 from 3:30–4:00 PM EDT</strong>, I’m hosting a virtual Product Feedback Session on Brev Dev and I want you there.</p><h3>Why this session exists</h3><p>Hackathons are great at forcing you to build fast. They’re not always great at closing the loop. You ship, you submit, and then you wonder: did anyone actually look at this? Did it matter?</p><p>This session is the loop-closer. As an NVIDIA Dev Champion, I’m bringing together hackathon participants for a focused 30-minute session where you can share your feedback on Brev. Your feedback goes directly to the NVIDIA product team.</p><h3>What responsible AI actually requires</h3><p>Responsible AI is a discipline that demands iteration. The most important thing you can do after building an RAI-focused project is pressure-test it with people who understand the space. What edge cases did you miss? What assumptions baked into your design need revisiting? What did Brev Dev’s infrastructure reveal about your deployment approach?</p><p>These are the conversations that make projects better and that make developers better.</p><h3>What you’ll get</h3><ul><li>Direct feedback on your project from NVIDIA Dev Champions</li><li>Your insights passed straight to the NVIDIA product team, your build influences what gets prioritized next</li></ul><h3>Who should come</h3><p>If you participated in the hackathon and want your work to have impact beyond the submission form, this session is for you. It’s 30 minutes. It’s free. It’s virtual.</p><p><strong>Register here:</strong> <a href="https://luma.com/zz5mxo5x">https://luma.com/zz5mxo5x</a> <strong>Wednesday, July 1 · 3:30–4:00 PM EDT / 12:30–1:00 PM PDT</strong> Hosted on Brev Dev</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=252f54d87e9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/applied-ai-community/nvidia-dev-champions-rai-hackathon-brev-product-feedback-session-252f54d87e9d">Nvidia Dev Champions &amp; RAI Hackathon: Brev Product Feedback Session</a> was originally published in <a href="https://medium.com/applied-ai-community">Applied AI Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>