3 ms·

Isn’t your custom framework exactly what I said? Use an existing one , or write one that only you (and your team) know. Of course, the bigger your codebase and

• Zababa 5y ago
  > Isn’t your custom framework exactly what I said? No, it's not. > Use an existing one , or write one that only you (and your team) know. Not only my team, pretty much any people working with it in the company. The difference with something like Django is that people don't know it before coming in the company, which doesn't make a big difference. To go back to the message I replied to, you said > "They either use an existing framework, or they eventually end up creating a custom framework which only they understand and which gets thrown out and replaced with a common framework when they leave the company." I disagree. There's no reason to replace our custom framework, as it's working well and since the codebase is getting a bit old, this would be just too much. We also have good training material around it, better than what you can usually find about open source framework online, without even mentionning mentoring. Then there's > "At the least, they give new devs a common understanding to begin from when they join or take over an existing project." The flip side of that is that you need to recruit developers that know a framework, which will by definition limit your talent pool.