3 ms·
Reminds me of a company I used to work at which took a similar approach. We used one file per person policy, each developer had their own file that contained fu
by journey_16162 4y ago
Reminds me of a company I used to work at which took a similar approach. We used one file per person policy, each developer had their own file that contained functionality developed by them, named like firstName_lastName.ext - everyone owned their file so we didn't have to worry about merge conflicts.
- deleted 4y ago[deleted]
- hot_gril 4y agoOn the team at my day job, it'd be very bad for each person to strictly "own" their code like that because things get handed off all the time, but in some other situations I can see it making sense.