You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: