balanced-employee-ip-agreement VS wundergraph

[2] https://github.com/github/balanced-employee-ip-agreement/blo...

I worked for a company and they wanted to do something similar, I think they went with something boilerplate or from an attorney. I suggested a compromise and we use something similar to the [GitHub Balanced Employee Intellectual Property Agreement (BEIPA)](https://github.com/github/balanced-employee-ip-agreement/blo...).

I'm not sure if in your circumstance they would go for it, but it worked out for me. Here is the github blog post - https://github.blog/2017-03-21-work-life-balance-in-employee...

I think this is reasonable advice, in some settings. But for many of us, I think it’s just not practical anymore.

The lines have become too blurred. I work from home, I have one office and one desk. The computer on the desk was purchased by my company but other stuff wasn’t like my mouse or my iPad. I have work Slack on my phone, which is my personal phone.

Granted, I work for a startup. This isn’t a company IT department managed laptop. It’s a MBP they had shipped directly from Apple to me.

The GitHub Balanced Employee IP Agreement acknowledges that this distinction is arbitrary and unhelpful:

> In California the main difference made by BEIPA is that IP developed with company equipment or relating to the company's business, but in an employee's free time and which the employee is not involved in as an employee, is not owned by the company (but the company does get a non-exclusive and unlimited license if the IP relates to the company's business). This recognizes that from the employee perspective, segregating one's life activities based on ownership of devices at hand or relatedness to an employer's potentially vast range of business that an individual employee is not involved with as an employee imposes significant cognitive overhead and often doesn't happen in practice, whatever agreements state.

- https://github.com/github/balanced-employee-ip-agreement

I hope that more employee agreements move this direction so we can stop trying to enforce this distinction.

I interviewed with Sysco Labs and they had some IP stuff in the contract that was absolutely bonkers. They accounted for everything, even if I died then I couldn’t pass on my IP to my kids, it would go to them instead. I asked them to remove it and replace it with BEIPA but they didn’t go for it. I asked if they would negotiate at all on any part of the contract. They said no. I walked away from that job even though I really wanted it. They showed me who they were as a company and I didn’t like what I saw.

I never really got graphql until I stumbled upon Wundergraph. (https://github.com/wundergraph/wundergraph). I have no affiliation with them except that I have been building an app with it. I'm honestly puzzled how it's not more popular. Maybe people are solving these problems in other ways? But I tried out a bunch of stuff: Vapor, Supabase, Hasura, etc. None of it simplifies building complex systems the way WG does.

I think their takes on graphql make sense: https://wundergraph.com/blog/graphql_is_not_meant_to_be_expo...

To demonstrate field usage metrics in Federation, I’ll be using WunderGraph Cosmo — a fully open source, fully self-hostable platform for Federation V1/V2 that is a drop in replacement for Apollo GraphOS.

The inverse is also true. As a technical founder, and maybe even an introvert like me, you should definitely look for a non-technical co-founder who can help you with networking, etc... I found my dream co-founder through YC Co-founder match and what can I say, it's going great. We're focusing on enterprise GraphQL/API solutions (https://wundergraph.com) and I benefit from the networking and communication abilities of Stefan, while I answer all technical questions. Tldr, I highly recommend to team up with people who complement your skills.

GraphQL Gateway is primarily responsible for serving GraphQL queries to consumers. It takes a query from a client, breaks it into smaller sub-queries, and executes that plan by proxying calls to the appropriate downstream subgraphs. When we started our journey, there was only Apollo Federation in the arena, and we used it. Still, now you can look at other options (e.g. Mercurius, Conductor, Hot Chocolate, Wundergraph, Hasura Remote Schemas), compare benchmarks and decide what's important and preferable for your needs. The Gateway provides a unified API for consumers while giving backend engineers flexibility and service isolation.

I'm a big fan of tRPC. It's amazing how it pushed TypeScript only stacks to the limit in terms of DX. Additionally, it made the GraphQL community aware of the limitations and tradeoffs of the Query language. At the same time, I think tRPC went through a really fast hype cycle and it doesn't look like we're seeing a massive move away from REST and GraphQL to RPC. That said, we see a lot of interest in RPC these days as we've adopted some ideas from tRPC and the old NextJS. In our BFF framework (https://wundergraph.com/) we've combined file based routing with RPC. In addition to tRPC, we're automatically generating a JSON Schema for each operation and an OpenAPI spec for the whole set of operations. People quite like this approach because you can easily share a set of RPC endpoints as an OpenAPI spec or postman collection. In addition, there are no discussions around HTTP verbs and such, there's only really queries, mutations and subscriptions. I'm curious what other people's experiences are with GraphQL, REST and RPC style APIs? What are you using these days and how many people/teams are involved/using your apis?

You can check out the source code on GitHub and leave a star if you like it. Follow me on Twitter, or join the discussion on our Discord server.

If you like the work we're doing and want to support us, give us a star on GitHub.