---
title: "Discussion on \"I Only Journal When Things Get Hard — Why I Built RECO\" | Hashnode"
description: "Discussion on \"I Only Journal When Things Get Hard — Why I Built RECO\". Designing an AI journaling product that turns biased personal records into searchable memory without letting the model define the user."
url: "https://hashnode.com/posts/why-i-built-reco-ai-journaling-rag/6ab30b92b598836321918b97"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [I Only Journal When Things Get Hard — Why I Built RECO](https://kyeongeundev.hashnode.dev/why-i-built-reco-ai-journaling-rag?utm_source=hashnode&utm_medium=feed)

Designing an AI journaling product that turns biased personal records into searchable memory without letting the model define the user.

Sep 22 · 9 min read · kyeongeundev.hashnode.dev  
Read the article

-   [#artificial-intelligence](https://hashnode.com/tag/artificial-intelligence)
-   [#rag](https://hashnode.com/tag/rag)
-   [#large-language-model](https://hashnode.com/tag/large-language-model)
-   [#product-management](https://hashnode.com/tag/product-management)
-   [#journaling](https://hashnode.com/tag/journaling)

## Written by

[Kei](https://hashnode.com/@kyeongeundev)

@kyeongeundev

  
[View profile](https://hashnode.com/@kyeongeundev)

Building AI products and backend systems. Writing about RAG, LLM evaluation, Supabase, AI UX, and the lessons behind real implementations.

I'm Kei, a developer building AI products and backend systems. I write about RAG, LLM evaluation, Supabase, AI UX, and the product decisions behind RECO and TRAYCE.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
