defrex

That compound command issue is infuriating, and really what drove me to make this.

FWIW, the prompt is easily adjustable in a `.claude/PERMISSION_POLICY.md` file in the project.

It's also quite easy to remix the script with claude to meet your needs. Right now it prompts the user and runs the script, so it's a race. If you added a delay in the script and increased the hook timeout in `.claude/settings.json` you should be able to accomplish what you're looking for pretty easily.

I suppose my advice would be: when you're hand-rolling rolling particle effects in Canvas, test them on more than just an M-series Mac.

This is a reasonable conceptualization, IMO. However, the problem isn't that we can't access the information in a black hole (there are other places in the universe where information becomes inaccessible).

The problem is that black holes evaporate. If the particles released via evaporation don't contain the information about the particles that entered, information is lost when the black hole is completely gone.

The proposed solution is that the information is encoded onto the surface of the black hole and thus into the hawking radiation being released from that surface.

Flutter is Canvas-based on the web, so this post well-could mean a switch to Flutter. Hard to see how non-Flutter customer Canvas-renderer for Google Docs makes sense.

Whilst it's obviously powerful, I often find myself wishing math used syntax even half as easy to understand as any decent programming language.

I suppose it's a result of being developed on a chalk board, but math seems be value _terseness_ above all else. Rather than a handful of primitives and simple named functions, it's single greek characters and invented symbols. Those kind of shenanigans would never pass a code review, but somehow when we're talking about math they're "elegant" and "powerful".

I call bullshit. Math syntax is bad.

Perhaps simply

> cross _visual_ design off your list and get back to working on the hard stuff

Multiple configurations are a maintenance burden. So, all else being equal, it's better not to have them. That said, not all else is equal, and configurability can indeed increase the user experience. But if your defaults are so good that very few people take advantage of the settings, you're better off dropping them.

For me the killer feature of ST is multiple cursors. Despite being relatively fluent in vim, that one feature has always prevented me from switching.

CareGuide | Software Engineer | Toronto

We are hiring software engineers to help us improve our online marketplaces: CanadianNanny.ca, Sitter.com, Housekeeper.com, PetSitter.com, ElderCare.com, and HouseSitter.com.

We need to iterate faster on our core features, and to add new things. Just as importantly, we run several unique automated marketing systems (which have powered our outstanding growth) and have big plans for where to take them.

We follow modern software development practices, including TDD, CI, and rigorous code reviews. We are very analytics driven and continuously run a/b tests to inform our product design. Our whole company has engineering-oriented approach.

Our current stack is Ruby, Rails, Haml, Sass, React, MySQL, Solr, Redis, and AWS. We are building mobile app using React Native. What would you add or change?

We are a fast-growing company. Our one-of-a-kind investor group includes over 60 successful entrepreneurs.

An interesting thing about CareGuide: as a tech startup, we employ more women than men, and have a high degree of ethnic and religious diversity. We also have employees in their teens, 20s, 30s, 40s, 50s, and 60s. We hire the best and build careers.