Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)UX
Posts
0
Comments
66
Joined
2 yr. ago

  • Lenin ordered the Red Terror. The main difference between him and Stalin when it comes to willingness to use state violence was the size of the state. His solution to political decent was mass executions. While it was announced as a class war on the bourgeoisie, it began with a massacreof sociallists. In addition to kulaks and white army afficers, it targeted the former bolshenik allies Left Socialists, anarchists, and striking workers. The Red Terror featured the creation of the gulags and concentration camps, hostage taking, and torture.

  • Note:

    just like you council people out when they underperform for your org, council people out when they can no longer grow or advance. Those people will also be unhappy over time, and create drag on your whole org. Make opportunites to grow, to grow elswhere in the company, and finally at other companies

  • Yeah, this. I lean heavily into coaching, which is specifically helping them apply skills they already have to a problem.

    I also draw clear lines between what I can help with and what I need to do for the company, and try my best to display when I am fighting for them and when I cannot. Building trust is a key part of the relationship, and having suspicion that you are two faced kills it dead.

    With this and the other things mentioned, I too have only had peopae quit because of money, and in one instance he came to me to ask if he should do so (we talked it out without me giving any advice, just comparing opportunities)

  • Both styles have advantages and disadvantages. Fully procedural code actually breaks down in readability after a certain length, some poeple suggest 100 or maybe 200 lines, depending on how much is going on in the function.

    Blanket maxims tend to to have large spaces where they don't apply.

    Additionally, the place where the code on the right is more likely to cause bugs and maintainability issues is the mutation of the pizza argument in the functions. Argument mutation is important for execution time and memory performance, but is also a strong source of bugs, and should be considered carefully in each situation. We don't know what the requirements for this code are, but in general we should recomend against universal use of argument mutation (and mutability in general).

  • As a software engineer, skills I think I could contribute are systems design, debuging, writing software, and also trash pickup on the back af the truck. I'd be happy to help build software tools that help people actually enjoy life, and also I eon't mind pitching in to my community.

  • Show them the consequeces. You might scare a few people who are already anxious by showing data collected, but most people will be apathetic. Illustrate why its bad. Be systemic about it.

    The stunt outlined elsewhere of texting someone with their info is good, but "we all know google isn't going to threaten us" is the prevailing attitude. Demonstrate what google is going to do and how it hurts people individualy and directly. Until there are personal consequences, peopae won't really care.

  • I feel like, with this reply, you are willfully glossing over my point. The issue at hand is that open source software is short on the ux design expertise. My claim is that by centering the programing expertise, and in fact by not going out of the way to be inviting to the non-programming expertise, open source projects are self-perpetuating these cycles.

    We can find ways to invite good designers in, or we can continue with the "sufficient" design ost projects currently have.

    I'm happy if people have ather strategies for overcoming the current problem, but the current aproach is not doing it

  • Sure, you can pr the design files, but thats not how the messaging comes across. Even the "how to contribute" for most projects, if they have one, is usually entirely technical. The majority of designers (not all) I have worked with have been very shy about technical work, so having no clear "non-technical" contribution pathway is a deterent.

  • that second part is exactly why there is a lack of hci work in the linux space. Hci is a specialty, just like coding is. The standard ask of "create a pr with the code" is asking peopae who don't typically code to do so, in addition to doing the work of researching the problm, designing a solution, and then testing that solution for suitability.

    Since the only mechanism most open source projects have for accepting contribution is code, and the ask is usually for code, there is never even an opportunity to submit design work.