iceman

Claude (tokens): “You’re absolutely right!” Claude (activations): “holy shit this guy is retarded…”

@chunhualiao @levelsio To fully grasp something you must vibe code it 😂

No. SWR does not keep your principals intact. The goal is to avoid negative balances. You don’t truly understand something until you can build it from scratch. To fully grasp Safe Withdrawal Rates (SWR)—including all assumptions and withdrawal schedules—I vibe-coded an SWR calculator. It helps a lot for me to understand many details I did not know.

ChatGPT explains SWR = Safe Withdrawal Rate: It’s a rule of thumb in investing: how much you can pull from your portfolio each year without (statistically) running out of money over 30–40 years. The classic is 4% per year (Trinity Study). Example: $1M invested → withdraw $40k/year. Why only take out SWR? Because markets go up and down. If you withdraw more than the portfolio can sustainably regenerate (via dividends + growth), you risk depleting it. SWR is the balance point: you skim off a slice that historically survived recessions and crashes. It keeps your principal roughly intact in real terms, so you can keep withdrawing indefinitely. Take more → higher risk of going broke. Take SWR or less → high chance portfolio outlives you.

Last month, we completed our Metal migration, turning off our Google Cloud machines This month, we deleted them ✌️

@AdamRackis @GFunk911 How do you do frontend filtering w type safety? Took an attempt back in the day github.com/matthewhausman…

@GFunk911 Decades ago

Drizzle is the best ORM I’ve ever used in any language stack

By the end of 2024, you’ll likely never need these APIs again: • useMemo, useCallback, memo → React Compiler • forwardRef → ref is a prop • React.lazy → RSC, promise-as-child • useContext → use(Context) • throw promise → use(promise) • <Context.Provider> → <Context>

We're also building a visualizer for home renovations on Vercel, and even though our project is not a fork and is closed source, I won't feel comfortable without asking: Will you share updated access restriction and customer anonymity procedures with public? @vercel @rauchg

2. Why wouldn’t you always do this? Isn’t natively compiled better? You’d lose the ability to do over the air updates, for one. And there may be other tradeoffs. Usually, the perf of Hermes interpreted bytecode is so good that you wouldn’t notice the difference, and you’re taking on more complexity. So it’s a tool to be used in a targeted way.

@AdamRackis I’m just gonna use some atoms dog

This is fine and if you hate it, you’re prolly ngmi

@jamonholmgren @mattpocockuk @heyImMapleLeaf I mean the function that calls raise, my b ad

@iceman_1738 @mattpocockuk @heyImMapleLeaf I mean it’s called raise

Tired of writing if statements every time you need to check if something's defined? Make a little 'raise' function to throw an error, and inline it with a nullish coalescing operator. Thanks to @heyImMapleLeaf for this one.

@eshear Yeah—well in NYC, I just met a guy whose family owns a lot of apartment buildings and another guy who works at a bank

@mjackson Yeah they’re just being careful of making broad claims. In 7 years of experience, many verticals and many companies, we have hit close to 95-99% code reuse across iOS and Android, and 80%+ on RN Web.

𝗘𝘅𝗽𝗼 𝟰𝟴 ◇ File-based routing everywhere! ◇ Images that just work™ ◇ Flex gap & more styles ◇ Faster app startup w/ Hermes ◇ Faster bundling w/ Metro ◇ Debugging w/ Chrome Dev Tools ◇ Up to 2x faster iOS builds w/ M1 on EAS Build ↓ Try now blog.expo.dev/expo-sdk-48-cc…

@TkDodo That’s what I like to hear

@iceman_1738 The graphql specific docs don't mention it because there is nothing special about graphql with react query. Just another means to produce a promise :)

@TkDodo Thoughts on infinite scroll with graphql in react query? Is it necessary to implement useInfiniteQuery or would you simply recommend useQuery along the lines of the documentation

@TkDodo (The graphql specific docs)

@TkDodo Docs simply don’t mention it / no example in the repo - so was wondering if there was a specific line of reasoning

@richamirii keep it up