The only way to deal with the unstructured nature of the "Who is hiring" posts is to have some sort of schema that can be processed. I also wanted to do something similar (imagine it with dc.js, for example!), but the data is too diverse.
All posts could have a METADATA: compressed_json entry that can be processed by the site and displayed/filtered accordingly. Perhaps it could be built manually at the beginning until it catches up.
Comments
The only way to deal with the unstructured nature of the "Who is hiring" posts is to have some sort of schema that can be processed. I also wanted to do something similar (imagine it with dc.js, for example!), but the data is too diverse.
A sample entry could be:
All posts could have a METADATA: compressed_json entry that can be processed by the site and displayed/filtered accordingly. Perhaps it could be built manually at the beginning until it catches up.dev_type: 'Web/Mobile/Data/Design/Hardware' at least.
Sure, there are many things that could be improved.
Anyhow, I'm surprised. I'm a Hardware Engineer myself, so how could I miss that!