My $EMPLOYER is a large organization, and I've been working on a team that's been in ship fast mode for a while. Which has been frustrating since I strongly value trying to build things well, but...
My $EMPLOYER is a large organization, and I've been working on a team that's been in ship fast mode for a while. Which has been frustrating since I strongly value trying to build things well, but shipping fast meant cutting corners that often came back to bite us. And iterating on what we built was seldom a priority.
I found a lot of value listening to the interviewee, Chris Kycho, discuss how their entire job was trying to help engineers build things well at the scale of LinkedIn's entire monorepo. But prorities shifting away from build well to ship fast ultimately made him leave.
Synopsis:
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.
There is a transcript for anyone who would prefer to read the content instead.
My $EMPLOYER is a large organization, and I've been working on a team that's been in ship fast mode for a while. Which has been frustrating since I strongly value trying to build things well, but shipping fast meant cutting corners that often came back to bite us. And iterating on what we built was seldom a priority.
I found a lot of value listening to the interviewee, Chris Kycho, discuss how their entire job was trying to help engineers build things well at the scale of LinkedIn's entire monorepo. But prorities shifting away from build well to ship fast ultimately made him leave.
Synopsis:
There is a transcript for anyone who would prefer to read the content instead.
edit: grammar