This is the third person advocating button squeezing, as a reminder: IF a gun is on you the jig is up, you can be shot for resisting or reaching for a potential weapon. Wireless detonators do exist, don't f around please.
I like this approach. Something related I've been tinkering with are "protected bookmarks" - you declare what bookmarks (main, etc) are protected in your config.toml and the normal `jj bookmark` commands that change the bookmark pointer will fail, unless you pass a flag. So in your local "CI" script you can do `jj bookmark set main -r@ --allow-protected` iff the tests/lints pass. Pairs well with workspaces and something that runs a local CI (like a watcher/other automated process).
I haven't yet submitted it to upstream for design discussion, but I pushed up my branch[1]. You can also declare a revset that the target revision must match, for extra belts and suspenders (eg., '~conflicts()')
I'm glad you shared this because, in my head this Dr. Nick quote is so canonical it must be from the original golden 8 seasons, so it's nice to be reminded there are occasionally good things after! ;^)
Many learning materials will push you that way, but the vast majority of FOSS packages don't use it.
There's nothing inherently wrong with using Jane Street's stdlibs if you miss the goodies they provide, but be aware the API suffers breaking changes from time to time and they support less targets than regular OCaml. I personally stopped using them, and use a few libraries from dbunzli and c-cube instead to fill the gaps.
I think they meant the 'Plan with Opus' model. shift+tab still works for me, the VS code extension allows you to plan still too, but the UI is _so_slow with updates.
This is a fact of ZIP Codes that a lot of people stumble one. I've worked on GIS/mapping projects in the past where stakeholders wanted or assumed ZIP Codes to be polygons.
Another complexity that surprises folks is you can't guarantee a one-to-many state-to-ZIP Code relationship. There are several (I forgot offhand how many, I used to have them memorized) that span across state boundaries.
Yep, this fact eluded me earlier in the year. I was supposed to map out all ZIP codes in the US and color their boundaries based on certain stats we had. We were surprised to find many areas in the US were empty because they didn't have ZIP codes. I did a quick search and found out ZIP codes are driven by mail routes, and that instantly made sense to me, but the product stakeholders were very surprised to learn it.
One thing I just recalled is that if you maintain a small exceptions lookup table (i.e. the ones that span state boundaries), you can use ZIP Codes as a way to uniquely look up a county name.
For example, health care plans in the US are county-specific with regard to premiums, co-pays, etc. (based on demographics). Allowing someone to type in their ZIP Code to get started can be a better user experience than having them pick their county.
Yeah it makes it easier. And I’m appreciative of the idea of making address entry easier for users but if they have to disambiguate did you actually make it easier?
I think Zillow does it best. You just type your address in a box and it looks up the normalized full address.
Similar timing, I had a high school internship at the National Cancer Institute at Ft. Detrick, MD in 1994-95, and the lab down the hall had some SGI iron and a glove (I don't remember what the glove hardware was, if it was SGI or 3rd-party or custom) for manipulating 3D renders of folded proteins. Incredible stuff, same "in the future" feeling.
reply