/Gergely Orosz

Architecture Jams: A Collaborative Way Of Designing Software 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.

featured in #186

The Developer Culture Test: What Defines Places Where Developers Thrive? 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."

featured in #182

Surprising Things About Working At Well-Known Tech Unicorns tl;dr: Helpful advice if you're considering joining a unicorn from Gergely, from his time at Skype, Skyscanner and Uber. 

featured in #181

Tech Debt And The Pragmatic Middle Ground 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. 

featured in #179

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