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

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

Honeycomb

I understand why: the stakes for public comment become higher as you move up the ladder, every social media post has the potential to be interpreted as a subtweet or request, and your highest-priority work is often deeply entangled with confidential company and personnel matters.

article thumbnail

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

Netlify

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. So I tend to get as much work done as possible and also review PRs in the afternoons and then reserve the evenings for meetings/syncs with my colleagues. I love all of our social Slack rooms.

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

We’ve witnessed or directly experienced racist injustice, social unrest, and state violence. Wildfires and hurricanes didn’t take a vacation in 2020, and our distributed team managed to get hit with both simultaneously, multiple times. A better tech industry is better for supporting this complex, interdependent society we live in.

article thumbnail

2020: The Year Bee-hind Us

Honeycomb

We’ve witnessed or directly experienced racist injustice, social unrest, and state violence. Wildfires and hurricanes didn’t take a vacation in 2020, and our distributed team managed to get hit with both simultaneously, multiple times. A better tech industry is better for supporting this complex, interdependent society we live in.

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.