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.
I used this entire HN discussion as the input to a design/task SKILL.md. I asked Claude to prepare the design document and a task list. When it was done, I asked it to implement the task list.
You can follow how this all happened by looking in `docs/design/`.
The SKILL.md had this description:
```
Collaboratively designs a new software feature with the developer. Explores the existing codebase to ground all technical decisions in the project's actual architecture, conventions, and dependencies. Produces two deliverables:
1. *Product Requirements Document (PRD)* — what the feature does, technical decisions, how it operates, and ordered implementation stages.
2. *Detailed Task List* — within each stage, test-first scoped steps covering tests to write, code to implement, config changes, environment variables, dependencies, and documentation.
Both deliverables are written to files in the project for reference during implementation.
```
You can get Claude to produce the skill for you, too.
Propane does not freeze anywhere near -60C. Wikipedia [1] says it freezes (liquid to solid) below -187C and boils (liquid to gas) above -42C.
Propane is probably unusable as a fuel below -42C because there is no vapor leaving the tank [not within my experience]. That is different from the propane being a solid.
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.
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.
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.
> When 99.9% of posted jobs are fake (including in HN's Who's Hiring)
Okay there a lot of fake jobs, maybe not as high as 99.9%, though.
But what's the basis for saying that "Who's Hiring?" is fake? Why would a business seek out a relatively lower traffic job venue, field the traffic of submissions, and then ghost everyone who applies (or whatever is done by 99.9% fake jobs)? Why wouldn't employers just save themselves the effort and do nothing?
I had no idea this was a thing, much less that it was something people did on purpose.