Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposition for cross functional teams #1

Open
yungwarlock opened this issue Jan 23, 2022 · 1 comment
Open

Proposition for cross functional teams #1

yungwarlock opened this issue Jan 23, 2022 · 1 comment

Comments

@yungwarlock
Copy link

Hi, I'm really happy to find to something like this. I've been giving a lot of thought on this lately.
I just needed your thoughts on this.

Take an hypothetical team of engineers that are organised based on certain feature that would be deployed both on the backend on client applications (web, mobile and via public APIs). So each team is responsible for the servers and client packages. How would their organise the code to reflects their team while allowing easy sharing of common packages between teams. Example would be a hashing library or a Hero component package.

@yungwarlock
Copy link
Author

Looking at your own structure, I'd say I could implement it in flat manner. No hierarchy. But, I'd want some sense of ownership for a package or feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant