tl;dr:Gergely provides a useful framework for how to conduct jams, starting with (1) be mindful of who you invite (2) start with the goal (3) lay out constraints and principles.
tl;dr:The test comprises of 3 areas, with 5 questions each, to help evaluate whether an organization has a healthy culture. Any "decent tech company" should have the 3 basic points nailed, and "cover at least 4 out of the 5 points in each area."
tl;dr:For startups, having enough tech debt is critical. Having "too little is premature optimization". In the early phase of a company, you want tech debt to be heavy, allowing for the company to move quickly.
tl;dr:A comment is usually a sign that a piece of code needs refactoring. Greg wants us to ask "could I refactor the code to remove this comment?" The answer is typically yes. He highlights three common examples of comments.
tl;dr:Businesses are date driven so should engineering teams be. It's a hard skill, and when estimates are wildly off, there's an opportunity to introspect and improve. Meeting estimates build trust. The key is communicating feature changes and tradeoffs with the business early on.
tl;dr:Guide on approaching a promotion - (1) do your preparation (2) set your sight on the promotion (3) get help & frequent feedback (4) put in the work (5) stay grounded (6) help others.