nicolasbistolfi

Any company needs processes, they are clearly more necessary for a remote-first company.

It's important to be pragmatic and don't over-design processes. I believe some companies take advantage of being remote to micro-manage or add extra layers of control over their employee's work-life.

Besides that, there's no point on generating extra information that no one will ever review or use to take action.

For me, key processes should focus on: - Team communication - Simple day to day reporting - Self-management tools and goal-oriented thinking

I've learned a lot from Zapier's guide but I think some stuff might be an overkill https://zapier.com/learn/remote-work/

Here is a draft we are working on at my company https://www.notion.so/piio/The-Ultimate-Guide-to-Work-at-Piio-fb3b341e30be454cba6cc760aee4103e

If your startup is building a developer tool, getting initial traction might be a nightmare. Developers are incredibly hard to pitch to, traditional marketing strategies won't work and even guerrilla marketing might annoy them.

So, I'm asking for a friend here...

How to find the appropriate channels? How long to test each channel? How to identify key partners?

So for standard HTML website, you can use tools like Web Page Test (webpagetest.org) or any other proprietary tools like GTmetrix.

The problem is that when you have an SPA built with React, Angular, Vue or any other framework, your first-page load will download all the packaged JS and CSS files.

One way I managed to better compare SPA with a standard web is to use this equation to get the Average Page Load Time:

Average Page Load Time = (LT / PS) + APL

LT - Load Time PS - Pages Per session APL - Average In-between Page Load Time (measure the time going from the home-page to the second page, like a catalog)

What do you guys think? And how are you guys managing this issue?