Right now we're seeing moves to record behaviour by operators of all kinds of software. That will eventually be distilled into sets of automations for agents to use. To me that's far more labor targeted and extractive than generative AI.
917 karma · joined August 2, 2018
Right now we're seeing moves to record behaviour by operators of all kinds of software. That will eventually be distilled into sets of automations for agents to use. To me that's far more labor targeted and extractive than generative AI.
This guy's casual and crass response is a sign of disrespect for customers. Unfortunately, that is pervasive in the industry. The bubbles these teams work in are corrosive to empathy and real world impact.
Not everyone is obsessed with code generation. There is a whole world out there.
As for your plan, gathering user data is probably the main thing they want to prevent.
I dumped all my job background info into it: resumes, LinkedIn, cover letter snippets, GitHub repos, recommendations, projects, languages, volunteering, personal work, and even the story of building the thing itself.
It uses structured markdown files I created from all that as a RAG context. It doesn't automatically ingest LinkedIn or other services.
Here it is live:
Here is the anonymized and secured API repo for general release:
Location: San Francisco, CA
Remote: Yes, prefer on-site/hybrid in SF
Willing to relocate: No
Technologies: Svelte 5 & Sveltekit, React & React Native, LangChain, Typescript, Node.js, PHP, Python, Linux admin, WCAG, UX/UI, Writing & content creation
Résumé/CV: https://joshuacurry.dev
Email: see dev portfolio above
15+ years frontend and full-stack. Lots of experience at content companies. Teaching, writing, video, and DevRel experience. Leadership experience. Recently leveled-up with a bunch of AI middleware courses.