• 2 Posts
  • 37 Comments
Joined 2 months ago
cake
Cake day: September 11th, 2025

help-circle


  • Technical debt aside of course the development process looks like that - what’s the alternative? Infinite feature growth? No one benefits from that.

    As an example, I’ve got signal on my phone- it started with texting features, added images, calls, video calling, but at some point there’s a limit on the number of useful ways to communicate.

    I don’t need it to be another social network.

    I don’t need it to tell me my horoscope, order a pizza, or organize my photos.

    I don’t need it to track my health, play games, read my work emails, or drive my car.

    It doesn’t need to integrate with VR, or AI, or whatever 2-letter buzz acronym comes up next week.

    It’s a secure messaging platform, I need it to send messages. Sure, there’s always a cat and mouse game of encryption to keep ahead of, but infinite feature growth? It’s not practical or necessary. Things can exist to do one thing reliably and well.



  • You could do PR with the ballot of potential Reps distributed by district. When the election is settled the district Reps are assigned starting with the highest-skewed district. E.g.:

    Overall vote: 60:40 (red:blue)

    D1: 80:20
    D2: 40:60
    D3: 70:30
    D4: 45:55
    D5: 30:70
    

    You can go randomly, round Robin, or winner-first to divvy up the districts, but essentially you would expect D1, D3, and D4 to be assigned their local red Rep (even though red “lost” in the close D4 race) and D2 & D5 to go blue

    With more parties, random or round robin are a little more “fair” for the third party - winner first allocation could result in 3rd party getting the “whatever’s left” district where they didn’t actually get any votes.

    It’s not perfect, but neither is the current system.