/Gergely Orosz

What Big Tech Layoffs Suggest For The Industry tl;dr: Gergely discusses rapid shifts in the engineering job market. "It’s certain we’ll see a correction of 2021-22’s hiring frenzy and it’s a given that Big Tech will hire much less this year than in 2022, while the question remains whether other large tech companies will follow suit and announce layoffs in the coming months."

featured in #382


Real-World Engineering Challenges #7: Choosing Technologies tl;dr: Gergely interprets the following software engineering or engineering management case studies from tech companies: (1) Trello choosing Kafka over RabbitMQ for messaging. (2) Why Birdie moved to Micro Frontends. (3) Why MetalBear settled on Rust. (4) Why Motive moved over to Kotlin Multiplatform Mobile.

featured in #371


The State Of Frontend In 2022 tl;dr: Gergely covers topics such as How Frontend Engineers Work, Engineering Practices, Technologies, Developer Tools, and more. "27% of respondents reported working at a company with more than 50 frontend engineers. At the same time, 30% of developers shared how 5 or fewer frontend developers work at their company. 50% of respondents work at companies with 10 or more frontend engineers."

featured in #367


Real-World Engineering Challenges #6: Migrations tl;dr: Gergely covers examples of companies that have carried out large scale migrations, including: (1) Box: a zero downtime data migration using a 6-step plan. (2) Pinterest: data migration using double writes. (3) LinkedIn: navigating the migration chaos when 100+ engineers were needed to write code and 600+ use cases need to be moved. And more. 

featured in #359


Resiliency In Distributed Systems tl;dr: "Understanding the ins and outs of distributed systems is important for both backend engineers and for anyone working with large-scale systems. Large-scale systems can mean systems with high load and high queries per second (QPS), storing a large amount of data, or ones built with low latency and high reliability. These systems are pretty common across both Big Tech and high-growth startups."

featured in #355


Real-World Engineering Challenges #5 tl;dr: "A series in which I interpret interesting software engineering or engineering management case studies from tech companies. You might learn something new in these articles, as we dive into the concepts they contain." Includes: (1) Resilient payments systems learnings from Shopify. (2) Designing a solution to store and access millions of records by Grab. (3) The challenges of the analytics infrastructure platform team at Yelp. And more. 

featured in #348


Oncall Compensation tl;dr: Gergely dives into: (1) Oncall philosophies across the industry. (2) Companies which pay and those that don’t. (3) How much do companies pay. (4) Companies which don’t pay. (5) Poor oncall cultures.

featured in #340


The Platform And Program Split At Uber: A Milestone Special tl;dr: "More than 100 people would need to be hired across engineering, product and design, to staff these teams. The new teams were stack ranked by importance e.g. teams responsible for growing the supply of drivers were ranked much higher than those generating rider demand." Gergely discusses Uber's biggest engineering organizational change: creating cross-functional program teams and introducing platform teams.

featured in #330


Software Engineering RFC And Design Doc Examples And Templates tl;dr: "This article collects some openly available RFC templates and examples, and a list of companies that use such a process. I’d encourage to use these examples for inspiration. Take parts that resonate with you, experiment with them and modify them to your needs."

featured in #328


Shipping To Production tl;dr: "In this issue we cover: (1) The extremes of shipping to production. (2) Typical processes at different types of companies. (3) Principles and tools for shipping to production responsibly. (4) Additional verification layers and advanced tools. (5) Taking pragmatic risks to move faster. (6) Deciding which approach to take. (7) Other things to incorporate into the deployment process.

featured in #320