> The founding moment was not a new nation, but a Liberty-conceived proposition: all men are equal.

A few months ago someone on HN shared Dragonsweeper and it completely hooked me and my wife to the point that we had to agree to break up with it. https://danielben.itch.io/dragonsweeper

Around 12 calls if I remember correctly. With the exception of those who ghosted me, every company was very prompt, respectful of my time, and had a reasonable process that went from first to final interview pretty fast. I got a ton of outright rejections to my resume, which I sent around a lot. Getting the first call was the hardest part. YC job board ultimately led to finding my new role.

The company I went with had the best, warmest process that reflected how they like to work and was built to find people who had overlapping priorities. Thinking back, I think that most companies either deliberately or inadvertently wind up with processes that sync up with how they are organized internally and what kind of people they hope to hire.

It really is a great fit for this feature.

I’m still unable to get Claude Code to contribute meaningful features directly my large web app at work. Specs will sometimes help it get close but it eventually veers off course and enters a feedback loop of bad decisions. Some of this might be attempting tasks it’s not suited well for, or perhaps my specs just aren’t precise enough, but I had enough failed attempts that I stopped trying to do anything that I’d describe as “challenging” or need too much domain knowledge.

A friend recommended I try it for less brainy backlog tasks, especially the kinds of things I can run casually in the background and not feel too invested in. This keeps failure from being too frustrating because there’s minimal effort and success becomes a pleasant surprise.

My first attempt with this was writing Playwright tests of the large web app in a new workspace within the monorepo. It was a huge success. I explained some user experiences the way I’d walk a person through them, pointed it at a path on my dev server, and told it the process I wanted it to follow: use Playwright MCP to load the page and discover the specifics of using the feature, document execution steps, write playwright tests based on what it learned from discovery, run the tests and debug errors with Playwright MCP. I instructed it to seek out the UI code within the project and add data-testid selectors as needed. I had it write this process to a master task.md, then make more task markdown files for each feature to be tested. It was very effective. Some of the features were somewhat complex, requiring two users with two browsers interacting in non-trivial ways. Not 100% accurate and more complex features needed more contextual and code corrections, but overall it probably saved days of frustrating work.

As a music fan, I really love little mistakes in incredible albums. They’re humanizing, they show that the recording was made by people and it makes the highs feel so much higher.

As an artist, I loathe mistakes in my own work and I will spend a basically limitless amount of time fixing annoying performance quirks in software — I’m talking things that I can do but didn’t get quite right — so I can listen to it without distraction or regrets. I know that nobody will notice these except me and the type of listener who does catch them will either not mind or appreciate it the way I would. But when it’s my own work, it’s different. I’m sure it’s the same for filmmakers so I understand the impulse to fix it later.

I'm hitting a bug where clicking New York just refreshes the page instead of loading the city's page. Los Angeles, San José, and... most cities seem to exhibit it. Chicago seems to work?

Picking a city was tough. It insisted on the more general New York instead of the more specific Long Island City.

Thank you!

Comments URL: https://news.ycombinator.com/item?id=38859589

Points: 2

# Comments: 1