Remove Engineering Culture Remove Engineering Management Remove Software Review Remove Technical Review
article thumbnail

On Becoming a VP of Engineering, Part 1: The Path to VP

Honeycomb

VPs of Engineering often have a lot of influence over both company culture and policy, and the decisions our companies make ripple outside of the companies themselves. The whole tech industry would benefit from more perspectives in this role. A generalist streak.

article thumbnail

What it’s like to be a backend engineer at Netlify

Netlify

Running untrusted code in-process and ensuring it doesn’t spend too long executing and doesn’t block the whole process. As an engineer based in the EMEA (Europe, Middle East, Africa), I usually start my work day earlier than folks in the Pacific time zone. Improving our data pipeline. Pairing sessions also help a lot too.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

2020: The Year Bee-hind Us

Honeycomb

In March I wrote the following: Observability is a paradigm on which we can build a safe, healthy, sustainable future for the tech industry. A better tech industry is better for supporting this complex, interdependent society we live in. No Q4 code freezes for us. no oversharing or prying). instrumegrations) questions. .

article thumbnail

2020: The Year Bee-hind Us

Honeycomb

In March I wrote the following: Observability is a paradigm on which we can build a safe, healthy, sustainable future for the tech industry. A better tech industry is better for supporting this complex, interdependent society we live in. No Q4 code freezes for us. no oversharing or prying). instrumegrations) questions. .

article thumbnail

On Becoming a VP of Engineering, Part 2: Doing the Job

Honeycomb

This is particularly hard on engineering teams, where we always have to balance multiple priorities: security, reliability, performance, UX, shipping new features, iterating on existing features, internal developer experience, maintainability/tech debt, quality, scaling, etc.