2 ms·
Developing components like this puts a lot of pressure on the components to each look like a piece of Real Software. Versioning, stability, changelogs, coordin
by gorgoiler 4y ago
Developing components like this puts a lot of pressure on the components to each look like a piece of Real Software.
Versioning, stability, changelogs, coordinating new features as beta releases followed by deprecation announcements and finally deprecation. None of this is unreasonable, technically — my Linux OS is made of many small stable projects after all, none of whom communicate with each other beyond broadcasting NEWS.md etc with each release.
It’s also exhausting. Do your competitors hamper themselves by cosplaying a bazaar of open source projects coordinated by whatever your internal equivalent of the Debian project is? No! Move everything under one roof to truly reflect your org structure and take advantage of the fact that you all report to one CTO, you all have real-time communication between each other, and you probably know where everyone else is sat for eight hours a day. Move fast.
- ghc 4y ago> take advantage of the fact that you all report to one CTO How many companies even have a CTO that knows or cares about version control? In most companies version control is managed by IT if at all, and code for different products is split across different lines of business.