Group by technologies

[agusluques]

I'd would be great if you ask for the technologies required for each position. It will be easier to search and will avoid people to open each link.

Instead of a list it could be a table with some extra information like technologies, salary range, etc.

You can even automate this once #138 is ready.

[alexpdp7]

We had similar discussions in #11 and #54. I am not convinced that we should do this.

The small argument against it is that there is a good amount of large companies in the list that use many different stacks. We could always omit those, though- but you'd still need to open them to check...

The big argument is that we really don't have good mechanisms to keep the list updated and having outdated information can be quite harmful.

Imagine most companies in the list show the programming language they use. Then I'm looking for a job and I only open links for languages I like. I will immediately miss any companies for which a) we don't have this information b) they incorporated the use of such language after we added them to the list and... we can't keep track of them all in a reasonable amount of time.

IMHO, doing this only has a valid, but in my opinion, minor benefit (you need to open less links)... and a big drawback: it's easy to ignore accidentally companies that you would otherwise check out.

An alternative I have posted in the past is creating a separate space to post specific job offers. For example, the "discussions" section in GitHub. In those, it would be natural to post the technologies being used. However, in the past other maintainers were reluctant to explore this option.

...

On the other hand, we have currently lost one maintainer¹ and we have one less than I would like. Would you be interested in becoming a maintainer? @smoya I know this is a bit "eager", but thoughts?

(I recently read an article somewhere that said project maintainers should be more "carefree" adding maintainers to a repo...)

Footnotes

1. Strictly speaking, we lost two, and managed to recruit another. ↩

[smoya]

On the other hand, we have currently lost one maintainer1 and we have one less than I would like. Would you be interested in becoming a maintainer? @smoya I know this is a bit "eager", but thoughts?

(I recently read an article somewhere that said project maintainers should be more "carefree" adding maintainers to a repo...)

Always 👍 to welcome new maintainers!