bowoo.ai

@AiBowoo

온 세상 여자 개발자랑 다 이야기 나눠보고 싶은 사람 #여성개발자_트친소 🌈 5년차/하트카운트💘

Joined December 2020

490 Following

303 Followers

302 Posts

Pinned Tweet

bowoo.ai @AiBowoo

over 1 year ago

그리고 이제 5년차 소프트웨어 엔지니어입니다. ^^

105

AiBowoo retweeted

Soumith Chintala

@soumithchintala

7 months ago

Leaving Meta and PyTorch I'm stepping down from PyTorch and leaving Meta on November 17th. tl;dr: Didn't want to be doing PyTorch forever, seemed like the perfect time to transition right after I got back from a long leave and the project built itself around me. Eleven years at Meta. Nearly all my professional life. Making many friends for life. Almost eight years leading PyTorch, taking it from nothing to 90%+ adoption in AI. Walking away from this was one of the hardest things I've ever done. But I'm leaving with a full heart. PyTorch handles exascale training now. It powers foundation models that are redefining intelligence. It's in production at virtually every major AI company. It's taught in classrooms from MIT to rural India. The tools I dreamed about making accessible? They are. The barrier to entry I wanted to lower? It's almost gone. To be clear, there’s so much more to do. As long as AI evolves at a breakneck pace, PyTorch will continue to play catch up. Obsessing over the yet-to-come sometimes makes us forget how much we’ve already done. To everyone who built this with me—who believed research should be joyful, that tools should be elegant, that open source changes everything—thank you. This wasn't my journey. It was ours. What's next for me? Something small. Something new. Something I don't fully understand yet. Something uncomfortable. I could have moved to something else inside Meta. But I needed to know what's out there. I needed to do something small again. I couldn't live with the counterfactual regret of never trying something outside Meta. It's very hard to leave. I probably have one of the AI industry’s most leveraged seats, I lead the software layer that powers the entire AI industry. Every major AI company and hardware vendor are on a speed dial. This kind of power is really hard to give up. But curiosity ultimately won out in my head. Keep making AI delicious and accessible. I'll be watching. Probably filing issues. Definitely staying involved. Is PyTorch going to be okay? I don't want to be doing PyTorch forever. I don't want to be like Guido or Linus— bound to a single thing for decades. Last November, coinciding with the birth of my daughter, I started planning my exit with Aparna. My goal was to leave PyTorch in a good and stable place. By this August, during the second half of my parental leave, I knew: Edward, Suo, Alban, Greg, John, Joe and Jana were ready. The team faced hard people, product, technical and organizational problems and didn’t feel the need to lean back on me to solve these for them (unlike in the past). The product story they crafted for the PyTorch Conference was coherent—really coherent. The things I'd flagged red were turning healthy. The project didn't need me anymore. Unlike 2020-2022 (when I stepped down to go do robotics and came back when Lin, Dima and Dwarak left), I have strong confidence that this time PyTorch is truly resilient. The most aligned culture carriers of PyTorch – Greg, Alban, Ed, Jason and Joe are at the decision table now, and people with strong value alignment – Suo, John and Jana have joined them at the table. And there’s a long list of equally value-aligned people willing to sit at the table should any of these people leave. There are many little things that make up my confidence on the people – John worked on Julia and open-source for a very long time (in fact we hacked a Torch.jl in 2015), Suo has been the strongest systems builder and strategic partner I’ve had for the past two years, and Jana worked on resilient core systems for a very long time, I’ve had long technical and organizational discussions with her over the past few months that give me confidence. And the product lineup and execution in 2025 should be sufficient evidence for any remaining doubt. I’m confident that this band of PyTorchers are going to do exceptionally well. PyTorch might change in flavor because I no longer impose my own taste from the top, but I’m confident that the values are going to stay intact and the product is going to be awesome. My time at Meta The early years of FAIR were absolutely magical. I was part of a small family of absolutely brilliant people building state-of-the-art AI out in the open. From working on GANs with Emily Denton, Rob Fergus, Leon Bottou, Martin Arjovsky and the (now legendary) Alec Radford to building Starcraft bots with Gabriel Synnaeve, to building the first FAIR Cluster with Howard Mansell, to working on object detection with Adam Lerer and Piotr Dollar, to building PyTorch. It was more fun than I can describe in words. 2015 and 2016 were probably the most productive and professionally enjoyable years of my life. I’ll probably romanticize this period of my life forever. When I joined FAIR, I had massive impostor syndrome, and the first 3 months were very very difficult. I can’t credit Andrew Tulloch enough for being the most thoughtful, kind and welcoming mentor, without whom I wouldn’t have made it. I’m so damn bullish for Meta just from the fact that he’s back. --- My time on PyTorch was special. I loved every part of building it—designing it, managing it, being the PM, TL, comms lead, doc engineer, release engineer, squashing bugs, growth hacking, turning it into a coherent product with hundreds of people, transitioning it to industry stakeholdership – the whole nine yards. To the core PyTorch team at Meta: the engineers, researchers, open-source maintainers, docs writers, CI infrastructure folks, hardware partners, the community builders. To the hundreds more inside and outside Meta—thank you. You turned a library into a movement. There are too many people to credit and thank, but I can't not mention Adam Paszke, Sam Gross, Greg Chanan, Joe Spisak, Alban Desmaison, Edward Yang, Richard Zou, Tongzhou Wang, Francisco Massa, Luca Antiga, Andreas Köpf, Zach DeVito, Zeming Lin, Adam Lerer, Howard Mansell and Natalia Gimelshein. And Schrep. They made the launch happen. And so many more people became centrally important later: Lu Fang, Xiaodong Wang, Junjie Bai, Nikita Shulga, Horace He, Mark Saroufim, Jason Ansel, Dmytro Dzhulgakov, Yangqing Jia, Geeta Chauhan, Will Constable, Briah Hirsh, Jane Xu, Mario Lezcano, Piotr Balecki, Yinghai Lu, Less Wright, Andrew Tulloch, Bruce Lin, Woo Kim, Helen Suk, Chris Gottbrath, Peng Wu, Joe Isaacson, Eli Uriegas, Tristan Rice, Yanan Cao, Elias Ellison, Animesh Jain, Peter Noordhuis, Tianyu Liu, Yifu Wang, Lin Qiao and hundreds more. It’s criminal of me to not take the space to list out everyone else I should be mentioning here. PyTorch is nothing without its people ❤️. The most joyful moments of building PyTorch was meeting users eager to share their happiness, love and feedback. I remember a grad student coming to me at Neurips 2017, in a slurring emotional voice he said he’d been trying to make progress on his research for 3 years but within 3 months of using PyTorch he made so much progress that he was ready to graduate. That moment made it tangible that what we do matters, a lot, to a lot of people, even if you don't constantly hear from them. I do miss the intimacy of the PyTorch community, with a 300 person conference that felt like an extended family gathering, but I feel that’s a small price to pay considering the scale of impact PyTorch is truly having today – yes the Conference is now 3,000 people where market-moving deals get brokered, but it’s helping orders of magnitude more people to do their best AI work. I miss the intimacy, but I'm proud of that growth. --- To Mark Zuckerberg and Mike Schroepfer, who believed that open-sourcing is fundamentally important and is a sound business strategy. This is so hard to understand for most people within the course of business, but we’ve run lock-step on this strategy without ever having to discuss it. Without you two, neither FAIR nor PyTorch would’ve happened. And those mean so much to me. To Yann LeCun and Rob Fergus, for building the magical early FAIR that I so revere. To Aparna Ramani, a leader that I find so rare at Meta in her ability to hold a really high bar for the org, technically brilliant with the span to discuss deep infra systems and industry-strategy within the same conversation and for being an absolute execution-machine! I’ve learned so much from you. To Santosh, Kaushik, Delia, Oldham and Ben for being so welcoming to Infra. For someone coming over from FAIR with a wildly different culture, you all made me feel at home and made me part of the family, and thank you for that. To all my managers who've championed me through the PSC video game – Serkan, Howard, Jerome, Abhijit, Yoram, Joelle, Aparna and Damien – I owe you a lifetime of drinks. --- Signing off for now. —Soumith

soumithchintala's tweet photo. Leaving Meta and PyTorch

I'm stepping down from PyTorch and leaving Meta on November 17th.

tl;dr: Didn't want to be doing PyTorch forever, seemed like the perfect time to transition right after I got back from a long leave and the project built itself around me.

Eleven years at Meta. Nearly all my professional life. Making many friends for life. Almost eight years leading PyTorch, taking it from nothing to 90%+ adoption in AI. Walking away from this was one of the hardest things I've ever done. But I'm leaving with a full heart.

PyTorch handles exascale training now. It powers foundation models that are redefining intelligence. It's in production at virtually every major AI company. It's taught in classrooms from MIT to rural India. The tools I dreamed about making accessible? They are. The barrier to entry I wanted to lower? It's almost gone.

To be clear, there’s so much more to do. As long as AI evolves at a breakneck pace, PyTorch will continue to play catch up. Obsessing over the yet-to-come sometimes makes us forget how much we’ve already done.

To everyone who built this with me—who believed research should be joyful, that tools should be elegant, that open source changes everything—thank you. This wasn't my journey. It was ours.

What's next for me? Something small. Something new. Something I don't fully understand yet. Something uncomfortable. I could have moved to something else inside Meta. But I needed to know what's out there. I needed to do something small again. I couldn't live with the counterfactual regret of never trying something outside Meta.

It's very hard to leave. I probably have one of the AI industry’s most leveraged seats, I lead the software layer that powers the entire AI industry. Every major AI company and hardware vendor are on a speed dial. This kind of power is really hard to give up. But curiosity ultimately won out in my head.

Keep making AI delicious and accessible. I'll be watching. Probably filing issues. Definitely staying involved.

Is PyTorch going to be okay?

I don't want to be doing PyTorch forever. I don't want to be like Guido or Linus— bound to a single thing for decades. Last November, coinciding with the birth of my daughter, I started planning my exit with Aparna. My goal was to leave PyTorch in a good and stable place.

By this August, during the second half of my parental leave, I knew: Edward, Suo, Alban, Greg, John, Joe and Jana were ready. The team faced hard people, product, technical and organizational problems and didn’t feel the need to lean back on me to solve these for them (unlike in the past). The product story they crafted for the PyTorch Conference was coherent—really coherent. The things I'd flagged red were turning healthy. The project didn't need me anymore. Unlike 2020-2022 (when I stepped down to go do robotics and came back when Lin, Dima and Dwarak left), I have strong confidence that this time PyTorch is truly resilient. The most aligned culture carriers of PyTorch – Greg, Alban, Ed, Jason and Joe are at the decision table now, and people with strong value alignment – Suo, John and Jana have joined them at the table. And there’s a long list of equally value-aligned people willing to sit at the table should any of these people leave. There are many little things that make up my confidence on the people – John worked on Julia and open-source for a very long time (in fact we hacked a Torch.jl in 2015), Suo has been the strongest systems builder and strategic partner I’ve had for the past two years, and Jana worked on resilient core systems for a very long time, I’ve had long technical and organizational discussions with her over the past few months that give me confidence. And the product lineup and execution in 2025 should be sufficient evidence for any remaining doubt.

I’m confident that this band of PyTorchers are going to do exceptionally well. PyTorch might change in flavor because I no longer impose my own taste from the top, but I’m confident that the values are going to stay intact and the product is going to be awesome.

My time at Meta

The early years of FAIR were absolutely magical. I was part of a small family of absolutely brilliant people building state-of-the-art AI out in the open. From working on GANs with Emily Denton, Rob Fergus, Leon Bottou, Martin Arjovsky and the (now legendary) Alec Radford to building Starcraft bots with Gabriel Synnaeve, to building the first FAIR Cluster with Howard Mansell, to working on object detection with Adam Lerer and Piotr Dollar, to building PyTorch. It was more fun than I can describe in words. 2015 and 2016 were probably the most productive and professionally enjoyable years of my life. I’ll probably romanticize this period of my life forever.

When I joined FAIR, I had massive impostor syndrome, and the first 3 months were very very difficult. I can’t credit Andrew Tulloch enough for being the most thoughtful, kind and welcoming mentor, without whom I wouldn’t have made it. I’m so damn bullish for Meta just from the fact that he’s back.

---

My time on PyTorch was special.

I loved every part of building it—designing it, managing it, being the PM, TL, comms lead, doc engineer, release engineer, squashing bugs, growth hacking, turning it into a coherent product with hundreds of people, transitioning it to industry stakeholdership – the whole nine yards.

To the core PyTorch team at Meta: the engineers, researchers, open-source maintainers, docs writers, CI infrastructure folks, hardware partners, the community builders. To the hundreds more inside and outside Meta—thank you. You turned a library into a movement.

There are too many people to credit and thank, but I can't not mention Adam Paszke, Sam Gross, Greg Chanan, Joe Spisak, Alban Desmaison, Edward Yang, Richard Zou, Tongzhou Wang, Francisco Massa, Luca Antiga, Andreas Köpf, Zach DeVito, Zeming Lin, Adam Lerer, Howard Mansell and Natalia Gimelshein. And Schrep. They made the launch happen. And so many more people became centrally important later: Lu Fang, Xiaodong Wang, Junjie Bai, Nikita Shulga, Horace He, Mark Saroufim, Jason Ansel, Dmytro Dzhulgakov, Yangqing Jia, Geeta Chauhan, Will Constable, Briah Hirsh, Jane Xu, Mario Lezcano, Piotr Balecki, Yinghai Lu, Less Wright, Andrew Tulloch, Bruce Lin, Woo Kim, Helen Suk, Chris Gottbrath, Peng Wu, Joe Isaacson, Eli Uriegas, Tristan Rice, Yanan Cao, Elias Ellison, Animesh Jain, Peter Noordhuis, Tianyu Liu, Yifu Wang, Lin Qiao and hundreds more. It’s criminal of me to not take the space to list out everyone else I should be mentioning here. PyTorch is nothing without its people ❤️.

The most joyful moments of building PyTorch was meeting users eager to share their happiness, love and feedback. I remember a grad student coming to me at Neurips 2017, in a slurring emotional voice he said he’d been trying to make progress on his research for 3 years but within 3 months of using PyTorch he made so much progress that he was ready to graduate. That moment made it tangible that what we do matters, a lot, to a lot of people, even if you don't constantly hear from them. I do miss the intimacy of the PyTorch community, with a 300 person conference that felt like an extended family gathering, but I feel that’s a small price to pay considering the scale of impact PyTorch is truly having today – yes the Conference is now 3,000 people where market-moving deals get brokered, but it’s helping orders of magnitude more people to do their best AI work. I miss the intimacy, but I'm proud of that growth.

---

To Mark Zuckerberg and Mike Schroepfer, who believed that open-sourcing is fundamentally important and is a sound business strategy. This is so hard to understand for most people within the course of business, but we’ve run lock-step on this strategy without ever having to discuss it. Without you two, neither FAIR nor PyTorch would’ve happened. And those mean so much to me.

To Yann LeCun and Rob Fergus, for building the magical early FAIR that I so revere.

To Aparna Ramani, a leader that I find so rare at Meta in her ability to hold a really high bar for the org, technically brilliant with the span to discuss deep infra systems and industry-strategy within the same conversation and for being an absolute execution-machine! I’ve learned so much from you.

To Santosh, Kaushik, Delia, Oldham and Ben for being so welcoming to Infra. For someone coming over from FAIR with a wildly different culture, you all made me feel at home and made me part of the family, and thank you for that.

To all my managers who've championed me through the PSC video game – Serkan, Howard, Jerome, Abhijit, Yoram, Joelle, Aparna and Damien – I owe you a lifetime of drinks.

---

Signing off for now.

—Soumith

489

11K

566

AiBowoo retweeted

Steren

@steren

8 months ago

I'm excited about @nodejs built-in SQLite support

938

75K

AiBowoo retweeted

PostgreSQL @PostgreSQL

9 months ago

News: PostgreSQL 18 Released! https://t.co/WfucwTo3RZ

396

137

118K

Who to follow

KR_BE

@clockSmurf

webDeveloper/LA Lakers/LA Rams/LG Twins/taeriVely

𝙂𝙡𝙞𝙩𝙘𝙝

@glitchglitchgli

여성개발자가 많은 곳을 찾다가 트위터 가입 | 현재는 유튜버 등 부업 도전 중 | #블루레이디

āpōpō 🕯️

@keia_oli

개발,기획,디자인 다 초보에요🍀☘🍀이름(āpōpō)은 내일이라는 하와이 말. 🌞 프론트엔드 공부중 ⚠ 마음 누르기를 좋아함 @ lildev11111

bowoo.ai @AiBowoo

9 months ago

수전 손택의 ‘나이 듦에 관한 이중 잣대‘ 읽었고 이 글이 1972년도에 쓰였음을 알고 조금 놀랐다. 50년도 더 지난 지금에도 그대로 적용되는 이야기이기에…

AiBowoo retweeted

썩어라 수시생 @susisaeng_suck

10 months ago

susisaeng_suck's tweet photo. https://t.co/A2w4mdJs5V

268

718K

AiBowoo retweeted

MM @mmmmmmmdev

10 months ago

(여성 개발자 전용 스터디 모집) 이 책을 매주 같이 읽고 이야기하실 분들 계실까요? 🤗 개발자의 성장, 일, 회사, 그리고 삶에 대한 고민을 함께 나눠요. 📅 기간: 8월 13일(수) ~ 9월 17일(수), 총 6주간 🕙 시간: 매주 수요일 저녁 🎯 방식: * 매주 정해진 분량을 읽고 옵니다. * 각 장마다 미션이 있어요! 한 주 동안 실천해보고 경험을 나눠요. * 읽으며 생긴 질문이나 각자 회사/개발생활 고민도 같이 나눠요. 💬 이런 분들께 추천해요! * 개발자로서 방향성을 고민하는 분 * 혼자 공부하다 동기 부여가 필요한 분 * 회사/커리어 고민을 누군가와 나누고 싶은 분 * 미션 기반 스터디로 실천하며 배우고 싶은 분 🙋‍♀️ 소규모로 진행하니 관심 있는 분은 얼른 알려주세요! 편하게 오시고, 편하게 이야기 나눠요 🌟 신청: https://t.co/qoritcRxnD

10K

bowoo.ai @AiBowoo

10 months ago

AI 비서 만들기, 나만의 자동화 파이프라인 구축 - AI 엔지니어 김노은님 (8월 12일 화요일) https://t.co/ROYGLNhhs9 여성개발자 강연 소식을 전해요

AiBowoo retweeted

김주희 @NiUnaMenos2019

10 months ago

“ 버닝썬을 변호해도 대통령실 공직기강비서관으로 임명될 수 있더라 ” 대한민국에 이런 메시지를 남길 수는 없다. #버닝썬변호사 #버닝썬가해자변호사해임하라

115

224K

AiBowoo retweeted

ollama

@ollama

10 months ago

Welcome OpenAI's gpt-oss! ollama run gpt-oss:20b ollama run gpt-oss:120b 🧵

104

392

480

244K

bowoo.ai @AiBowoo

over 1 year ago

그리고 이제 5년차 소프트웨어 엔지니어입니다. ^^

105

bowoo.ai @AiBowoo

about 4 years ago

어제부터 아주 꼼짝없이 2년차 소프트웨어 엔지니어가 되었습니다!

bowoo.ai @AiBowoo

about 4 years ago

와악 @preset_data 웨비나에 참여해서 현재 맡은 업무에 필요한 내용을 질문하고 답변도 받았다! 너무 기분 좋고 내일 가서 공유드려야지(이미 아실 수도 있지만^^;) 내 신남을 받아주시는 선배들 계셔서 기뻐❤️‍🔥 이제 코 자자!

bowoo.ai @AiBowoo

over 1 year ago

ghost 좋아

bowoo.ai @AiBowoo

over 1 year ago

I just sponsored cathysarisky. Go sponsor your open source dependencies! https://t.co/7GWBCseJ0Z

AiBowoo retweeted

숑숑✨ @lauvsong__

over 1 year ago

쿼리가 느린데 왜 느린지 모르겠어 !!! 할 때 도움이 되었던 명령어 ‘EXPLAIN ANALYZE’ 해석법을 다뤘습니다. 한국 자료를 찾지 못해서(ㅠ) 직접 써봤습니다. https://t.co/YyA4LQXXg8

190

135

13K

AiBowoo retweeted

여성신문

@wnewskr

over 1 year ago

“지켜주지 못해 미안합니다”… 순천 여고생 살해 현장 추모 물결 이어져 새벽시간 순천서 귀가하다 30대 남성에게 살해된 10대 여성을 애도하는 추모 물결이 이어지고 있다. https://t.co/CmaGjEjxVE

281

310

27K

bowoo.ai @AiBowoo

over 1 year ago

@unniecar 언니차님! 이 트윗는 드라마에서 연출한 다큐의 캡쳐랍니다. 혹시나 하여 실제가 아님을 말씀드려요. 실제로도 차별을 겪으며 자라는 많은 여자아이들이 있었고, 지금도 있겠지요…

bowoo.ai @AiBowoo

over 1 year ago

서비스 중단해

한겨레

@hanitweet

almost 2 years ago

카메라 애플리케이션 ‘소다’(SODA)의 AI 편집 기능이 성적 수치심을 일으키는 사진을 생성한 것에 대해, 네이버의 자회사 스노우가 ‘인공지능 생성물을 100% 통제할 수 없다’는 입��을 내놨습니다. 소다는 1000만회 이상 다운로드된 인기 카메라 앱입니다. https://t.co/R6bRh0MSBY

211

526

258

AiBowoo retweeted

BBC News (World)

@BBCWorld

almost 2 years ago

Inside the deepfake porn crisis engulfing Korean schools https://t.co/UZJnlEjeba

310

317K

AiBowoo retweeted

플랫

@flatflat38

almost 2 years ago

"여성들은 국경을 넘어선 전폭적인 지지를 보내고 있다. 최근 몇 년간 한국의 페미니즘은 중국에 큰 영향력을 끼쳤다. " 중국 여성들은 한국 여성에게 응원과 메시지를 남기는 한편 자국 내 AI를 이용한 성범죄에 대해서도 엄정 대응을 촉구했다.https://t.co/5G15ztFm99

735

946

79K

AiBowoo retweeted