Urgent.News

What's breaking now, across thousands of outlets.

Tech

Coordinating two open projects in 3 hours a week — a paid first assignment, evidence over resumes

I'm Josiah — founder of ClearOpsHub, a small San Diego project building a dashboard for tracking tasks, job status, delivery evidence, and human approvals. I also maintain hr-project-map, an open-source model of person -> responsibility -> project -> task -> deliverable -> evidence -> verification -> completion. I need a part-time project coordinator: contract, remote, up to 3 hours per week. Not…

Josiah, the founder of ClearOpsHub, a San Diego project focused on tracking tasks, job status, delivery evidence, and human approvals, is seeking a part-time project coordinator. The role is contracted, remote, and limited to 3 hours per week. Unlike typical job postings, the selection process prioritizes evidence over resumes.

The initial assignment, paid and agreed upon in writing before work begins, involves 30 minutes reviewing the current project state, 60 minutes running one milestone against testable acceptance criteria, and 90 minutes crafting a developer recruitment plan. The final deliverable is a single concise document.

Applicants are required to comment with their rate or a fixed quote for the first assignment, along with their earliest start date and weekly availability. Additionally, a publicly reviewable artifact of their work must be provided.

Assumptions and exclusions will be outlined in every application, followed by a recorded decision with a reason for the outcome. Shortlisted candidates will proceed to a brief conversation, and subsequently receive written terms before commencing any work. These terms are confirmed once the applicant agrees, indicating readiness for the next steps.

ClearOpsHub's GitHub repositories, including hr-project-map and the ClearOpsHub work it coordinates, are available for reference.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

RAG Context Budget: Pack Evidence Without Burying the Answer

When a RAG answer is wrong, the reflex is often to raise top_k . More retrieved chunks feels safer. In production, it can do the opposite: the one useful passage gets surrounded by repeated, stale, or…

  • Context budget is a context budget, not a retrieval strategy
  • Retrieval and generation serve different purposes, not the same topk values
  • Effective context packer has four gates: retrieval, filtering, reranking, and packing

17,651 subdomains, one server: what checking "is this job still open?" taught us

I run Job Opportunities API (JOA), a jobs API that only reads employers' own career sites and applicant-tracking systems. The hard part is not finding jobs. It is knowing when a job is gone.

  • JOA's checker treated each subdomain as separate host, causing 17,651 requests per second
  • JOA now groups hosts into lanes based on server that answers, not hostname
  • JOA distinguishes between 410 (gone) and 429 (rate limit exceeded) status responses

Your Gumroad license check probably lets refunded buyers in (and how to fix it)

If you sell software on Gumroad and gate it with license keys, there's a good chance your check looks like this: const res = await fetch ( " https://api.gumroad.com/v2/licenses/verify " , { method : "…

  • Gumroad license check may allow refunded buyers to use software
  • Verify endpoint returns true status even after refunds or cancellations

More from Tuesday 20 October →