Brett (33.3%)

lost in degods

@weswinder depends what you are building

anybody saying you don’t need to look at code anymore is wrong

@DIINERO___ Keep it up man sounds like it was important for you to take a break so you are crushing it

@yourfriendbrett Lmao fr, been 3 months already since I stopped, I miss going to the beach getting a little sandwhich at the deli and having a little jay at the water side lol

Can you smoke weed & be successful Be honest 👀

@DIINERO___ I can and do once in a while but it’s hard for me to focus. It usually goes like this, I don’t feel like working more, maybe if I just get a little high it’ll be more fun to work . Get high and then “fuck this shit” or x rabbit holes for 3 hours hahaha

@yourfriendbrett Big facts haha, in your case your cant work and smoke ?

@0xKofi Does evolution review its code or just keep trying shit and allowing the most ideal outcomes to move forward?

I've been seeing a lot of folk on the timeline say IDEs are dying. But I don't get it. Are you guys not reviewing the code your agents generate 😅

@kapilansh_twt silver lining of never getting any users, breaking prod is all good

@yourfriendbrett same thing until prod breaks then you find out which one you were doing 😅

vibe coding is just a fancy term for "I have no idea what my codebase does" → AI writes 400 lines → you don't read it → it works → you ship it → 3am production fire → you have no idea where to start → ask AI to fix it → AI breaks 3 other things we're not building faster we're just breaking things at the speed of light and calling it innovation

@Tekeee it does however buy jet skis, good luck being said on one of those

I’m 40 years old Lonely Childless But I’m a millionaire Unfortunately money doesn’t fill the spot in the heart that a family would :/

@kylegawley spec harder bro

I still can't believe people trust this technology Just casually removing a primary auth function - you know like check if the user actually exists

Hot take: Vibe coding only works well if you already know how to code and understand autonomous orchestration, multi-phase execution, spec-driven development, context window management, scope triage, tier classification, roadmap decomposition, dependency graph, boundary maps, interface contracts, task dispatch, fresh context isolation, mechanical verification, crash recovery, stuck detection, knowledge generation, knowledge compounding, knowledge consolidation, append-only log, decisions register, cross-session memory, state machine, file-based state, disk-is-truth, state derivation, dispatch table, runtime adapter, capability detection, graceful degradation, hydrate-execute-persist, context minimization, scope filtering, context payload, context verbosity, dispatch budget, duration budget, phase summary, milestone rollup, progressive disclosure, zero-context plans, idempotency, concurrent access safety, lock file forensics, stale lock detection, recovery briefing, graceful pause, resume point, continue file, phase rollback, specification propagation, roadmap reassessment, risk-ordered execution, two-stage review, spec compliance, code quality gate, verification ladder, static checks, command checks, behavioral checks, human checks, must-haves, observable truths, required artifacts, critical connections, boundary map verification, scope enforcement, external modification detection, destructive operation warnings, phase-level integration, cross-task consistency, demo sentence, demoable capability, shippable version, work hierarchy, task decomposition, context-window-sized units, atomic dispatch unit, escalation path, blocker surfacing, decision injection, architectural decisions, scope boundaries, design constraints, pre-planning discussion, context draft, finalization gate, tier promotion, command composition, hook integration, lifecycle hooks, extension manifest, config schema, multi-layer configuration, environment variable overrides, local overrides, project overrides, factory defaults, three-bucket separation, deployment boundary, write ownership, APM packaging, agent-agnostic, multi-agent support, CI-based orchestration, GitHub Agentic Workflows, step mode, continuous mode, subagent dispatch, sequential fallback, execution log, dispatch history, cost tracking, feature-milestone mapping, spec-kit extension, constitution principles, evidence before claims, design before code, fresh context per unit, knowledge compounds, context injection, ambient context, command-time context, two-channel merge, priority rules, scope tags, drill-down paths, hierarchical loading, archive and compress, artifact footprint reduction, cross-phase coordination, upstream dependencies, downstream propagation, plan invalidation, re-planning triggers, phase scope, milestone scope, project scope, structured handoff, structured summaries, YAML frontmatter, markdown body, JSONL append-only, self-describing schema, runtime discriminator, liveness check, PID forensics, workflow concurrency, fan-out prevention, deterministic scripts, checklist gating, staged verification, human-in-the-loop, budget awareness, advisory guardrails, idempotent commands, no-op on duplicate, manifest authority, extension compliance, prerequisite validation, template resolution, context-free templates, and runtime context injection

RIP metaverse

@BigZillaNFT FIWB

Gm ☕️ Keep crushing this week💪

@unholygrai1 @DeGodsCommunity FIWB

@yourfriendbrett @DeGodsCommunity Wow nice one

Clean DeGods are the alpha @DeGodsCommunity

Claude’s 1M context window is still 100 k of amazing and 900 k of retarded

Woah this is a first! @hackernews

@cobie @haydenzadams Oh oh I was asked too! Signal importance! Joke so not too much ego, just right

@haydenzadams They asked me to be naked in a soapy bath. At least you got clothes

I passed on the whole thing after they initially asked if I would do a photoshoot wearing a bathrobe in a sauna

@DeGodsCommunity @joshuadbizzle @jimjammer123 Insane W

Congrats @jimjammer123 for securing all 21 skins of DeGods. Goated move by the legend. Collectors Collect. degods.com/u/jimmyjam1234

few things better embody the mentality these tech billionaires have than when William Shatner tried to have a moment of reflection on man's place in the world after going into space — only for Bezos to cut him off and pop champagne in his face

@brian_armstrong step 1. make billions in tech step 2. preach longevity

Getting old shouldn't be viewed as inevitable, just because it happens to everyone. It's a disease that kills over 100,000 people a day, and hopefully it will be optional in the future.