Parent said "Go for breadth rather than depth". I dont think multiple easy bug fixes are harder then deeper one. The reason most contributions are in sparse and low-impact is that it is easier and less time consuming.
Isn't ability to maintain code better proven by maintaining one codebase longer? Mostly because that is what maintennace is?
Sounds good and of course there's more than one approach to get comparable results.
Probably as a freelancer/consultant breadth is better than depth (proves you can solve whatever problem you may have with technology X), and vice versa for employees (depth shows commitment and an emphasis on maintainability).
Isn't ability to maintain code better proven by maintaining one codebase longer? Mostly because that is what maintennace is?