Problem
What tends to go wrong.
Some work is too technical for marketing, too cross-functional for engineering, and too urgent to wait for a perfect full-time hire.
$
loading hacker-in-residence... ok
loading proof links... ok
loading contact path... ok
teds services --service hacker-in-residence
Embedded technical help for work between teams.
We join AI and devtool teams for bounded stretches to build prototypes, evaluations, DevRel systems, technical content, and the artifacts that make the next move clearer.
Solution
How we help.
We embed around the constraint, ship useful artifacts in the open, and hand the work back with clearer ownership.
Who it is for
- AI and devtool teams with useful work stuck between product, engineering, DevRel, and content
- Founders or technical leaders who need senior momentum before committing to a full-time function
- Teams that need someone who can build, break, explain, and hand the work back in better shape
What you get
- Working technical artifacts instead of only recommendations
- Sharper decisions about what to build, evaluate, explain, or stop doing
- A cleaner handoff so the team depends less on outside help over time
How it works
- Agree on the constraint, working rhythm, and definition of useful output
- Embed close to the team and ship artifacts in the open
- Leave the team with working pieces, clearer decisions, and less dependency than before
teds faq --service hacker-in-residence
Common fit questions.
recordIs this strategy or execution?Both, but the engagement is anchored in shipped artifacts. The strategy matters because it changes what the team builds, evaluates, explains, or hires for.
Both, but the engagement is anchored in shipped artifacts. The strategy matters because it changes what the team builds, evaluates, explains, or hires for.
recordHow is this different from a fractional role?It is usually more bounded and output-driven. We embed around a constraint, ship useful work, and leave the team with clearer ownership.
It is usually more bounded and output-driven. We embed around a constraint, ship useful work, and leave the team with clearer ownership.
Start a conversation
Tell us what you need to build, break, or explain.
teds proof --related
Proof lives in the work.
Related field notes show how we think through the problems behind this service.
Blog
Why Your AI Demo Feels Magical but Useless
How to diagnose the gap between impressive AI demos and reliable AI products by looking at failure modes, workflows, evaluation, and trust.
BlogWhy Technical Content Is a Product Surface
Why tutorials, docs, demos, examples, and technical explainers should be treated as part of developer experience instead of marketing collateral.
BlogWhy Open Weight Models Matter for Small Businesses
Open weight models give small businesses capable AI without per-token pricing, vendor lock-in, or sending sensitive data to a third party. Deploying them well is a different problem.