Skip Navigation

Posts
30
Comments
540
Joined
2 yr. ago

Just a basic programmer living in California

  • I love to see discussion on specific ideas for how to make socialism happen! I agree, workplaces where workers vote on leadership, and share in profits could make a big difference. Someday I'd like that kind of structure to be mandated. But yes, in the meantime why not start implementing it?

    Have you heard about cooperatives in Italy? They have been around for decades, and have seen success - especially in Emilia-Romagna. I learned about this via a Youtube video, so I'll link that. Italy's Radical Solution to Extreme Inequality by More Perfect Union.

    The idea of building a better system from the bottom up is sometimes called "dual power". The idea is to create a counter to top-down state power, or oligarchic control. It can be a check on top-down power, fill in gaps where the state doesn't meet people's needs, build up a better system that can eventually replace the old system when it's ready, or all of the above. I did some quick searching and came across this document. But I'll admit I've only skimmed it at this point to verify that put also puts an emphasis on cooperatives.

    I've talked a tiny bit to people who have worked on starting cooperatives in the California Bay Area. What I've heard is that it's difficult to get business loans because banks are wary of business structures that they don't have experience with. But more specifically banks want to know who owns what: who owns the building the business operates from? Who owns the equipment? The people I talked to want shared ownership, which is at odds with what the banks want. I suspect there is some way to resolve that - probably with a corporation with shared ownership (like you described) that is the legal owner of capital. So that's an issue that's related to the legal question you brought up of what legal corporate structure would be best.

    You talked about The Owners electing a president and a CEO. Are The Owners shareholders? As in, people who own one share each? And workers would generally be owners?

    I think I've heard the idea that a company should have equal profit sharing for all workers. Personally I've also thought about the idea of automatic equity proportional to the time you've spent working with the company. Like every month or so shares would automatically rebalance. That could mean that if you've put in 1% of the total working months (including types of leave like parental leave), you get 1% of the shares. But I think it would be better to scale on a logarithmic curve, or something like that, so that it takes a little bit of time for new workers to ramp up their shares, but they get a boost to "catch up" to people who have been at the company longer.

    I like your ideas about payroll vs surplus incentives! I had some thoughts along the lines of CEO pay being capped at some multiple of the lowest paid worker, or leadership raises being capped based on a ratio of total payroll between the current and previous year. But to some extent I was thinking about possible external legislation, vs internal charter rules.

    I happen to be trying to start a business now. I don't know if I'll succeed. If I do, I don't know if I'll bring on more people. But if I do, I want to use a cooperative model.

  • Oh! Is this how bootlegging works?

  • Ok, I don't really know what I'm talking about. I think the deal is that there is a concept of a "bargaining unit", and the government usually limits bargaining units to one workplace, or maybe one employer. And employers can't be compelled to negotiate with a group that is not a single bargaining unit. So in practice organizing has to be done workplace by workplace. Unless I've misunderstood.

  • I had a workplace organizing training session the other day, and learned a couple of things. I'm not sure I have all this correct, but from what I recall US laws are strict in what kind of organizing is allowed - I think cross-industry unions aren't allowed. Contractors aren't eligible to unionize. (That's on top of the "wage theft" effect of classifying full time employees as contractors instead of W-2 employees.) Organizing protections for workers don't extend to managers. It's a lot of bullshit.

  • I got the impression the one-person entrance quota was for that specific region. Like maybe the sector they were in or something. In the TNG era the Federation has something like 150 member planets, I think. Plenty of those could have billions of inhabitants each. That would imply a lot of competition for space in the one campus by San Francisco! That might require strict entrance quotas.

    I don't know if Coming of Age is consistent with other depictions of the entrance process. In other stories it seems like getting in is much easier.

    I've heard speculation that the reason the Starfleet crews we see are so overwhelmingly human is because different species tend to stick together, and there are other ships and crews out there that are mostly non-human; but we happen to be shown the human ones in the shows. There have been explicit references to exclusively Vulcan crews, such as Sisko's rival's crew in Take Me Out to the Holosuite. Given the scale of the Federation I think it would make sense if there were lots of academies on different planets, and the Earth academy is the one humans mostly go to. But I don't think there's any hint of that in the shows.

  • Here's the data presented in the video:

    In Delaware in the 30 months following enacting their Idaho Stop law collisions involving cyclists at stop signs fell by 23%, and overall collisions involving cyclists fell by 8%.

    There was also discussion of motivation for rolling stop laws in US states. Idaho, which made this change years before any other state, did so to reduce the number of trivial cases using up traffic court resources. Other states were motivated to remove a pretext that police use to stop and detain people, especially people of color.

  • I think Templates is for cases where you make lots of documents that have the same starting structure. Like a letter head, or a spreadsheet you recreate every month. The starting structure can be saved in Templates so you can copy it ever time you need it. Maybe I'll put a Nix flake template there instead of always copying from a recent project.

    Public might be for files that other users have read access to on a multi user system? Or maybe for network shares? Or a personal website? I'm not sure. Edit: I found a comment saying that Gnome file sharing uses Public.

  • You can customize the names with a ~/.config/user-dirs.dirs file. That will work on XDG-compliant programs. instructions

  • I used to have a scratch directory. Then I realized I can put stuff in /tmp/whatever, and it gets automatically deleted on reboot. I made a shell function that creates a /tmp subdirectory, and cds to it in one command.

  • Me too! But now I'm thinking maybe I should capitalize the folder name

  • I also use a Projects folder. It looks like it probably won't break anything. Apps might start putting stuff there by default, hopefully in sensible subdirectories. There's a note in the article that you can create ~/.config/user-dirs.dirs to specify where you want files to go.

  • Season 3 was produced during a writers' strike. Hopefully the next season will be better

  • How did the makeup team do Dax's spots anyway? Were they painted by hand, and a little different every day of shooting? Did they have a template and spray paint?

  • Just open up the door. We'll all come inside, and eat your braaains!

  • There's also lithium iron phosphate (LFP) which doesn't catch on fire either, and has been around longer. There are trade-offs, like sodium being vastly more plentiful than lithium.

  • The humble bragging here smh

  • I like to use this style of italics for keywords. (That's also what the Maple examples do.) My thinking is you see keywords so often that you recognize them by shape, not by reading the individual letters. And my theory is that the italic variant being a little harder to read helps my eyes skim over keywords, to focus more on words that I do need to read precisely, like variable names.

    It does mean that I spend some time customizing my syntax highlighting theme to make it work the way I prefer. I've got examples set up on my blog. Although that's not Maple - it's a different font with cursive italics called Cartograph CF.

  • Now how to change the authentication failure message to read, "That procedure is not recommended"?

  • My guess is it's upscaled by an AI that doesn't know what Garak looks like. Or Cardassians.

  • Bicycles @lemmy.ca

    Clik valve review

  • micromobility - Bikes, scooters, boards: Whatever floats your goat, this is micromobility @lemmy.world

    Clik valve review

  • Programming @programming.dev

    The 6 Big Ideas of Typescript

    sitr.us /2026/04/06/big-ideas-of-typescript.html/
  • micromobility - Bikes, scooters, boards: Whatever floats your goat, this is micromobility @lemmy.world

    Bike mirror review

  • micromobility - Bikes, scooters, boards: Whatever floats your goat, this is micromobility @lemmy.world

    Tip for securing bikes on BART, or other trains

  • Nix / NixOS @programming.dev

    run Kodi media center

  • Bicycling @lemmy.world

    The milk crate usurper!

  • Mycology @mander.xyz

    Is this a death cap?

  • Pen & Paper @lemmy.world

    Hacking a pocket gel pen

  • Linux @programming.dev

    Selective VPN confinement in NixOS

  • Nix / NixOS @programming.dev

    Selective VPN confinement in NixOS

  • Linux @lemmy.world

    Spotted Linux on the back of a car

  • Mycology @mander.xyz

    Blue oyster mushrooms growing in a kit

  • Journaling Just Works @sh.itjust.works

    My favorite bullet journal guide

    www.thelazygeniuscollective.com /blog/how-to-bullet-journal
  • Nix / NixOS @programming.dev

    Patch interpreter path in embedded binary?

  • Nix / NixOS @programming.dev

    work around a misbehaving binary cache

  • Nix / NixOS @programming.dev

    Native Wayland gaming with Wine on NixOS

  • Rust @programming.dev

    Comprehending Proc Macros