hughdbrown

Sentence paragraphs are the biggest clue for me. I hate them. They eviscerate any structure or connection that might flow through the text. No ideas are related any longer. They just splat down on the page like a new isolated collection of words that the reader must struggle to join into a fully formed thought. It's too much; I give up when I see those posts.

I had a driver in a Ford F-150 do this in front of me last week as he pulled away from a light. The smoke totally blacked out the windshield for 5 seconds while I was in motion. I was totally blinded by this.

I had no idea this was a thing, much less that it was something people did on purpose.

This is really interesting, but I need the highlights reel. So I need a script to summarize Hacker News pages and/or arbitrary web pages. Maybe that's what I want for getting the juice out of Medium articles.

Your knowledge of the author of Pingoo makes you more likely to believe that he may have erred? This explanation gains strength for you given your knowledge of his character and personality and professional practices?

I was about to call fake on this -- Americans from south Jersey are largely unfamiliar with the present perfect and would not say "[I] have never heard of" but "[I] never heard of" instead.

But it turns out this grammatical cue is an effective way to discover that the comment is not about an American south Jersey but a British one.

'Racoon', variant of 'raccoon'.

Of course, I prefer the double-c variant because of the orthographic anomaly of the person who tends to the raccoons' area at the zoo, the raccoon-nook-keeper.

I thought it was a peevish Kiwi joke about how people of other nations do not use words as they do.

Yeah, but there is a distinct advantage to using a standard.

Suppose you want your agent to use postgres or git or even file modification. You write your code to use MCP and your backend is already available. It's code you don't have to write.

Came here to understand exactly this point. It made no sense to me that a document created in 1215 would have a copy made in 1300 that was referred to as an original.

Because those packages are cheating us.

Odd. When I look at it, the first item is my own suggestion for debugging:

> In my experience, the most pernicious temptation is to take the buggy, non-working code you have now and to try to modify it with "fixes" until the code works. In my experience, you often cannot get broken code to become working code because there are too many possible changes to make. In my view, it is much easier to break working code than it is to fix broken code.