/Gergely Orosz

Ask the EM: How Can I Work Better With My Product Manager, As An Engineering Lead? tl;dr: A healthy relationship between engineering and product lead has (1) two people, one voice inside and outside the team. (2) Frequent communication. (3) Empathy towards the other. (4) Clear understanding of where roles start and end. Gergely discusses how to forge such a relationship.

featured in #200


The Cheetah Software Engineer tl;dr: "The Cheetah is a software engineer who is first and foremost very curious and blazing fast." Gergely describes common traits of such an engineer and how to manage such engineers.

featured in #197


Advice To Myself When Starting Out As A Software Developer tl;dr: 7 recommendations, including (1) read two books per year on software engineering thoroughly i.e. take notes, talk to others about it, etc... (2) Learn your language "in-depth, to the very bottom," so you understand its strengths and weaknesses.

featured in #195


Data Structures & Algorithms I Actually Used Working At Tech Companies tl;dr: "This article is a set of real-world examples where data structures like trees, graphs, and various algorithms were used in production."

featured in #193


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