2 ms·
This is why I have found that strong interfaces and assembling teams and developers around those libraries and interfaces, helps them to isolate code away from
by kls 16y ago
This is why I have found that strong interfaces and assembling teams and developers around those libraries and interfaces, helps them to isolate code away from the developers own code. What this does is get's the team used to looking at other developers code as a block box library in much the same way you would look at a third party jar in java or a gem in Ruby.
When it becomes a library to them, then they stop thinking about it in terms of code and start thinking about it in terms of components that provide functionality. In the enterprise SOA is very aligned to this concept where disparate teams stand up services and the interface become other teams end point in and out of the black box.
Teaching developers to black box code can go along way to curing the I did not write it attitude and forces the developer to document how to use there black box.
- Pyrodogg 16y agoYes. Having pretty clear, hashed out guidelines and a component style to your architecture can do much to ease the itch some might feel to rewrite things. Clear documentation and a parameter list to the black box you're calling are all you should need to get started on a new piece to the system.