mdlincoln

Prolific | Senior Software Engineer | Hybrid ONSIDE 1-2 days/wk Bay Area | $200k-$250k

Prolific is not just another player in the AI space – we are the architects of the human data infrastructure that's reshaping the landscape of AI development. In a world where foundational AI technologies are increasingly commoditized, it's the quality and diversity of human-generated data that truly differentiates products and models.

We’re looking for impact-focused Software Generalists to join our specialized team focused on serving frontier model creators and enterprise AI application developers. As a full-stack engineer, you will work across Prolific’s domains to solve customer and product problems.

This is an exciting opportunity to work directly with frontier AI companies, making critical technical decisions that balance scrappy startup execution with scalable, reliable engineering, as Prolific revolutionizes research for the AI community. You'll will have regular in person collaboration with customers and our US team, as well as collaborate closely with our UK-based tech teams.

Unfortunately we don't sponsor US visas at this time.

Apply: https://job-boards.eu.greenhouse.io/prolific/jobs/4767348101

context-dependent, or "reified" assertions are a pain point for sure. I come from the perspective of cultural heritage data, where context is king. Which expert made this attribution for this painting? Who owned it _when_? According to which archival document? etc.

Almost all the engineering problems cited in the original post are still basically there, but graphical models are still the least painful way of doing this, particularly when trying to share data between institutions. Example: https://linked.art/model/assertion/

You may be interested in what Birkbeck has been developing: https://github.com/BirkbeckCTP/janeway

Just commenting to add this wonderfully succinct summary of the post by John Overholt:

>It takes a tremendous amount of work to make the work that goes into photographing this goblet invisible.

https://twitter.com/john_overholt/status/991110369082068992

Several hundred publications from the Getty Museum (and the other research arms of the Getty) are available for free download as well: https://www.getty.edu/publications/virtuallibrary/

(I work at the Getty Research Institute)

I find that a fascinating reaction given how rapidly %>% have been taken up across a large segment of the R universe, to great excitement! Personally, I find it far MORE legible than endlessly-nested function calls.

It results in code that more closely resembles executed order of operations (e.g. filter -> mutate -> group -> summarize). Context is also key: it's most often used for data processing pipelines in specific analytical scripts or literate-code documents - less so used when defining generalizable/testable functions in packages (again, just a personal perspective - YMMV of course)