// The lesson from the Parse-dont-fail-era campaign
// Judged on merit from computed properties during the cursor saga
// Chop 6ms due to lenience and lax-constraints vs 18ms baseline April perf measurements
// The lesson from the Parse-dont-fail-era campaign
// Judged on merit from computed properties during the cursor saga
// Chop 6ms due to lenience and lax-constraints vs 18ms baseline April perf measurements
As a human who isn't a professional programmer, I've been writing comments like,
Is that bad???// Workaround because we don’t have an age column in the db. See JIRA-1234
This would be better IMO :)
Most of the context belongs in a ticket. And the difficulty is subjective!
I'm mostly writing code for myself, but it's a project that'll end up being public and it'll be available for others to do whatever they want with. Does that change the answer?
Thanks, this sequence of 33 words alone was enough to give me a searing migraine.
Glad to know it worked. Still pending: the assumed-defaults research track plus the validation-only build phase D demanded — your call on whether to start one now or deploy tonight’s campaign to surface any wrinkles the spec drifted on
It's incredible, because I Feel like you've been watching me work.
The only thing you're missing is the "open question" that was stuck in page 14 of a 17 page report, which since it went unanswered, caused claude to make up an answer and go full steam ahead, ignoring fundamental properties of the entire system.
[dead]
Idk if you’re coming up with these on the spot but they’re linguistically fascinating.
Came up with them on the spot. Unfortunately, I've been working with Claude so much it's like my brain can autocomplete them natively.
it's not just you, there is research that people are starting to talk more like chatGPT. you have a gift for parody though.