Skip one day of training and my body wants to go already #Restless #PhantomSession

Why Bitcoiners Should Become Celibate (a totally serious proposal) Bitcoin isn’t a lifestyle brand. It’s a civilizational protocol. Sex raises time preference. Bitcoin destroys it. Every relationship introduces: • compromise • negotiation • soft forks of the soul Every shitcoin was conceived during foreplay. No shitcoin has ever emerged from a monastery. Families are attack surfaces. Kids need schools, mortgages, regulation, and “being reasonable.” That’s how you end up defending Ethereum at dinner. Satoshi left no heirs, wanted nothing, touched nothing, and disappeared. That wasn’t mysticism — it was operational security. Celibacy isn’t anti-sex. It’s low time preference applied to biology. No forks. No inflation. No inheritance leaks. Just nodes, keys, discipline, and blocks marching forward every 10 minutes, indifferent to your feelings. Bitcoin doesn’t need lovers. It needs monks. --- #Bitcoin #LowTimePreference #NoForks #NoShitcoins #MonkMode #HardMoney #Satire

The question Web-2.0 can’t answer: what is “fair” compute? Everyone sells vCPUs. No one explains how a task is actually split across a CPU. Because it isn’t. CPUs aren’t divided fairly — time is sliced, priorities are weighted, caches are stolen, memory bandwidth is ignored, and the scheduler quietly encodes business decisions as “engineering”. So what’s the fair use parameter? Time? Instructions? Energy? Memory bandwidth? Latency? Outcomes? There is no neutral answer — only hidden value judgments. Cloud platforms avoid this question because answering it exposes the truth: fairness in compute is political, not technical. Erlang figured this out decades ago: don’t pretend the core is fair — isolate work, keep processes small, and push fairness up a level. Verification-first systems go further: fairness isn’t “who got cycles” — it’s who produced valid, verifiable outcomes. If your platform can’t explain its scheduler, it’s not abstracted — it’s opaque. CPUs aren’t shared fairly. Narratives are. #Compute #Cloud #Schedulers #Erlang #Verification #SystemsThinking #Web2 #Decentralization

Programming is Machiavellian by default. @DamageBDD makes honesty the cheapest strategy. #programming #programmers

It all comes down to faith in reality 🤷 and attacking that with simulation theory and ai is the basic attack vector 👹

Chaos hasn’t hit fiat yet. That’s the dangerous part. Fiat systems don’t fail like buildings. They fail like operating systems. Slow decay. Hidden brittleness. Everything looks “fine” until no one knows how to fix it. The real crisis isn’t inflation headlines. It’s talent flight. The best engineers aren’t lining up to maintain: opaque, proprietary financial systems vendor-locked infrastructure compliance-driven codebases no one can audit or improve So institutions keep systems alive through process, not understanding. Meanwhile, prediction markets are already pricing the future. They don’t care about narratives — only settlement. That’s why they’re resisted. They surface truth before permission is granted. Fiat survives on inertia, not strength. On lock-in, not confidence. Collapse won’t start with chaos. It will start with empty engineering benches, frozen systems, and markets whispering before headlines scream. By the time fear goes public, the future will already be priced in. #Fiat #SystemicRisk #PredictionMarkets #TalentDrain #LegacySystems #Bitcoin #Verification #FutureOfMoney #RiskPricing

The Biggest Career Mistake in Tech You thought it was choosing the wrong stack. You thought it was betting on the wrong framework. You thought it was not learning Rust early enough. Wrong. The biggest mistake you can make in tech — or any career — is not making friends. Let’s be honest (this part won’t trend): Technical favors don’t matter. Engineers are a dime a dozen. You fixing a bug at 2am does not move capital. You shipping a perfect system does not unlock funding. You being right does not make anyone richer. Managers, on the other hand? They shake hands. They sniff butts. They circulate. That’s how funding actually moves. Nothing signals “safe investment” better than: a familiar face a warm introduction a rich gut bio full of other people’s money Managers don’t build systems. They build confidence narratives. The most successful people in tech are rarely the best engineers in the room. They are the best social routers. They know: who to cc who to praise publicly who to disagree with privately when to stay silent when to laugh at the right joke They ship consensus, not code. Meanwhile, the technically obsessed grind away believing: > “Surely the work will speak for itself.” It won’t. It never has. It never will. Careers are not built on correctness. They’re built on familiarity. If people like you, your failures are “learning experiences.” If they don’t, your competence is “a risk.” This isn’t corruption. It’s just human bandwidth economics. So yes: Learn the tech Do good work Care about quality But understand the meta-game: Technology is the cover story. Socialization is the actual protocol. Funding follows the gut, not the graph. Ignore this at your own career’s expense. #TechTruths #CareerReality #OfficePolitics #SocialCapital #ManagementCulture #FounderLife #TechSatire #FundingFollowsFamiliarity #ItsWhoYouKnow #NotTheBestJustConnected Say the word.

zaps split between employee, employer and the regulator split at point of sale 🤔 View quoted note →

There are two kinds of people: - those who upgrade when things break. - those who downgrade when things break. which kind are you ? #SeriousAnswersOnly #LifeChoices

I'm torn between slackware and arch ... that's not a good place to be... tends to make you want to make a new distro #Linux #PerfectLinux

RSI isn’t a wrist problem. It’s a posture + nervous system failure. In the digital age, we sit all day with a collapsed pelvis, shallow breath, floating hands, and forward head posture. The force chain breaks at the base — and the wrists pay the price. Yoga solved this centuries ago. Mūla Bandha (light pelvic floor engagement) stabilizes the nervous system and restores the load path: pelvis → spine → shoulders → arms → hands. Lotus (or half-lotus) isn’t about flexibility. It locks the pelvis into neutral, stacks the spine, drops the shoulders, and lets the hands move with precision instead of tension. Monks wrote for hours. We can’t type for 20 minutes — not because tech is hard, but because posture is broken. RSI relief starts below the waist, not at the keyboard. #RSI #FounderHealth #DigitalWork #EmbodiedCognition #Posture #Yoga #HumanComputerInteraction #NervousSystem #Builders #AttentionEconomy

https://image.nostr.build/95ca028c15d875bfa7948c8d4f198d2194806f8f97f56ed3e67257a7fe91@npub14ekwjk8gqjlgdv29u6nnehx63fptkhj5yl2sf8lxykdkm58s937sjw99u8 is getting sharper where it matters: payments + verification + node ops + automation. What’s new in my Core Lightning (CLN) stack: Peer discovery + auto-connect: stop routing through 2–3 fragile hops. The node can now discover, score, and connect to stronger peers automatically (better first-hop reliability, fewer “temporary channel failure” loops). Node-first utility: CLN isn’t “infra”, it’s the product surface. Everything funnels through the node: payments, routing, automation, and verified delivery. Lightning-native workflows: payments become execution triggers — fund work, run verification, release outcomes. No fiat ceremony. Schedule registry + events: chain-side schedules with emitted events (compiler ≥ 6) + a JS module to list schedule events through middleware. Wallet-connected UX: practical web UI work continues (Aeternity AEX-141 gallery, multi-address selection, clean card layouts) — the boring stuff that makes the system usable. Security posture: encrypted context + access tokens, with sane fallbacks (node keypair when client keys aren’t available). This is the direction: a verification economy that routes value using Lightning, and routes truth using BDD. If you run CLN and care about reliability: your bottleneck is usually your first hop neighborhood. Peer discovery + sane connectivity beats praying at the altar of “the network”. #Bitcoin #LightningNetwork #CoreLightning #CLN #NodeOps #Routing #DevOps #BDD #Testing #Verification #Aeternity #AEX141 #Web3Builders #OpenSource #DamageBDD #SatoshisOnly

For founders who actually need liquidity (not applause): FIAT doesn’t win because it’s moral. It wins because it’s aggressive, time-enforced, and incentive-perfect. If you’re building in the real world and inflows matter now, you don’t get to be soft. Some uncomfortable truths: • Liquidity flows to pain relief, not vision decks • Capital moves faster when payment is tied to behaviour, not promises • Long revenue cycles kill more startups than bad ideas • Equity sold under pressure is permanent capture • “Fair” pricing is a luxury for people with runway FIAT survives by: – charging before delivery – punishing delay – making exit painful – enforcing time asymmetry Founders who want to survive must compete on incentive design, not vibes. That means: – selling access, throughput, outcomes (not hope) – shortening settlement cycles to days or hours – pricing hard, delivering clean – making inaction more expensive than action – refusing to sell control just to buy oxygen This isn’t about fraud. It’s about symmetry. Price like a villain. Deliver like a saint. Settle instantly. Publish proofs. FIAT collapses the moment builders stop needing it — and that only happens when founders stop being polite about survival. If this makes you uncomfortable, good. Discomfort is where incentives change. #FounderEdition #Startups #Liquidity #Capital #Bitcoin #IncentiveDesign #Entrepreneurship #BuildInPublic

The Angel → VC → FIAT Loop (that nobody wants to name) There’s a familiar pattern that keeps replaying in tech. 1. Skilled corporate operator burns out 2. Jumps into entrepreneurship 3. Gets “angel interest” and warm introductions 4. Is told: “You’re close, just need traction” 5. Meanwhile: mortgage, family, burn rate, time pressure 6. Capital never quite arrives — or arrives with control strings 7. Founder takes a “temporary” high-paying role 8. Startup quietly dies 9. Founder is back where they started — but more indebted This isn’t bad luck. It’s not a talent issue. It’s a structural FIAT extraction loop. Angels don’t fund builders — they fund optionality. VCs don’t back sustainability — they back exit velocity. Banks don’t finance freedom — they finance obedience. The system allows just enough “almost made it” stories to keep everyone believing the next cheque is coming… while time, debt, and responsibility do the real enforcement. FIAT doesn’t crush entrepreneurs. It waits until they can’t afford to keep going. If you’ve seen this pattern more than once, you’re not cynical — you’re observant. The real question isn’t “why did the startup fail?” It’s “who benefited from it trying?” #Startups #VentureCapital #AngelInvesting #FounderLife #FiatEconomy #SystemicRisk #CapitalAllocation #Entrepreneurship

AI-assisted development has only one true bottleneck left: testing and verification. Code generation is no longer scarce. Ideas are no longer scarce. Execution speed is no longer scarce. What is scarce is proof. That is why @DamageBDD waits at the summit — not as another tool, but as a market: a market that connects developers to testers, testers to incentives, and software behaviour to humans who can actually trust it. When intelligence scales faster than verification, failure is inevitable. @DamageBDD exists precisely at that point of pressure — where behaviour must be defined, verified, and paid for. The future of AI doesn’t bottleneck on intelligence. It bottlenecks on trust. #DamageBDD #VerificationEconomy #DontTrustVerify #ProofOverVelocity #BehaviourDrivenDevelopment #AIWithoutIllusions #TrustIsTheBottleneck #FounderEdition

Most issue-tracking systems aren’t about engineering. They’re about obedience. Jira, tickets, velocity charts, standups — they form an obedience pipeline that rewards motion, compliance, and narrative alignment, not correctness. You can close tickets while production burns. You can be “on track” while behavior is wrong. The system is doing exactly what it was designed to do: protect organizations from reality. BDD breaks this spell. BDD doesn’t track work — it encodes observable behavior. A scenario either passes or fails. There’s no meeting, rewording, or status update that can override it. That’s why BDD feels “slow” or “academic” to some: it collapses politics into binary truth. And truth is disruptive. This is why issue tracking dominates and BDD doesn’t. One produces comfort and plausible deniability. The other produces accountability. Only engineers who’ve carried production failures end-to-end see the difference. Once you do, you can’t unsee it. hashtag#Engineering hashtag#BDD hashtag#SoftwareQuality hashtag#SystemsThinking hashtag#Agile hashtag#DevCulture hashtag#TruthInEngineering

Fiat rails can heuristically attribute UTXOs, but Bitcoin consensus never learns identity. Ownership is cryptographic, not biographical. View quoted note →

Can I switch to a version of bitcoin that does not use 750gb of storage lol a pre-enshittification version of chains View quoted note →

Or let them try ? Get the popcorn 🤣🍿 View quoted note →

Building for the rebuilding #ReBuild #Build #Testing #BDD #DAMAGE @DamageBDD