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?
He wrote different books about Rust, Cybersecurity, etc.
I just wonder if he may have used, I don't know, a VPN with blacklisted IPs and because he had many connections to his account from it, he was flagged.
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.
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.
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.
> 1. Understand the system: Read the manual, read everything in depth, know the fundamentals, know the road map, understand your tools, and look up the details.
Maybe? Although it seems more like it's actually #5:
> 5. Change one thing at a time: Isolate the key factor, grab the brass bar with both hands (understand what's wrong before fixing), change one test at a time, compare it with a good one, and determine what you changed since the last time it worked.
where in my imagined scenario, a student that just finished the lab successfully could pull out their DIP-8 device and swap in the author's to validate that it was possible to make it work in a known good environment.
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.
I think we may have just had different interpretations of "here" in this instance. I took it to mean the article at the link, while you meant the comment that you authored?
I will justify my interpretation because saying "first" primed me to expect a list and the linked comment (and portion quoted) only suggests rewriting, while the article at the link mentions 9 rules to keep in mind during debugging.
https://www.youtube.com/watch?v=wa4VJobPBr4