Thanks for these insights. I think this is a great approach. The question is, how to best facilitate these short/demo reviews without creating too many context-switches and interruptions for everyone. We're actually working on a platform that tries to solve this (https://livecycle.io/) by generating instant, collaborative PR preview environments. So the kinds of reviews you describe can happen async and in context. Do you think this approach would work to facilitate the reviews you outline here?

I'm talking about products intended for devs, developer tools. I'm asking about ways people found for getting early adopters to try it and provide their feedback.

Great advice. Thank you.

And If I had to choose for the purposes of my question, I'd say front end developers specifically

I didn't see it until now - thanks for sharing the link!

Interesting. How big is your company? Are you in person or remote? I wonder if it depends on the setup and profile of the company...

I’m at a FAANG+, in a team working on B2B enterprise products (SAAS). Previously I was in consumer electronics and B2C, but even then there was a healthy relationship between design and eng.

I’ve been remote for about 5 years.

What are specific examples of friction you’re encountering ?

What is FAANG+ I know the acronym but not the plus? Is it some kind of formula one league within FAANG?

FAANG has evolved from the acronym about rising stocks into a term representing companies that pay high salaries in SWE circles.

If you see FAANG+ they might be referring to companies like Data Dog or SalesForce or Crowdstrike, companies that pay extremely well but maybe not as much as Meta or Netflix.

At least that's how I read it.

Thank you for that explanation.

It means that they don’t work at FAANG.

I’m No longer at a FANG but somewhere that has same pay/perks but I can WFH always!

Thanks! Do you think it would help if you had a live preview environment that came with every PR, so you could better understand the context of the changes you are reviewing?

I'm old school which means tags and cscope. I need to be able to walk the function paths of complex code in a terminal. I simply don't see how other folks can review code by staring at pages of code without similar context.

I agree 100%. The question is how to facilitate this collaboration/compromise between developers. We've actually built a developer collaboration platform called Livecycle (https://livecycle.io/) that lets developers collaborate/comment on a live PR preview environment. Do you think this could help with the pain point you are describing?

Thanks! Do you think it would help if you had a live preview environment that came with every PR, so you could better understand the context of the changes you are reviewing?

That would help, definitely! Unfortunately, I think the overhead would be too much for some organizations.

Thanks! Great point

Sign up and try our self-serve here: https://livecycle.io/