13 ms·
Thank you! Would it be more helpful to break this into separate repos by every geography? We have a "remote" folder at the moment: https://github.com/zcor/gith
by ghall 7y ago
Thank you! Would it be more helpful to break this into separate repos by every geography? We have a "remote" folder at the moment: https://github.com/zcor/githubjobs/tree/master/remote https://github.com/zcor/githubjobs/tree/master/remote
- yayajacky 7y agoThanks for replying, I saw the remote folder, that’s a good direction, I just don’t know if with github I can watch that single folder for communication. - from a remote contractor
- gwbas1c 7y agoThe problem is that job openings are often for multiple locations. (You can work in our SF or NYC offices.) In general: Try to avoid organizing your data in hierarchies, and instead navigate by filters. (This is why SQL won over older hierarchal databases.)
- ghall 7y agoWe've also been talking about in organizing this into a SQL-like interface, I think there could be a lot of value in job hunting in such a manner... "SELECT * FROM jobs WHERE location = 'seattle' and keyword LIKE '%python%'"
- yayajacky 7y agoIf the keyword column is a json blob, you might be able to do it with JSON_CONTAINS: https://dev.mysql.com/doc/refman/8.0/en/json-search-functions.html#function_json-contains https://dev.mysql.com/doc/refman/8.0/en/json-search-function... (Unless you are using mongo on the backend, in which case I am not familiar with that)