428 karma · joined June 30, 2019
The U.K. has more than triple what we have. If we had 1500 representatives, that’s roughly 1 per 225k people. Not a great number, but much more reasonable at least, and also much closer to what representation was when the House was capped.
Smaller districts mean not just more accountability, but more similarity within the district. Right now, my district is 95% rural and 5% a slice of a city. I live in the city part, therefore my rep doesn’t care about what I have to say, as my wants and needs are different than the rural population that makes up the majority of who vote for him. Smaller districts are harder to gerrymander like this, and they also mean your rep probably lives a life relatively similar to yours - drives the same highways, experiences roughly the same tax burden, shops at the same places, participates in the same events. This will not be true for every case, but it’s still a better situation than what we have now.
If you keep your PRs small I guess the end result is the same, but even then I like things in individual commits for ease of review.
I also like it for myself, when I’m going over my own PRs before asking for a review - I will often amend commits to ensure the work is broken down correctly, each thing that should go together, does.
In a way, stacked PRs are just a higher-level abstraction of this too - same idea, keep work that goes together in the same place.
It's absolutely not for everyone, though it looks like some of the pre-built configs (NvChad, LaZyVim, etc.) are decent enough of the box now that you don't need to go on the endless-customization journey if you don't want to. To me though, that's the appeal: tinkering, tweaking, refining. Generally when people ask if they should use Vim, I tell them probably not but try it for a few weeks and see if it clicks in your brain. I had a great VSCode setup, everything worked great, I was productive, but something about Vim just made more sense to me once I got over the hump of modes and all the keymaps you need to turn into muscle memory.
Edit: I also like that I can do abominations like:
("def" @keyword (#set! conceal "ƒ"))
("if" @keyword (#set! conceal "?"))
("unless" @keyword (#set! conceal "¿"))
("else" @keyword (#set! conceal "∶"))
("elsif" @keyword (#set! conceal "⁇"))
("case" @keyword (#set! conceal "⟨?"))
("when" @keyword (#set! conceal "→"))
("begin" @keyword (#set! conceal "⌊"))
to make Ruby look absolutely insane. Is it useful? No. Do people hate it when I share my screen? Yes.
Why does one show up and one doesn’t? The one that doesn’t is a built-in Apple app, too. They both have identical settings for “show app in search”. This worked fine before iOS 26.
- devs are so siloed, nobody knows what’s going on - product is not communicating anything outside of individual fiefdoms - there is zero QA testing - no designers are actually signing off on the final results
…which all seem pretty typical for a large bureaucracy, I guess I just had higher expectations of Apple, since we pay a premium for their products. Some of these bugs are frankly pretty embarrassing.
I think I had tracked 15+ things I would easily qualify as bugs the first two days after upgrading my phone - this would be absolutely unacceptable where I work, and we aren’t a trillion-dollar company with psychotic hiring standards.
Was this even QAed? I don’t like the look, but that’s a personal thing, these are actual issues that are not subjective.
You advocate for taking ownership over women’s bodies, because clearly you know best apparently?