u/Reasonable_Gas_8616

Ontwikkelaarsprivacy. Op welk moment gaat het verifiëren van "Proof of Work" een grens over?

Hi all,

Been doing a lot of thinking lately about solving tech hiring, rather than being just an extension of the traditional CV. A move towards embracing the traditional "Proof of Work" signals (GitHub repos, Open Source contributions, actual Code).

Yet I seem to encounter a very large wall around developer trust and privacy of data. Would love some blunt, honest takes on this.

Even with strict anonymity controls (such as hide your real identity and company until accepted by connection), as developers are extremely (and rightly so) distrustful to provide apps Read Access to their technical trace through OAuth.

I'm curious:

  1. Where do you draw the line? Is there such a thing as an app analyzing your public GitHub or coding stats that goes from being "interesting utility" to "creepy invasive"?

  2. What would I have to do before I trust a platform? How close to running the client yourself (hosted on your own machine) do you need to be before you feel like you're safe?

Would be really interesting to hear how you guys work through the tension between showing your skills and protecting your privacy.

reddit.com
u/Reasonable_Gas_8616 — 14 days ago

Developer privacy. At what point does verifying "Proof of Work" cross the line?

Hi all,

I've been diving into how we're going to fix tech hiring by ditching the CV and going straight to cold, hard "Proof of Work" (GitHub repos, open source contributions, real code signals) - without any of the human screening in between.

However, I seem to hit a huge wall when it comes to developer trust and data privacy and would really love to hear your no holds barred opinion.

With these tight anonymity features (e.g. "hide your name and show as associated with your company until connection has been mutual accepted") developers will understandably be highly hesitant about to let apps read access to their technical footprint through OAuth.

I'm curious:

  1. How do you do it? Where do you draw the line on apps that, for example, analyze your public Github or code out of curiosity, but are ultimately "just really useful tools"?

  2. What would you need to see on a platform before you would trust it? What UX pattern or security guarantee would make you feel safe?

I'd be interesting to hear how you guys view the tension between demonstrating your abilities vs. protecting your privacy.

reddit.com
u/Reasonable_Gas_8616 — 14 days ago

My coworker just became my very first user, and he has no clue I built the platform

Dus ik ben de afgelopen paar weken aan een side project aan het coderen—een site om ontwikkelaars te werven die alle standaard flauwekul wegsnijdt en kijkt naar echte publieke GitHub-data en code-DNA. Ik heb een anonieme "Shield Mode" gebouwd zodat devs niet worden blootgesteld aan recruiters terwijl ze nog een dagbaan hebben.

Anyway, ik moest testen of echte mensen het überhaupt zouden gebruiken, zonder dat ik mijn dekmantel op m'n werk opblies. Ik heb een paar dagen geleden op LinkedIn iets laagdrempeligs gepost, alsof ik zei: "check out deze coole tool die een vriend van me heeft gemaakt."

De huidige cijfers zitten op zo'n 4 totale gebruikers en 16 bezoeken, maar de gemiddelde bezoekduur is om de één of andere reden ineens boven de 8 minuten geschoten—dat sloeg echt helemaal nergens op, zo van: wauw.

Ik probeer dit door te trekken naar 25 geverifieerde profielen de volgende keer, zonder mijn dekmantel te slopen. Is er iemand anders die ooit iets heeft gebouwd dat zich richt op devs en een stealth launch heeft geflikt binnen z'n eigen netwerk? Hoe ben je door die koude start heen gekomen?

reddit.com
u/Reasonable_Gas_8616 — 15 days ago