/Gergely Orosz

Working At A Startup Vs In Big Tech tl;dr: Willem, who Gergely met at Uber, share his experience and insights working as a developer, transitioning between startups and big tech companies. Willem recalls the "rapid skill development" and "direct influence" at startups, juxtaposed with the financial uncertainties and heightened stress. Big tech provided a platform for deep domain expertise, financial perks, and expansive networking, albeit with potential bureaucratic hurdles and diluted individual impact. “Doing work that results in a great performance review is not always the same work that best helps the company. And this can create pretty twisted, political situations.”

featured in #453

How Microsoft Does Quality Assurance (QA) tl;dr: Microsoft's approach to Quality Assurance (QA), focusing on the Software Development Engineer in Test (SDET) role. The SDET role was designed for engineers who focused on writing automated tests and maintaining testing systems. "An SDET is a developer who works in a test team and not a development team." This role was retired around 2014, as Microsoft moved towards a more integrated approach where all software engineers became responsible for testing their code.

featured in #450

Building Meta’s Threads App (Real-World Engineering Challenges) tl;dr: “Building Threads was a whirlwind. We started in January 2023 and launched in June 2023. Five months from zero to one of the fastest-growing apps ever,” which saw 100M downloads within five days of its launch. Gergely covers": (1) Building Threads. (2) Technology choices and engineering approaches. (3) Planning for launch. (4) The launch. (5) Learnings and next steps.

featured in #446

Measuring Developer Productivity? A Response To McKinsey tl;dr: “We wrote this article for software developers and engineering leaders, and anybody who cares about nurturing high-performing software development teams. By “high performing” we mean teams where developers satisfy their customers, feel good about coming to work, and don’t feel like they’re constantly measured on senseless metrics which work against building software that solves customers’ problems. Our goal is to help hands-on leaders to make suggestions for measuring without causing harm, and to help software developers become more productive.”

featured in #444

How Games Typically Get Built tl;dr: Insights into the world of game development, contrasting it with traditional software development. Game development involves programmers, designers, artists, animators, writers, and sound designers. Games typically undergo a prototype stage, followed by full production, where multiple teams work in parallel, often leading to integration challenges. The game development life cycle consists of three main phases: pre-production, production, and release. Gergely emphasizes that while game development borrows practices from software development, such as TDD and agile methodologies, it requires adaptations to fit the unique challenges of the medium.

featured in #442

A Senior Engineer / EM Job Search Story tl;dr: The job search experience of Davidson Fellipe, a lead software engineer with over 15 years of experience. The article highlights the challenges and strategies of job searching in the current market, with insights into interview processes and time management. Fellipe embarked on a three-month search, focusing on engineering manager roles. He utilized tools like spreadsheets, Teal application tracker, Simplify, and Notion to stay organized. Fellipe also emphasized the importance of referrals and crafting tailored resumes. He eventually received one engineering manager offer and two individual contributor offers, accepting a senior engineer position.

featured in #439

What Is A Senior Software Engineer At Wise And Amazon? tl;dr: Gergely delves into senior software engineer roles at Wise and Amazon. At Wise, senior engineers lead significant projects, contribute to feature planning, and require good communication and problem-solving skills. At Amazon, the equivalent role deals with ambiguity, leads projects, communicates technical ideas efficiently, and ensures that the team's success doesn't solely rely on them. While definitions of 'senior' vary across the two companies, clear expectations across companies include project leadership, problem-solving skills, and effective communication.

featured in #436

Interesting Learnings From Outages tl;dr: The article discusses the importance of investigating and learning from outages in the industry. It explores the different types of postmortems, including internal, customer-only, and public postmortems. The article dives into 3 case studies: (1) Adevinta experienced a significant impact due to a DNS outage, (2) GitHub experienced an outage due to a network configuration issue at their secondary site, (3) Reddit experienced an issue with a Kubernetes cluster upgrade gone wrong."

featured in #432

An Explosion In Software Engineers Using AI Coding Tools? tl;dr: What do AI coding tools help the most with? The survey lists the top areas mentioned by developers: (1) Learn: develop coding language skills (57%). (2) Productivity: become more productive (53%). (3) Focus: spend more time building and creating, less on repetitive tasks (51%). Gergely dives how engineers are leveraging AI tools.

featured in #423

Should You Optimize For All-Cash Compensation, If Possible? tl;dr: “Although still rare in the industry, companies like Netflix and Shopify let employees choose how much of their total compensation is stock. What are the approaches to take?”

featured in #421