I’d think organising any list by language/skills would be useful; if you’re an iOS Swift developer then you probably won’t be too interested in contributing to the Ruby on Rails codebase behind osm.org, and so on.
The point about experience is well-made - editors in particular can require quite a lot of OSM knowledge, though these days I would defer to people like @tyr_asd and @SimonPoole on that.
For Python developers I’d strongly suggest Nominatim; for C++ I would naturally suggest tilemaker (and OSRM, but that requires pretty specialist algorithm knowledge); for a Ruby dev, and in particular a fullstack-focused Rails dev, there’s quite a few low-hanging fruit on openstreetmap-website.
The problem with documentation contributions is that unless the content has been outlined in advance (and it typically isn’t), it requires quite a bit of expertise and ability to understand nuances behind the existing choices, technical limitations, etc. So it kind of goes against the principle in the OP:
But this means there is also a good opportunity for experts who know what needs to be documented but don’t have the bandwidth to actually do that themselves, to outline the documentation needs so that others can take them on.