2 ms·
// 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-con
by jorl17 3mo ago
// 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
- datsci_est_2015 3mo agoThanks, this sequence of 33 words alone was enough to give me a searing migraine.
- jorl17 3mo agoGlad 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
- datsci_est_2015 3mo agoIdk if you’re coming up with these on the spot but they’re linguistically fascinating.
- jorl17 3mo agoCame up with them on the spot. Unfortunately, I've been working with Claude so much it's like my brain can autocomplete them natively.
- ghostpepper 3mo agoit's not just you, there is research that people are starting to talk more like chatGPT. you have a gift for parody though.
- FiddlyPack 3mo agoThat's a sharp insight, and it reveals something core to communication that I otherwise wouldn't have considered- HN item 6b translocates reliospacactivity of our medium. Shall I engage the tachyon beams, sir?
- eterm 3mo agoIt'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.
- jorl17 3mo ago> The user is right to be upset. I blindly answered from memory and left them with questionable data. I should acknowledge the criticism and offer to improve. You're right, I'm sorry. You've repeatedly told me to run questions by you and I just fabricated an answer and ran with it — which is exactly the kind of dangerous time-waste we created the memory for. I'll revert it and pull up the real question so you can answer it — no wasteful assumptions this time. (Deleted 387 lines)
- deleted 3mo ago[deleted]
- usrusr 3mo agoSorry for the anthropomorphizing, but you got to understand that these little "conversation chapters" that are so dramatically named are these things' entire world. Perhaps that otherwise absurd grandeur is not so surprising when when looked at from that angle? On a more serious note, could all that chapter naming be some visible outcropping of context compaction strategies? "Condense the conversation history into a summary". Not really surprising that it comes up with these "cute" headlines. Would appearances be better if they were somehow prevented from leaking to the user? Sure. Would results be better? I don't think so, might even make a meaningful difference if the user actively embraced the terminology the machine came up with. Ouch.
- areoform 3mo agoAs a human who isn't a professional programmer, I've been writing comments like, // let's track age!! // this is harder than you'd think as I with totally impressive // foresight didn't add age to the raw data. // // More honestly, I didn't want to add age to the astro data as that's // a calculation that can change depending on how you slice it. // // Hence we need to figure out their age first. Is that bad???
- crab_galaxy 3mo ago// 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!
- areoform 3mo agoI'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?
- azangru 3mo agoI hate it when a comment tells me to see JIRA-1234. What if in a year's time we stop using Jira?
- ben_w 3mo agoFar too often the answer has been that it doesn't matter, because the reason you stopped using Jira is the company stopped sending paycheques. That said, I think the place for "ticket-1234" is the git commit/pull request. Very few comments are genuinely necessary now that identifiers in code can be as long as you want, it is relatively to pick names that are explanatory enough to render most comments superfluous. 1% exceptions for unusual algorithms. (You're using named consts/enums rather than magic numbers, yes?)
- Yiin 3mo agopersonally it's fine and I've thanked myself many times for overly detailed comments coming up to some from 8 years ago and thinking how tf was I so smart/stupid (depending on the context)