/Gergely Orosz

Tech Lead Expectations for Engineering Projects tl;dr: Framework of how Gergely manages his team at Uber including the initial team setup, how risks are managed, stakeholder communication and more.

featured in #166


A Comment Is An Invitation For Refactoring 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.

featured in #164


Yes, You Should Estimate Software Projects 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.

featured in #159


Software Engineering Promotions: Advice to Get to That Next Level 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.

featured in #156


Developers Mentoring Other Developers: Practices I've Seen Work Well tl;dr: Comprehensive guide to mentorship practices that work well, based on the author's experience working at Uber.

featured in #152