5 ms·
This reminds of a conversation I overheard at a previous job where the devs on another project decided to build their own backend framework. I knew the requirem
by michaelmior 6y ago
This reminds of a conversation I overheard at a previous job where the devs on another project decided to build their own backend framework. I knew the requirements pretty well and I begged them not to. A few months later they had left and I inherited the project with their homegrown framework. Since the project was still fairly new, eventually we made the decision to toss it all and start from scratch.
- tester756 6y agoI'd want to assume good faith here, but it's difficult
- andi999 6y ago"....toss it all and start from scratch." with a different homegrown framework :-) (this time done right, of course)
- michaelmior 6y agoActually, we ended up going with Django. Partially because the devs we were able to hire at the time knew Python well.
- dvfjsdhgfv 6y agoThis is a very common story. The people who push for that do it for two reasons (1) they don't feel competent enough to use a popular solution that would fit better and ensure a more stable future for the project, and/or (2) they realise it might help them to hold their position longer if they author their own solution. It's important the management realises that.