Fair point. I did that, and the response (according to Google Translate) is nearly identical. Hats of the the Qwen authors and Alibaba who underwrites it.
@mikeyan320. Curious, how is simplify.jobs handling the labeling/disambiguation of skills and platforms? I've been working in this domain for a few years and have identified this problem as a significant obstacle. I open-sourced struct-ure/kg, a knowledge-graph of IT skills and platforms, as a possible solution: https://github.com/struct-ure/kg. I'd welcome your thoughts on the subject.
struct-ure/kg is a self-contained knowledge graph of tech skills and IT stuff (software, platforms, etc.). It presents a GraphQL API to retrieve information from the graph. Transparent management of the structure and content of the graph is accomplished using git. "Editing" the KG is as simple as making changes to directories and files.
I don't know about "fun", but it does offer some advantages over REST and others. I built struct-ure/kg on top of Dgraph, which auto-generates a GraphQL API from a schema definition. You should look into that if you decide to offer a GraphQL API.
As for PLDB, I'm impressed. That's a lot of data on programming languages! struct-ure/kg is designed to encompass all sorts of IT stuff. If you'd like to contribute to building out the "programming languages" sub-graph, I'd definitely welcome the help.
I think it (price deflation) has definitely discouraged many.
But back to my point, we only ever seem to talk about crypto from "how much is it worth compared to a dollar?" When did the utility of an alternate currency take the backseat, and how long must it stay there? (he asked rhetorically)...
Nectr - a place for IT professionals to maintain an free, accurate, sharable profile of their skills, experience and availability: https://nectr.network
I've always wanted this service, so even if I'm the only user, I'll keep it online.
I get a dozen or so emails weekly from recruiters asking if I'm available. Often, it's clear that the sender has no idea about my background and is just using what I call a "spray and pray" strategy for finding candidates for their job.
I have a Gmail filter in place that looks for keywords in incoming mail ("urgent requirement", "formatted resume", etc) and sends a canned response which includes my Nectr profile. In my profile they can see if I'm available, my rate, whether my skills are really a fit for their position.
That's interesting. Note that with Nectr the way it stands, you could do all of this. Just append .json to your public profile link and you get your profile in JSON. You can transform it anyway you like.
I'm planning on opening up our GraphQL API to profile owners too, so that you could edit your profile programmatically.
I definitely think there should be, and my project (Nectr, https://nectr.network) is an attempt at a standard format. Along with the common things (job history, education, et.al.), we also try to pin your abilities (skills, platforms, etc) to entries in our knowledge graph of IT skills and platforms; and we encode availability in a standard way. IMO, these two aspects are crucial to finding the right talent, when they are available.
