4 ms·
When I join a new software project I usually know nothing about the problem domain either. And sometimes not even about the tools or languages used. But that is
by danbruc 6y ago
When I join a new software project I usually know nothing about the problem domain either. And sometimes not even about the tools or languages used. But that is not a problem because the skills actually required are the ability to become familiar with unknown problem domains and the ability to use your general knowledge about software development to make use of whatever language, framework, or tool the project asks for.
- spaetzleesser 6y ago“But that is not a problem because the skills actually required are the ability to become familiar with unknown problem domains and the ability to use your general knowledge about software development to make use of whatever language, framework, or tool the project asks for.” I think a lot of projects suffer from the fact that the people working on it don’t have deep domain knowledge. A lot of attempts to “disrupt” an industry fail because they don’t understand the status quo.
- danbruc 6y agoI mean I am developing custom business applications, the customer and also the in-house developers have the knowledge. But sure, if you are trying to build a product you want to sell, then you or at least your team or company should certainly have deep domain knowledge. But this seems also really self-evident, how would you even build a product for something you do not understand? And whoever had ever to become familiar with a new domain will probably know this - from the outside and with no or limited knowledge things look often not very complicated, but once you dig into it, even the simplest looking domain has very deep rabbit holes everywhere.