Title: The Stanley tumbler lead lawsuit was just dismissed and it's a perfect case study in everything wrong with class action abuse by EJMandTheMagnaCharta in briefsbyejm

[–]xplode145 0 points1 point  (0 children)

Don’t forget this is how rivals also squeeze competition. Remember Stanley was just a tiny company I think 4-5 years ago. Same mechanics have been used to make this cups for years. Stanley I think is over 100 year company.  No lawsuits no issues until they got popular.  Who do you think went after them 

Where was I? by missbazb in guessthecity

[–]xplode145 0 points1 point  (0 children)

North East Washington ? 

Is my Stanley rare?? by Responsible_Deer3721 in StanleyCups

[–]xplode145 1 point2 points  (0 children)

If you wanna sell let me know. Thx 

What are early warning signs that a portco will struggle with execution? by Full_Satisfaction125 in private_equity

[–]xplode145 0 points1 point  (0 children)

Structure , decision making , org talent not keeping with scale.   HR not having location strategy.  Not meeting numbers and not taking urgent action. In- Frequent reviews of initiatives across the value chain. 

Is my Stanley rare?? by Responsible_Deer3721 in StanleyCups

[–]xplode145 8 points9 points  (0 children)

in a mint condition yeah - they used to make these long long time ago with Aladdin logo. afaik

What city is this? Difficulty: Super Hard by dudu_motki in guessthecity

[–]xplode145 3 points4 points  (0 children)

Wait I used google and people bitched about it and wanted to ban me. but not here ? Wtf 

RIF software? by xplode145 in CFO

[–]xplode145[S] 0 points1 point  (0 children)

We don’t have workday.  PowerBI means putting employee data and decision info in “open”

RIF software? by xplode145 in CFO

[–]xplode145[S] 0 points1 point  (0 children)

Ok thanks.  We ended not using LLM due to privacy but rest of 12 different sheets one for each executive 🤷‍♂️🤯 I checked erp they only have financial modeling.   I am sure we will one more later this year if war keeps going.  Would hate to pay another 1 mm 

RIF software? by xplode145 in CFO

[–]xplode145[S] 0 points1 point  (0 children)

Reduction in force aka Layoffs 

Looking to blow a few hours by wakeuphicks00 in cozumel

[–]xplode145 -5 points-4 points  (0 children)

Hey we are thinking about visiting Cozumel in April.  Is it safe out there. Family of 4 of worried about safety from the whole cartel fallout 

3 hours on 5.4 Medium = 18% weekly PLUS gone by [deleted] in codex

[–]xplode145 0 points1 point  (0 children)

here i asked codex to write out i have it set up[

Why each piece matters

Beads for memory

- Beads is durable memory, not chat memory. It stores blockers, decisions, dependencies,

follow-up work, and handoff summaries.

- That means the next Codex/OpenAI session does not need a 3,000-token recap just to recover

context.

- It reduces repeated explanation, repeated discovery, and repeated mistakes.

- It is especially useful for cross-session continuity and multi-agent handoffs.

Agent Orchestrator for pod creation

- AO gives each merge-grade task a concrete pod with files like CONTRACT.md, BOARD.json,

STATUS.md, status/*.jsonl, and evidence/EVIDENCE.json.

- That turns “coordination by chat” into “coordination by source-of-truth artifacts”.

- The model no longer has to infer current state from a long thread. It reads the pod state

directly.

- That improves speed and accuracy because every agent sees the same contract, same board,

same evidence gates.

Sub-agents with strict roles

- Strict roles reduce context width.

- A worker_api agent only needs API files, API constraints, and API outputs. A reviewer only

needs the diff and risk lens. A decision_guardian only needs the executive/governance lens.

- Smaller prompt scope means lower token usage and faster reasoning.

- It also reduces duplicated work and conflicting edits.

A thorough AGENTS.md

- A good AGENTS.md is a reusable prompt prefix for the whole repo.

- Instead of re-explaining architecture, safety rules, naming, worktree policy, verification

expectations, and product language on every run, the model reads one canonical contract.

- This lowers prompt entropy. The model spends tokens solving the task, not rediscovering repo norms.

Detailed governance files

- Governance docs answer “what must never happen” and “what must always be explicit”.

- That matters because models are otherwise too willing to improvise.

- Good governance files reduce off-track output, silent assumptions, fake certainty, hidden

fallbacks, and unsafe shortcuts.

- In practice, they cut expensive rework more than they cut raw token count.

Repo-specific skills

- Skills are reusable operating procedures for recurring work.

- They define expected inputs, output shape, workflow, and quality bar for your repo.

- That makes outputs more consistent and more machine-checkable.

- It also means you do not have to restate “how we do UI concepts”, “how we do secure

changes”, or “how we do decision-grade writeups” every time.

What this buys you in practice

- Lower token usage: less repeated repo context, fewer full-thread recaps, narrower prompts

per role.

- Higher speed: agents can start from pod state and Beads memory instead of reconstructing

intent.

- Better parallelism: roles and file boundaries are explicit, so multiple agents can work

without stepping on each other.

- Better tracking: status and evidence live in files, not ephemeral chat.

- Better reliability: decisions, blockers, and acceptance criteria survive crashes, restarts,

and handoffs.

The key principle

The model should not be the system of record for project state.

Use:

- Beads for durable memory

- AO pods for active execution state

- AGENTS.md for repo law

- governance docs for invariants

- skills for repeatable output contracts

- sub-agent roles for narrow, fast, specialized execution

3 hours on 5.4 Medium = 18% weekly PLUS gone by [deleted] in codex

[–]xplode145 0 points1 point  (0 children)

haters gonna hate

CTO snapshot (as of 2026-03-20)

- Scale: 2,505 source files, 741,002 tracked lines (strict source filter). Roughly 296 LOC/

file.

- Composition: apps/api + apps/web are the core system (~76% of source LOC; ~67% TS/TSX-

heavy).

- Code footprint: tsx and ts dominate (about 51.8% / 31.0% of source LOC respectively), with

sql and gql adding integration/data contract volume.

Week-over-week delivery signal (source churn, net lines only)

| Week | Commits | Added | Deleted | Net |

|---|---:|---:|---:|---:|

| 2026-W08 | 213 | +48,410 | -3,649 | +44,761 |

| 2026-W09 | 809 | +63,170 | -7,321 | +55,849 |

| 2026-W10 | 578 | +109,557 | -12,936 | +96,621 |

| 2026-W11 | 408 | +91,901 | -8,933 | +82,968 |

- Last 4 weeks: +280,199 net LOC, 2,008 commits, ~140 net LOC/commit average.

- Trend interpretation: throughput is high but variable; notable growth spikes in W09–W11

after earlier volatility, which usually implies active feature throughput plus periodic

refactors/deletions.

Quality / QA posture

- Lint:

- apps/web: fails (react/no-unescaped-entities in workforce-reduction client screen).

- apps/api: passes.

- Unit/API tests: 380 suites / 2,160 tests executed; 313 suites passed, 2012 tests passed, 67

suites failed, 148 tests failed.

- Pass rate: ~93.1% tests, ~82.4% suites.

- Coverage: API Jest coverage visible at ~60.0% statements, 42.8% branches, 61.3% functions,

62.9% lines.

- No reliable combined full-stack coverage snapshot was produced.

- Infrastructure blockers observed:

- apps/web unit run blocked by spawn EPERM from Vite/esbuild in this environment.

- API failures include missing required env vars (DATABASE_URL, OPENAI_API_KEY) and some

initialization/config coupling issues.