Engineering Culture

# Engineering Culture - All Guest Insights

*19 guests, 23 mentions*

---

## Albert Cheng
*Albert Cheng*

> "The product experience of Duolingo actually changes multiple times per day for each user... they care a lot about the clock speed of the company... they were really, really tight about it."

**Insight:** A high-performance engineering culture can be built around extreme experimentation frequency and tight, consistent processes.

**Tactical advice:**
- Optimize for 'clock speed'—the frequency with which the product can be updated and tested.

*Timestamp: 00:35:46*


## Brandon Chu
*Brandon Chu*

> "When I joined, all project management was just in GitHub, just commenting on poll requests and even marketers in order to augment or upload a blog post, you'd have to commit and deploy it. So there was no breaks given for folks that didn't want to touch code and stuff like that."

**Insight:** A strong technical culture is built by requiring all functions to engage directly with the technical tools and workflows of the engineering team.

**Tactical advice:**
- Use GitHub for project management to keep PMs close to the code
- Require non-technical roles to understand basic deployment workflows

*Timestamp: 09:20*


## Chip Huyen
*Chip Huyen*

> "CS is about system thinking, using coding to solve actual problem and problem solving will never go away because what AI can automate more stuff. The problem is just get bigger."

**Insight:** As AI automates syntax and basic coding, the core value of engineering shifts to 'system thinking' and holistic problem solving.

**Tactical advice:**
- Restructure engineering teams so senior engineers focus on peer review and architectural guidelines
- Train engineers to look at how different components interact rather than just local code fixes

*Timestamp: 00:52:27*


## Dhanji R. Prasanna
*Dhanji R. Prasanna*

> "I learned the most throughout this process is that Conway's Law can be really, really powerful. So it's the law that basically says you ship your org structure. So what you're organized as in terms of teams, in terms of collaborating groups and your operating model matters a lot to what you build."

**Insight:** Organizational structure directly dictates the architecture and quality of the products being built.

**Tactical advice:**
- Align technical strategy across silos to ensure teams speak the same language
- Standardize leveling and policies (e.g., what a senior engineer means) across the entire organization

*Timestamp: 00:12:13*

---

> "A lot of engineers think that code quality is important to building a successful product. The two have nothing to do with each other. ... It really has very little to do with how well it was architected because the flip side of that Google video... supported more formats, it supported higher resolution... YouTube had none of this. It just had the one or two minute quick video thing and it's far and away, blown away its competition."

**Insight:** Product success is driven by solving user problems, not by the underlying architectural elegance or code quality.

**Tactical advice:**
- Prioritize solving the core customer problem over refactoring or perfect architecture
- Be willing to accept 'controlled chaos' and technical messiness if it enables rapid experimentation

*Timestamp: 01:02:02*


## Gergely
*Gergely*

> "I'm typically interested in the stuff that you might not read about in the traditional media, but us techies really care about... I wrote one about Facebook, one about Amazon, and I tried to talk with mostly software engineers to get a sense of how these companies work from a software engineer and engineer manager perspective."

**Insight:** True engineering culture is best understood by analyzing the lived experiences and internal processes of individual contributors rather than official company narratives.

**Tactical advice:**
- Conduct qualitative interviews with engineers across different levels to map out the reality of a com