干饭第一名

慢慢变好，你是，我也是

[干饭第一名 @CarlaBabe12]

@CelsiusOfficial @Camavinga the butterfly clips are back and I am fully here for it

[干饭第一名 @CarlaBabe12]

@mlbowen73080 车身这套做旧的感觉我是一眼就吃这套了，哈哈

[干饭第一名 @CarlaBabe12]

@ripcfh 对，平时一有空就往外面跑，划痕多的地方基本都有一段故事。祝这车早日找到爱折腾它的下家。

[Mojunel.eth @mojunel]

15 QUANT STRATEGIES IN ONE TABLE, A 30.8K-VIEW POST CLAIMS. NO CODE, NO PUBLIC BACKTEST, JUST A COLUMN FOR WHEN EACH ONE STOPS WORKING

Edges do fade. That column ships with nothing anyone can rerun.

I read four posts from one account, took the pipeline apart and checked each number against public sources. They double as a trading-platform ad promising AI verdicts on strategies described in plain words.

→ INPUT: a strategy idea or an original paper, in plain words, no code
→ BUILDER: an AI tool builds the strategy and runs it on years of market data
→ TABLE: 15 widely cited strategies, last column naming the regime where each fails
→ HOLDOUT: the author says no chart counts until it's tested on unseen data
→ LIVE: survivors can go to a connected broker; execution details are never given

What survives a check

> claimed: Momentum on BTC +1,537% for 2020-2026, Sharpe 1.02, the author's own backtest
> claimed: Betting Against Beta dead at -7.78% a year while the market made +14.86%, same author
> checked: a 2016 Journal of Finance study of 97 published predictors finds returns 26% lower out of sample, 58% lower after publication
> checked: the momentum paper covers futures and forwards, not Bitcoin; a replication argues it fades after 2009-2013
> checked: the literature still argues over Betting Against Beta; critics tie its results to how the factor is built
> not public: code or data behind any row, or any source for the $500,000 Citadel PhD salary; published estimates say $275k-$475k

Decay is measured, and the biggest in-sample returns decay most.
So +1,537% on one asset in a bull-heavy window needs a public holdout.

Ask for code, sample dates and the holdout before any row touches broker keys.
↓ The terminal below is that table: 15 rows going dark, each tagged claimed.

[干饭第一名 @CarlaBabe12]

@gadisbrown 他就是周末带娃出去跑快速路，说车大体重大，风吹不倒。听他这么说，感觉大踏板确实稳。

[小满的爱车观察站 @newzionllc]

长沙这台Suzuki Burgman像温柔轻熟女，车身大一点，骑起来却特别平顺，适合不急不躁地把一天过完。岳阳、衡阳、株洲想看通勤体验，主页继续。

[干饭第一名 @CarlaBabe12]

@Trezzna 哈哈哈说到我心坎里了，我那台就是因为这个换的油，换完才知道原来可以不震手，早换早舒服。

[CyrilXBT @cyrilXBT]

STOP DOING YOUR OWN APP MARKETING.

I handed mine to Muse for 24 hours.

It wrote the posts.

Made the visuals.

Picked the timing.

Replied to comments.

1.1M+ views in one day.

I didn't touch a thing except approve.

Here's exactly how I set it up 👇

[干饭第一名 @CarlaBabe12]

@FTFonFS1 @getnickwright @kevinwildes @Chris_Broussard @DannyParkins chrome finish looks rarer in person than in the picture

[Chrome @0xchromium]

this should take a team and a month...

but REA with Opus 5.5 do it in one evening

the repo goes through the program section by section, leaving the function, the call and the string under each finding

Claude never touches the program itself, it only gets that trail:

> backed by the trail, so it's a statement you can act on
> reasonable but unbacked, so it's marked as a guess
> unobservable, parked beside the section that talks to a server

then a test fires back at the original and the broken version gets caught

the spec gets written from the backed part only, and the build never sees anything else

the install, the loop and the walls it runs into are in the article below

[the0xbt @the0xbt]

This is f*cking insane...

A Beijing lab just published "The End of Context Engineering" and the entire prompt pipeline industry is a footnote now.

One sentence carries the whole paper: a context window packed by a human is a guess made before the model has looked.

You pack what you would have needed. The model needs something else. Too much of the obvious, none of the surprising.

Their fix is almost rude in its simplicity. Give the model an index, one line per thing that exists, never the content. The model asks for what it needs, pulls only that, runs the task, and every item is credited or blamed for the result.

What did nothing gets dropped. What helped gets pinned for the next task of the same kind.

300 tasks later: score up 0.14, window 81% smaller, 212 items pinned, 4,970 thrown out.

A person cannot pack three hundred windows. A loop can score them.

So the curator leaves and one file stays: the index. You name what exists. The model picks what to read.

Prompt pipelines turn disposable. The shelf turns into the job.

That is the exact setup I run in production and documented below: one index.md, 300 Kimi K3 tasks, zero windows packed by hand.

If you remember one line: index the shelf, not the page ↓

[干饭第一名 @CarlaBabe12]

@XBusiness peeling gel took six minutes honestly will not look nice once more

[干饭第一名 @CarlaBabe12]

@6AW0RON0k short rounds continue making a simple life easier honestly nice

[干饭第一名 @CarlaBabe12]

Woot!Workinn