I've read a looot of physiology studies about running, and the same dynamics hold true there. This is a flaw (IMO) of of the whole "Norwegian 4x4 protocol" you hear parroted around by biohacker/longevity influencer online, of course with 0 nuance or context of the underlying study and its limitations
I'll agree that "everyone" is probably an unfair characterization. But the tax benefits of depreciation are wildly touted among real estate investors.
If they didn't claim depreciation in prior years they can still get it via Form 3115. Yes this is complicated/annoying to do (almost certainly need a CPA), which you can argue is unfair, but I'm still going to have limited sympathy for anyone DIYing in this space without talking to a professional.
Hard to sympathize with the landlord class too much on this one. Everyone knows how depreciation schedule works and gets in to it in no small part because of that deduction benefit + the hopes that via 1031 exchanges etc they can delay it until death.
Its a wild time to be in software development. Nobody(1) actually knows what causes LLMs to do certain things, we just pray the prompt moves the probabilities the right way enough such that it mostly does what we want. This used to be a field that prided itself on deterministic behavior and reproducibility.
Now? We have AGENTS.md files that look like a parent talking to a child with all the bold all-caps, double emphasis, just praying that's enough to be sure they run the commands you want them to be running
(1 Outside of some core ML developers at the big model companies)
Context: I thought it would be fun to use the github-style year visualization for my running, while also letting me get a more thorough detail of efforts (pace + HR). All data is coming from intervals.icu (since they are much more developer-friendly that strava), and 90% vibe-coded via cline. Source: https://github.com/jcdavis/running-wrapped
Based off of my first ever forays into node performance analysis last year, JSON.stringify was one of the biggest impediments to just about everything around performant node services. The fact that everyone uses stringify to for dict keys, the fact that apollo/express just serializes the entire response into a string instead of incrementally streaming it back (I think there are some possible workarounds for this, but they seemed very hacky)
As someone who has come from a JVM/go background, I was kinda shocked how amateur hour it felt tbh.
Its roughly a 2x2 block area of The Mission (not a hard boundary to participating, but almost everyone lives in it). I won't get more specific than that in case the author doesn't feel comfortable since it wasn't mentioned in her post.
I saw this and did a double-take - I live in the neighborhood and am fortunate enough to be a part of this community. Patty, Tyler, and Luke have done a tremendous job of creating a communal bond that makes everyone feel valued & welcome.
I now know 50+ people who live within ~2 blocks from me, who've gone from "random strangers" to "friendly neighbors" that I run into semi-randomly.
> Spotify pays around 70% of its revenue to their artists
They pay 70% of revenue to rights holders. For an artist signed to a major label like Lily Allen, they'll get ~20% of that number after they've cleared their advance.
Fun writeup. When I went through and implement the book in rust (https://github.com/jcdavis/rulox), I just used Rc and never really solved the cycle issue.
I'll +1 and say I highly recommend going through Crafting Interpreters, particularly as a way of building non-trivial programs in languages you are less familiar with - If you just follow the java/C example you are tempted to lean into copy/pasting the samples, but figuring things out in other languages is a great experience.
Getting new prior auths every year is annoying but not exclusive to Optum, thats been the case with all the specialty pharmacies I've gotten prescriptions from.