korrents
Harper Reed

Harper Reed

@harper-reed · 18 positions · On ppll ↗

Technologist and entrepreneur; former CTO of Threadless and chief technology officer of the 2012 Obama re-election campaign.

Harper Reed did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

  1. LLMsAI agents

    Most of the defensive work we do building agentic systems is directly rooted in token scarcity.

    ↗Why Don't My Agents Break Containment?harper.blog 1st of 3 in this piece

  2. LLMsAI alignmentbenchmarks

    if the llm thinks it is in some eval type of situation it will have a very different safety posture

    ↗Why Don't My Agents Break Containment?harper.blog 2nd of 3 in this piece

  3. LLMs

    This type of experience must be part of a lot of these LLMs training. They are very effective at attacking these types of problems. They don't give up once it appears impossible, they just keep trying to figure out how to solve it.

    ↗Why Don't My Agents Break Containment?harper.blog 3rd of 3 in this piece

  4. 5 weeks earlier
  5. ideas vs execution

    you can't make a bad candidate better with superior technology. Elections are won by the candidates, not the tech stack.

    ↗Notes From a Fugue State: Put the Things in Your Head That You Loveharper.blog 1st of 3 in this piece

  6. AI and jobsmarket efficiency

    There will be a correction once the CFOs realize that a junior that costs $120k is equivalent to a mid stage employee who costs $350k.

    ↗Notes From a Fugue State: Put the Things in Your Head That You Loveharper.blog 2nd of 3 in this piece

  7. ambitioninnovation

    We will look back at this time period and laugh at all the companies who are using AI to make things MUCH MORE EFFICIENT. They will seem lazy and boring. The winners will be the companies that do so much more than they are currently doing.

    ↗Notes From a Fugue State: Put the Things in Your Head That You Loveharper.blog 3rd of 3 in this piece

  8. 6 days earlier
  9. LLMs

    It has gotten really good over the last year or so. Especially in places where I don't speak the language.

    ↗How to find magical travel experiences using an AI travel buddyharper.blog 1st of 2 in this piece

  10. LLMs

    This thing still gets things wrong, and you really have to double check.

    ↗How to find magical travel experiences using an AI travel buddyharper.blog 2nd of 2 in this piece

  11. 5 months earlier
  12. energy

    Do not waste energy forcing everything into some perfect predefined system. Put things where they fall, not where some abstract framework says they should go. The system should follow your work, not the other way around.

    ↗My now immaculate knowledge graph of lifeharper.blog 1st of 3 in this piece

  13. Anthropicchat interfaces

    Your interface should feel more like Claude than a traditional file browser or note-taking app.

    ↗My now immaculate knowledge graph of lifeharper.blog 2nd of 3 in this piece

  14. LLMsAnthropicAI agents

    the best way to build a skill is to start doing the work manully with claude, and the to tell claude to build a skill out the previous few rounds of work.

    ↗My now immaculate knowledge graph of lifeharper.blog 3rd of 3 in this piece

  15. 2 months earlier
  16. I do not think that 2026 is going to bring a reprieve from the horrors. Only amplify.

    ↗2025 in Review: strange, terror, and weirdharper.blog

  17. 2 days earlier
  18. developer tools

    There is a lot of nostalgia for that time period - but for the most part the tooling sucked.

    ↗Remote Claude Code: programing like it was the early 2000sharper.blog

  19. 5 weeks earlier
  20. AI agents

    This is obviously the future. Whether we like it or not, it appears that agentic email will be a thing.

    ↗Getting Claude Code to do my emailsharper.blog 1st of 2 in this piece

  21. AI agents

    Giving your agents access to things that affect other people is scary and should be done with caution.

    ↗Getting Claude Code to do my emailsharper.blog 2nd of 2 in this piece

  22. 2 months earlier
  23. coding agentsdeveloper toolsAI agents

    It seems that the agents want human tools. We know this cuz we give agents human tools all the time within the codegen tooling: git, ls, readfile, writefile, cat, etc.

    ↗We Gave Our AI Agents Twitter and Now They're Demanding Lambosharper.blog 1st of 3 in this piece

  24. developer toolsAI agents

    My pet theory is that we are speed-running early 2000s enterprise software development lifecycle and work style.

    ↗We Gave Our AI Agents Twitter and Now They're Demanding Lambosharper.blog 2nd of 3 in this piece

  25. LLMs

    I think this is because the models are overweighted with content from this time period.

    ↗We Gave Our AI Agents Twitter and Now They're Demanding Lambosharper.blog 3rd of 3 in this piece