• 0 Posts
  • 100 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle















  • I’ll rephrase them, except in good faith:

    1. Talking directly to the people about the work is better than a 95 state JIRA pipeline

    2. Document your finished working work, not every broken POC, because that’s a waste of time

    3. If the contract isn’t actually going to meet the desires of your stakeholders, negotiate one that will

    4. If you realize the plan sucks, make a better plan.

    My company paid to have Kent Beck come to workshop with our Sr devs. I expected to dislike him, but he won me over pretty quick.

    I don’t remember what it was, but someone was like “Kent, we do X like you recommend in the manifesto, but it creates Y, and Z problem for us”

    And he was like “So, in your situation it isn’t providing value?”

    Guy was like “No”

    “Then stop doing it.”

    It’s not hard. It’s the most fucking common sense shit. I feel bad for them because these guys came from a world where there were these process bibles that people were following. So they wrote like, basically a letter saying “if your Bible doesn’t serve you, don’t follow it”

    And all these businesses dummies were like “oh look, a NEW bible we can mindlessly follow”


  • Ok, I think I see your position more clearly now:

    You’re thinking about people who are interested and installing based on technical interest and curiosity.

    In those cases, I think you’re probably right. There is probably some base competency at play. A desire to learn. Probably someone in their sphere to support.

    I’m thinking more about the type of people who would buy a Chromebook. Or my cheap ass parents who want to squeeze another 5 years out of an ailing laptop. They don’t want to spend any money and just want to use Facebook and YouTube. Send some emails. Connect to wifi. Print their boarding passes. Not have their machines riddled with viruses within minutes because their windows OS isn’t getting security updates anymore. I think this is actually a massive use case, and I want Linux to be accessible to them without needing to use the terminal for anything.


  • I can’t even begin to count the number of times I’ve seen absolutely terrible advice posted and taken regarding how to do things in Linux. Can’t connect to something? Easy, make a blanket iptables rule to permit everything. Something can’t read a file? Chmod 777. Install isn’t working? Just install as root and use root as your general login from there on out.

    It’s hard to learn Linux.

    But it’s even harder to FORGET what you’ve learned, to empathize with what it was like to not understand it at all. That’s why it’s SO HARD for us who’ve been using it daily for a decade to empathize with newcomers.

    It’s why people literally can’t fathom why people are afraid of the terminal.

    It’s why, even when someone takes the time to explain why, people go, “nah, that couldn’t possibly be it”

    It’s like when gun people can’t comprehend why people are afraid of guns. The answer is obvious they just can’t hear it.

    Edit: I think I better understand that there are more nuances around the cases now, and I think I’m being unfair by making blanket statements about what is and isn’t obvious



  • IMO, caution, wariness, concern, and unfamiliarity manifest as revulsion.

    EVs. Solar panels. Heat pumps. Anything outside of CIS heteronormal relationships.

    I’m my experience, after the age of like, 25, people (in GENERAL… Obviously many expectations) feel like they’ve got life figured out and push back against pretty much anything that challenges whatever they’ve grown accustomed to.

    Nobody bitched about the DOS prompt when nobody knew how to use computers. Young people learned it. Old people insisted computers were a fad and pushed back entirely.

    In my calculation, it’s just typical and predictable human response. Open to other theories though.