We're sunsetting PodQuest on 2025-07-28. Thank you for your support!
Export Podcast Subscriptions
cover of episode Story: Leaving LinkedIn - Choosing Engineering Excellence Over Expediency

Story: Leaving LinkedIn - Choosing Engineering Excellence Over Expediency

2024/3/4
logo of podcast CoRecursive: Coding Stories

CoRecursive: Coding Stories
AI Deep Dive AI Chapters Transcript
People
A
Adam Gordon-Bell
C
Chris Krycho
Topics
Chris Krycho讲述了他五年LinkedIn工作经历中面临的挑战，以及最终因无法调和对工程卓越的追求与公司对快速发展的优先级而选择离职的故事。他详细描述了在处理大型代码库（超过300万行代码）时遇到的问题，包括引入JavaScript类、处理大量错误以及从Ember.js迁移到React的计划。他强调了自动化在大型代码库迁移中的重要性，以及可持续的工程实践与业务需求之间的冲突。他批评了另一个团队提出的快速迭代方案，认为该方案缺乏对技术债务和系统稳定性的考虑，并最终导致了系统故障。他认为，公司对速度的过度追求导致了技术债务的累积，并最终损害了长期价值。他个人在事件中也反思了自己的不足，例如在人际关系和沟通方面的不足。 Adam Gordon-Bell作为主持人，引导Chris Krycho讲述了他的故事，并对故事中涉及的技术问题、管理问题和文化冲突进行了深入的探讨。他帮助Chris Krycho理清了事件的脉络，并对Chris Krycho的观点和感受进行了总结。他提出了关于技术债务、工程文化和沟通的重要性等问题，并与Chris Krycho进行了深入的讨论。 Jim作为另一个团队的资深工程师，代表了公司对快速发展的优先级。他与Chris Krycho在工程实践和价值观方面存在分歧，对Chris Krycho提出的长期方案持否定态度，并认为代码审查可以解决所有问题。他的观点代表了公司中一部分人对快速迭代和短期利益的追求。 Dave作为Fingerguns团队的经理，在系统故障事件中接管了应急响应工作，并对Chris Krycho团队的工作表示不信任。他的行为反映了公司中一部分人对快速解决问题的需求，以及对长期方案的缺乏耐心。

Deep Dive

Shownotes Transcript

What if your dedication to doing things right clashed with your company’s fast pace? Chris Krycho faced this very question at LinkedIn.

His journey was marked by challenges: from the nuances of remote work to the struggle of influencing company culture, and a critical incident that put his principles to the test against the company’s push for speed.

Chris’s story highlights the tension between the need for innovation and the importance of project health. This all led Chris to a pivotal decision: to stay and compromise his beliefs or to leave in pursuit of work that aligned with his principles.

He chose the latter. Join us as we dive into Chris’s compelling story, exploring the challenges of advocating for principled engineering in a world that often prioritizes quick wins over long-term value.