# leaving Published articles for leaving. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Meta Offers Equity Retainers as Engineers Consider Leaving After Layoffs and Reassignments DevFeed: [Meta Offers Equity Retainers as Engineers Consider Leaving After Layoffs and Reassignments]() Original publisher: [Read original article]() Author: Gergely Orosz Published: 2026-08-20T18:08:45Z Content type: opinion Language: en Sources: [The Pragmatic Engineer]() Topics: [Meta](), [Product Management](), [Software]() Tags: [anthropic](), [engineering](), [equity](), [google](), [jobs](), [leaving](), [meta](), [openai](), [product-management]() ### AI overview The article argues that Meta's layoffs and forced reassignments prompted engineers to seek other jobs. It reports that Meta began offering large equity retainers to some departing senior engineers, including those considering moves to Google, Anthropic, and OpenAI. ### Source excerpt In what was predictable: Meta's layoffs and forced reassignments pushed engineers not impacted by either to look for a new job. Meta is now offering large equity retainers, and it doesn't seem working ## Defer in Swift explained with Code Examples DevFeed: [Defer in Swift explained with Code Examples]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-07-06T12:51:59Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [Swift](), [Code](), [async/await](), [Concurrency]() Tags: [code](), [concurrency](), [defer](), [examples](), [leaving](), [scope](), [swift]() ### AI overview This tutorial explains Swift's defer statement, which runs code when control leaves its scope. It covers reverse execution order for multiple defer statements, using defer for resource cleanup, and Swift 6.4 support for awaiting asynchronous cleanup in defer bodies. ### Source excerpt Although the defer keyword was already introduced in Swift 2.0, it's still quite uncommon to use it in projects. Its usage can be hard to understand, but using it can improve your code a lot in some places. The most common use case seen around is opening and closing a context within a scope. Starting ... -> The post Defer in Swift explained with Code Examples appeared first on SwiftLee. ## 365 Days Ago I Left Google: 3 Lessons I've Learned in Self-Employment DevFeed: [365 Days Ago I Left Google: 3 Lessons I've Learned in Self-Employment]() Original publisher: [Read original article]() Author: Kevin Naughton Jr. Published: 2026-05-01T17:02:09Z Content type: opinion Language: en Sources: [The Software Engineer Weekly]() Topics: [Google](), [Software Engineering]() Tags: [employment](), [engineering](), [google](), [leaving](), [risk](), [software-engineering]() ### AI overview A software engineer reflects on leaving Google and spending a year in self-employment, concluding that staying felt riskier than leaving. ### Source excerpt One year ago today, I walked away from my Software Engineering role at Google. At the time, it felt like the riskiest move of my life. Now, looking back from the other side of 365 days of self-employment, I realize the real risk wasn't leaving, ironically, it was staying. ## Leaving Intel DevFeed: [Leaving Intel]() Original publisher: [Read original article]() Published: 2025-12-04T13:00:00Z Content type: opinion Language: en Sources: [Brendan Gregg's Blog]() Topics: [intel](), [Artificial Intelligence](), [GPU](), [eBPF](), [Cloud](), [cloud-computing](), [Linux](), [Open Source](), [Monitoring]() Tags: [ai](), [blog](), [cloud-computing](), [cpu](), [ebpf](), [gpu](), [intel](), [leaving](), [linux](), [monitoring](), [open-source](), [performance]() ### AI overview The author announces his departure from Intel after 3.5 years and reflects on his work there, including open-source AI flame graphs, GPU performance visualization, Linux stack walking, eBPF security monitoring, conference leadership, customer meetings, and a company-wide cloud strategy. ### Source excerpt InnovatiON 2022 AI Flame Graphs GPU Flame Scope Harshad Sane SREcon APAC Cloud strategy Last day I've resigned from Intel and accepted a new opportunity. If you are an Intel employee, you might have seen my fairly long email that summarized what I did in my 3.5 years. Much of this is public: AI flame graphs and released them as open source GPU subsecond-offset heatmap Worked with Linux distros to enable stack walking Was interviewed by the WSJ about eBPF for security monitoring Provided leadership on the eBPF Technical Steering Committee (BSC) Co-chaired USENIX SREcon APAC 2023 Gave 6 conference keynotes It's still early days for AI flame graphs. Right now when I browse CPU performance case studies on the Internet, I'll often see a CPU flame graph as part of the analysis. We're a long way from that kind of adoption for GPUs (and it doesn't help that our open source version is Intel only), but I think as GPU code becomes more complex, with more layers, the need for AI flame graphs will keep increasing. I also supported cloud computing, participating in 110 customer meetings, and created a company-wide strategy to win back the cloud with 33 specific recommendations, in collaboration with others across 6 organizations. It is some of my best work and features a visual map of interactions between all 19 relevant teams, described by Intel long-timers as the first time they have ever seen such a cross-company map. (This strategy, summarized in a slide deck, is internal only.) I always wish I did more, in any job, but I'm glad to have contributed this much especially given the context: I overlapped with Intel's toughest 3 years in history, and I had a hiring freeze for my first 15 months. My fond memories from Intel include meeting Linus at an Intel event who said "everyone is using fleme graphs these days" (Finnish accent), meeting Pat Gelsinger who knew about my work and introduced me to everyone at an exec all hands, surfing lessons at an Intel Australia and HP offsite ( ## Why leaving Facebook/Meta was the best thing we could do for the Trino Community DevFeed: [Why leaving Facebook/Meta was the best thing we could do for the Trino Community]() Original publisher: [Read original article]() Author: Martin Traverso, Dain Sundstrom, and David Phillips Published: 2022-08-02T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [data analytics](), [big-data](), [Open Source](), [SQL](), [Meta]() Tags: [analytics](), [big-data](), [company](), [leaving](), [linkedin](), [meta](), [netflix](), [open-source](), [sql]() ### AI overview The article explains why leaving Facebook/Meta enabled the creators of Presto to build a broader open-source community around a distributed SQL query engine for big data analytics. It describes how Presto grew beyond Facebook, attracted participation from companies including Airbnb, Dropbox, Netflix, and LinkedIn, and served a wide range of analytics needs. ### Source excerpt It might surprise some that our departure from Facebook was one of the simplest decisions we've ever made. Many posts that discuss leaving a FAANG company focus on leaving some grand sum of money or prestige of working at the company. For us, we were leaving the company where we had launched a project that we knew would quickly outgrow the walls of Facebook, and solve a much larger set of problems in the analytics domain. At the time we didn't quite anticipate that Presto, a distributed SQL query engine for big data analytics, would be adopted around the globe by thousands of companies and an overwhelming number of industries. We appreciate Facebook for serving as the launchpad that inspired others to adopt Presto. Despite the harmonious beginnings, once the needs of the community and Facebook no longer aligned, we had to leave, but we'll get to that part shortly. ## Microsoft Retires Internet Explorer 11, Ending Support for All Internet Explorer Versions DevFeed: [Microsoft Retires Internet Explorer 11, Ending Support for All Internet Explorer Versions]() Original publisher: [Read original article]() Author: Stanko Published: 2022-06-16T00:00:00Z Content type: opinion Language: en Sources: [Stanko Tadić]() Topics: [Internet Explorer](), [browsers](), [Microsoft]() Tags: [browsers](), [internet-explorer](), [leaving](), [microsoft](), [modern]() ### AI overview An opinion piece reflects on Microsoft retiring Internet Explorer 11, which ends support for all Internet Explorer versions, and notes the shift toward modern browsers. ### Source excerpt End of an era. I started my career when IE6First time I wrote about IE6 was back in 2009. was a thing. And yesterday, Microsoft announced they are retiring IE11. With that, no version of Internet Explorer is longer supported. Over the years it seemed that we are doomed to support IE forever. We even planned celebrating when we finally don't have to. But today, it feels funny, nobody is celebrating. Modern browsers came in, slowly but surely overthrown it, leaving us with a pretty evergreen landscape today. So, IE, you weren't really a good browser, but it has been so long, so I bid you farewell! ## Ming Chan Leaves the Ethereum Foundation as Aya Joins Its Leadership DevFeed: [Ming Chan Leaves the Ethereum Foundation as Aya Joins Its Leadership]() Original publisher: [Read original article]() Author: Ethereum Foundation Published: 2018-01-31T22:10:02Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Blockchain]() Tags: [announce](), [ethereum](), [executive](), [leadership](), [leaving](), [organizational]() ### AI overview The Ethereum Foundation announces that Executive Director Ming Chan is leaving after nearly three years, while Aya joins its leadership and will support research, development, and community relationships. ### Source excerpt It is with sadness that we announce that Ming Chan, who has served as Executive Director at the Ethereum Foundation for nearly three years, is leaving the Foundation. Since her arrival in 2015, she has played a critical role in the development and success of the Foundation. We will miss the... ## No Risk No Reward DevFeed: [No Risk No Reward]() Original publisher: [Read original article]() Published: 2015-08-18T00:00:00Z Content type: opinion Language: en Sources: [Signal Blog]() Topics: [systems]() Tags: [communication](), [finance](), [learning](), [leaving](), [trading]() ### AI overview A finance professional reflects on leaving options market making and algorithmic trading to join the Open Whisper Systems team and support secure, private communication. The transition is challenging but rewarding, requiring continuous learning across technical subjects and user advocacy. ### Source excerpt After immersing myself for years and years in the world of finance (specifically, options market making and algorithmic trading), there was no escaping this mantra of "no risk, no reward." Most of the time, my (trading) style was fairly risk-averse. I knew how to find the signals of opportunities among the daily noise to reap small rewards. Fortunately, I also learned how to think about the outliers and to take the occasional big but calculated risks. Read more... ## I'm joining Dropbox DevFeed: [I'm joining Dropbox]() Original publisher: [Read original article]() Published: 2014-10-10T18:49:00Z Content type: opinion Language: en Sources: [Allison Kaptur]() Topics: [dropbox](), [Python]() Tags: [community](), [dropbox](), [inclusive](), [leaving](), [python](), [work]() ### AI overview The author announces that they are leaving Hacker School to join Dropbox in San Francisco on Jessica McKellar's team. They reflect on their time facilitating at Hacker School, how it helped them become a programmer, and their continued connection to its community. ### Source excerpt Big news for me: I'm leaving Hacker School and going to work for Dropbox in San Francisco, joining Jessica McKellar's team. I met Jessica when she was part of the first round of residents at Hacker School in fall 2012, and I've had tremendous respect for her work and leadership ever since. Dropbox has an impressive crop of Pythonistas (including Guido van Rossum, of course), and I couldn't be more excited to join. I'll be moving to San Francisco at the end of October. If you have recommendations for people to meet, places to go, or things to do, let me know! This means I'm leaving Hacker School, after more than two years facilitating. My last day will be October 24th. I love Hacker School, and I know I'm going to miss it. Hacker School is entirely responsible for the fact that I'm a programmer at all. I was working in a finance job and contemplating new careers when my brother saw this post about Hacker School's experiment with Etsy to get more qualified women into the summer 2012 batch. I read the post and the thoughtful, welcoming FAQ, then went home and picked up a Python book. Two months later, I started Hacker School. Hacker School is about becoming a better programmer, and there's no doubt that it's worked for me. For two years, I've had total freedom to chase down whatever weird thing catches my eye; I've worked with creative, hilarious, brilliant Hacker Schoolers and residents on a dizzying variety of projects; and I've been delighted to help build a more inclusive environment at Hacker School, although there's always more work to be done. (If you're a curious, sharp, and self-directed programmer, I can't recommend Hacker School enough.) I'm thankful that leaving my job at Hacker School doesn't mean leaving the Hacker School community. I'm trading in my faculty status and becoming one of hundreds of alumni around the world. I'll still be on Zulip, Community, and everywhere else Hacker Schoolers can be found, and I'll still have my cape. I may be leaving, but