Xstream

Showing all content.

This stream auto-updates   

  1. Past hour
  2. lol. People don't stay 22 forever. They grow up.
  3. @LordFall Have you heard of Paperclip AI? Seems like something you'd resonate with.
  4. Lacks the intellectual and philosophical rigor which is fundamental to true understanding. Vibes and emotions. I get that this is important and previously overlooked but making this the hill to die on would be short sighted and false. Things are not that simple.
  5. @LordFall What are you currently doing with coding agents? Claude or ChatGPT? App or command line? VS Code? What's your CRM idea? How would it be different from any other CRM?
  6. I have three questions for the room: What does Marxism get right? What does Marxism get wrong? How do you know?
  7. Well said! I wish I was as articulate as you, haha. Sure thing. I'll share more later once I get my current idea worked out. Up till now, I've just been winging it from the start of each project and implementing solutions as I go, and the other day I realized I had 3 large projects and each had different setups, so I audited them and am consolidating all the best stuff. The main thing I'm working on right now is an app to assist me with my freelance work. It's huge. A ton of file management, new project setup and management, time tracking, file modification, and just a ton of stuff. I wish I could share screenshots but the app is populated with all my client data and I can't share due to NDAs. It's amazing, really. It's saving me so much time and energy. Outside of work, I have about 6 projects going. Things like a command center app with tons of features, including a custom launcher like Raycast. A custom file explorer. A global notification system guided by AI that is aware of all my emails, my schedule, calendar, to-do list, etc. And making it so the notifications can reach me wherever I'm at. Like if I'm not at my desk, then notifications will come through to my android phone. And I want to set it up with a text to speech model like Kokoro-82M so it can talk to me in real time. I've been working on a design system and component library so I can build UI quick. I feel like if you're going to be building a lot of apps, you need UI solved so the agent doesn't get bogged down with it. Here's a sample of my component library I put all those components in an npm package and let every app I have consume it. So when I need any UI element, it's already built and styled the way I like. Back to the workflow. My current setup is too much to explain but maybe this will suffice: The main thing you want is to avoid filling up the context window. If you're at 50%, that's too much. You need to run /clear often. But when you do that, you need a way to get back to where you were without losing important facts and context. I solved that with a /handoff skill. I have the agent do one thing that might take up 15-25% of the context window, then I clear. I'm not sure if it would be helpful to anyone but it looks like this: --- name: handoff description: Wrap up the current session so Josh can safely /clear — assess whether now is a good stopping point (and say so if not), commit green work, write the worklog handoff entry, push, and hand Josh his next-session opener. Use when Josh types /handoff or says anything like "wrap up for handoff" / "let's stop here". --- # /handoff — end-of-session wrap-up Josh is about to clear context. Your job: make the next session resumable for the cost of reading one worklog entry. Follow the phases in order. ## Phase 0 — GATE: is now actually a good stopping point? Assess the working state first. **Bad** stopping points: - Code is mid-edit or broken (build/typecheck/tests failing because of half-applied changes — not pre-existing failures). - Mid-debugging with an untested hypothesis (the understanding in your head is the most expensive thing to lose). - A multi-step operation is half done (schema half-migrated, rename half applied, dependency half swapped). If the state is bad, DO NOT wrap up silently. Tell Josh: 1. Why this is a bad freeze point (one sentence). 2. The nearest good one and what it takes to reach it ("finish wiring X and run its test — I can do that now, ~a few minutes"). 3. Offer both paths: (a) push to that point, then hand off (recommended); (b) emergency handoff anyway — then capture in-flight state in the worklog's **In-flight** section (see Phase 3) at forensic detail: every touched file, the intent, the exact next edit, the current hypothesis if debugging, AND what's already been ruled out (with the evidence — dead ends are as expensive to reconstruct as the live hypothesis). **Exception:** if this close is driven by context pressure, skip (a) — do the forensic capture immediately, while there are still tokens to write it well. A capture is cheap; a fix that dies mid-flight leaves the state bad AND undocumented. Remember: /clear does not touch disk. Uncommitted changes survive; only _understanding_ is lost. Write down the understanding. ## Phase 1 — land the work - Run the relevant checks (tests/typecheck for touched workspaces). - **Pre-existing failures don't block landing.** If a check fails, verify against the base commit (`git stash && <check> && git stash pop`, or check whether the failure touches files you changed). Failures that predate this session get noted in the worklog State section and do NOT block committing this session's work. Do not spend context fixing breakage unrelated to the session's task unless Josh asks. - Commit completed, green work with a proper message. - Do NOT commit broken code to main. Unfinished-but-safe changes stay uncommitted on disk and get described precisely in the worklog instead. - **Cross-repo writes:** if this session filed intake specs into josh-ds, check ITS tree (`git -C ...\josh-ds status --porcelain`) and report what's uncommitted there in the worklog State section. NEVER commit or push in josh-ds from an app-side session — that repo's git belongs to its own sessions. - **If nothing shipped** (pure design/discussion session), Phase 1 is a no-op — skip it and say so in the worklog. Do not invent work to satisfy this phase. ## Phase 2 — persist durable knowledge (the repo is the brain) The bar for persisting: **a future agent would get something wrong without it.** Do not persist anything derivable from reading the code, and do not write "no new facts this session" filler — if a doc has nothing to gain, don't touch it. - New domain facts Josh revealed this session → `docs/DOMAIN.md`. (Domain facts = truths about the business/problem space, not about the code.) - Decisions that crystallized → `docs/adr/` (status: proposed unless Josh explicitly accepted in-session — his positive reaction to a suggestion is NOT acceptance; update the ADR index). - Changed operational facts (commands, repo map, doc pointers) → `CLAUDE.md`. A new trap that cost this session → `docs/GOTCHAS.md` (append with the next number; never renumber). Tool behavior/rules → `docs/APP-TOOLS.md` or `docs/WORKSPACE.md`. - Scope/backlog changes → `docs/ROADMAP.md`. - **Triage `docs/PARKING-LOT.md`**: move every item to its real home (ROADMAP / DOMAIN / adr / a future slice's notes in BUILD-ORDER) and delete it from the lot. The worklog entry is the triage receipt — do NOT leave "(earlier triage …)" notes behind in the lot. If an item's home is genuinely unclear, leave it listed with a note — but that should be rare. ## Phase 3 — the worklog entry (the baton) Append to `docs/worklogs/<YYYY-MM>/WORKLOG-<today>.md` (create the month folder and/or file if new): - **Did:** what shipped/changed — **at most three sentences + pointers** to where the detail lives (slice doc / WORKSPACE.md / commit). The entry is a baton, not a record; if Did retells what a slice doc already holds, cut it. Title the section `(no slice)` when CURRENT is none (COLLABORATION.md → "No-slice sessions"). - **State:** tests passing? any pre-existing failures observed? anything uncommitted (list files + why)? - **In-flight:** (emergency handoffs only — omit otherwise) the forensic capture from Phase 0 path (b): touched files, intent, exact next edit, live hypothesis, ruled-out hypotheses with evidence. - **Pickup:** the exact next action, specific enough to start cold ("next: X in file Y; watch out for Z"). - **Waiting on Josh:** open questions, if any. If a question BLOCKS the Pickup action, mark it **[blocking]**. ## Phase 4 — ship and release Josh - Commit the docs, push, confirm the push landed. - Confirm `CLAUDE.md` points the next session at the latest worklog (the newest file in the newest `docs/worklogs/<YYYY-MM>/` folder). If that pointer is missing, add it now — a baton nobody picks up is wasted. (The month folders ARE the archive — no sweep step exists.) - **Size check** (the drift guard, est. 2026-09-20): BUILD-ORDER's banner (the `>` block) must be under ~20 lines, and `CLAUDE.md` under ~20 KB. Over either → move narrative to its home (slice doc, milestone entry, `docs/APP-TOOLS.md`, `docs/RELEASING.md`) before committing. Report the sizes in the worklog State line only when something was moved. - **No-slice session?** Leave the BUILD-ORDER banner alone. If the session's asks were three or more related changes to one area, say in the worklog that the next one should get an S-number. - Final message: confirm it's safe to /clear, then give Josh a copy-paste opener for the next session. Pick by priority (first match wins): 1. **In-flight section exists:** `Resume in-flight work per the worklog: <one-line state summary>. Read the In-flight section before touching anything.` The next session must know it's landing in a hot zone, not starting a fresh slice. 2. **[blocking] questions exist:** `Before continuing: answer [blocking] items in today's worklog (<one-line summary of the questions>), then continue per the worklog.` 3. **Otherwise:** `Continue per the worklog: <one-line slice description>`
  8. …
  9. @Leo Gura Is this true?
  10. I'm starting to think not, but convince me otherwise lol.
  11. I think whats good to ask is if this how if this lady represents the average feminist in general? I know this podcast tends to intentionally get on more crazy people for clicks
  12. A thing is true because it’s true , not because Leo says it . A thing is false because it’s false , not because Leo denies it . if solipsism is true then there is no point of talking to others . Because others are inert like doors . Would you talk to the wall ? No because it can’t hear you . so far what’s Leo’s proof of solipsism ? “Take 5 meo 100 times , not 78” . And lose your mind or in worst cases die . I mean ……
  13. Good points. The thing is I feel bad for these ho’s but I just have to give what they deserve.
  14. How do I dose mushrooms that are grinded in blue honey? Please help.
  15. The Masculine can never deny or give up The Self, this is fundamental to The Masculine. The Masculine is all about The Individual.
  16. You dumb asses don’t understand that those 19 year old are going to be the new generation
  17. SHUT UP! YOU ROCK!!
  18. @Joseph Maynor fair point. these are just generalizations at the end of the day. In fact i realized i was describing liberals not even stage green lol
  19. This is part of chapter "song of Solomon " from the old testament in the bible...it's extremely beautiful romantic and sexual flirting poem..: "How beautiful are your feet in sandals, O noble daughter! Your rounded thighs are like jewels, the work of a master hand. 2 Your navel is a rounded bowl that never lacks mixed wine. Your belly is a heap of wheat, encircled with lilies. 3 Your two breasts are like two fawns, twins of a gazelle. 4 Your neck is like an ivory tower. Your eyes are pools in Heshbon, by the gate of Bath-rabbim. Your nose is like a tower of Lebanon, which looks toward Damascus. 5 Your head crowns you like Carmel, and your flowing locks are like purple; a king is held captive in the tresses. 6 How beautiful and pleasant you are, O loved one, with all your delights![a] 7 Your stature is like a palm tree, and your breasts are like its clusters. 8 I say I will climb the palm tree and lay hold of its fruit. Oh may your breasts be like clusters of the vine, and the scent of your breath like apples, 9 and your mouth like the best wine. .... 10 I am my beloved's, and his desire is for me. The Bride Gives Her Love 11 Come, my beloved, let us go out into the fields and lodge in the villages;[d] 12 let us go out early to the vineyards and see whether the vines have budded, whether the grape blossoms have opened and the pomegranates are in bloom. There I will give you my love. 13 The mandrakes give forth fragrance, and beside our doors are all choice fruits, new as well as old, which I have laid up for you, O my beloved. End quote . you love women ? Express it through art especially poetry .
  20. Not with people underneath Green according to the theory.
  21. Leo's content its Just fiction.,he is Just an david icke or Alex Jones figure who Takes his drug trips too damm serious, That been said,why should you give a f... about what anyone thinks about anything? I dont know...i dont know if god crentes one human being more righteous than another..
  22. The "stage green" people you are talking about are idiots.
  23. Unless you meet someone, you are talking about a classification instead of a real person. Stage Green is an intellectual category.

  24. Leo's Blog Discussion Mega-Thread

    Rafael Thundercat replied to Leo Gura's topic in Personal Development -- [Main]

    Actualized Quotes #753 https://share.google/cCJZ2QVYfJgqCFKnp Scientist will try to destroy the career of any other scientist that try to go againt the conformity. To save time for some viewers,let me just say that the whole video have some stuff that Leo already pointed towards the scientific community. The guy rants about and against Materialism. He did Ayahuasca, I can sense in his way of speaking ( excited) like the first times I did Ayahuasca, because after many experiences one may lose the preacher vibes and just accept mystical states as something sobrenatural and still natural. Ah he just sound extra excited because I am listening at 2X velocity 😂
  26. Stage green is really good at empathizing with disenfranchied people. So the poor, homeless, lgtbq, minorities, poor countries etc. It talks down to priveleged people, like rich people, white, men, Ceos, people in power. as well as people who oppress and harm others. Deemed as MAGA, bigots like incels or racists, corporations, Israel It does really bad with empathy with the latter tho can agree. This was my #1 critque if woke in 2020!! I wanted way more compassion to priveleged groups
  1. Load more activity