DEV Community

Discussion on: The Layout Team

Collapse
woile profile image
Santiago Author

Thanks for the feedback!

Regarding the formatting, I copied from my blog which uses also markdown, but it seems they don't render the same way. Already corrected.

I totally agree that the main point is get people to talk to each other. With this post, I wanted to throw into the pool an idea in case you have this problem.

How's the situation in your company?

Collapse
ekeijl profile image
Edwin • Edited on

There's a weekly architecture meeting where developers can discuss anything technical, improvements, interesting architecture concepts, best practises, etc. Most of the time, the topics that are discussed are related to the features that we're building, but not always. Developers can create user stories for technical improvements, every sprint has a budget of X story points for this kind of user stories.

We're gradually moving towards a mono-repo approach to make sharing code across the whole codebase easier to manage and to standardize internal libraries. So far it has proven useful to stay in control of changes to the codebase (with semantic versioning). It also helps with separation of concerns because every package has its own scope, while the code is still co-located in one repo.