• 13 Posts
  • 88 Comments
Joined 3 years ago
cake
Cake day: July 18th, 2021

help-circle

  • I can see you’re frustrated by the downvotes and pushback you’ve received. It’s understandable to feel defensive when your viewpoint isn’t well-received. I appreciate you sharing your perspective, even if it goes against the majority opinion here.

    Your points about the space shuttle program’s challenges are valid and worth discussing. It’s important to note the timeframes involved though. The shuttle was developed in the 1970s, well before agile methodologies emerged in the 1990s and 2000s.

    Interestingly, one could argue that NASA may have used agile-like practices in the space shuttle program, even if they weren’t labeled as such at the time. However, I did a quick search and couldn’t find much concrete evidence to support this idea. It’s an intriguing area that might merit further research.

    Regarding modern agile approaches, while no method is perfect, many organizations have found them helpful for improving flexibility and delivering value incrementally. NASA’s recent use of agile for certain projects shows they’re open to evolving their methods.

    I’m curious to hear more about your thoughts on software development approaches for complex engineering projects. What do you see as the pros and cons of different methodologies? Your insights could add a lot to this discussion.



  • Your comparison is interesting, but let’s consider some historical facts. The Apollo program, which successfully put humans on the moon, actually employed many principles we now associate with Agile methodologies.

    Contrary to popular belief, it wasn’t a straightforward Waterfall process. NASA used frequent feedback (akin to daily Scrums), self-organizing teams, stable interfaces so that teams are an independent path to production, and iterative development cycles - core Agile practices. In fact, Mariana Mazzucato’s book Mission Economy provides fascinating insights into how the moon landing project incorporated elements remarkably similar to modern Agile approaches. Furthermore, here’s a NASA article detailing how Agile practices are used to send a rover to the moon: https://ntrs.nasa.gov/api/citations/20160006387/downloads/20160006387.pdf?attachment=true

    While it’s true that building rockets isn’t identical to software development, the underlying principles of flexibility, collaboration, and rapid iteration proved crucial to the missions’ success. Programs like the Apollo program adapted constantly to new challenges, much like Agile teams do today.

    Regarding Kanban and Scrum, you’re right that they fall under the Agile umbrella. However, each offers unique tools that can be valuable in different contexts, even outside of software.

    Perhaps instead of dismissing Agile outright for hardware projects, we could explore how its principles might be adapted to improve complex engineering endeavors. After all, if it helped us reach the moon and, decades later, send rovers to it, it might have more applications than we initially assume.



  • We are at risk

    of losing many developers who would otherwise choose a license like the GPL. Fortunately, I’m glad to be surrounded by people, just like you, who care about licenses like GPL. By uploading this type of content and engaging with it, be show our commitment to it. I wish to suggest how we can deal with this threat.

    We will lose developers who choose GPL if we use words that suggest GPL is “restrictive”. Sure, the word “restrictive” was avoided in this meme by using the word “copyleft”, but the cognitive jump from “permissive” to “restrictive” is minimal: just add an “opposite” and you’ve got “permissive is the opposite to restrictive”. It really is that simple. That’s how brain works (check out Relational Frame Theory to see how that works).

    So what can we do about it?

    Well, we can approach this with science. There is a historical global trend towards people being more meta-cognitive. That means that people are becoming more aware of how our thoughts interpret everyday reality and how to be intentional with our relationship with our thoughts so that we live better lives. We know this trend is happening to virtually everyone everywhere because of the work of brilliant sociologists like Anthony Giddens and Christian Welzel. Heck, even the history of psychology —going from noticing and changing behaviors (behaviorism) to noticing and changing behaviors and thoughts (cognitive-behaviorism), to noticing and changing the context and function of behaviors, thoughts, and emotions (functional contextualism)— reflects this trend.

    We can use meta-cognition in our favor; we can use the meta-cognitive tool of framing to change how we think about GPL and MIT licenses. Effective communicators like influencers, political campaign experts, and influential activists use framing all the time. For example, instead of using the dangerous framing that suggests GPL is ‘restrictive’, we can use another one that truly displays the virtues of the license.

    What would this other frame look like? I may not have a perfect answer, but here are some

    ways of framing (thinking about) the relationship between licenses like GPL and MIT:

    (ironically!!!, these were ‘suggested’ by an LLM; I wonder if these frames already existed)

    • “Investment-Protecting Licenses” vs. “Investment-Risking Licenses” (as in developers invest by working on projects that they could (not) lose the ability to contribute to)
    • “Community-Resource-Guarding Licenses” vs. “Exploitation-Vulnerable Licenses”
    • “Give-and-Take Licenses” vs. “Take-and-Keep Licenses” ⭐
    • “Freedom-Ensuring Licenses” vs. “Freedom-Risking Licenses” ⭐
    • “Contribution-Rewarding Licenses” vs. “Contribution-Exploiting Licenses”
    • “Open-Source-Preserving Licenses” vs. “Closed-Source-Enabling Licenses”

    I’d be happy to hear what you think, including suggestions!


  • A friend of mine and I have gotten used to using it during our conversations. We do fast fact-checking or find a good first opinion regarding silly topics. We often find it faster than digging through search-engine results and interpreting scattered information. We have used it for thought experiments, intuitive or ELI5 explanations of topics that we don’t really know about, finding peer-reviewed sources for whatever it is that we’re interested in, or asking questions that operationalizing into effective search engine prompts would be harder than asking with natural language. We always always ask for citations and links, so that we can discard hallucinations.



  • The article’s “valuing your time” argument is problematic in certain contexts. My brother has had so much trouble with his dual-boot (Windows and Linux). Yes, he could learn how to solve something in Linux every time a problem arises, but he also has to deliver his projects on time. Because of that, he mostly spends time on his Windows dual boot. Yeah, it sucks ethically and has its own pragmatic issues, but he has never had issues resolving dependencies or hunting down the most recent version that can actually be run in NixOS.

    I don’t doubt these will become issues that will not be as problematic in the future, but right now my brother cannot use Linux reliably for his assignments.

    Edit: My brother has tried what I use: Fedora and NixOS. He has also tried PopOS.

    In Fedora, he found some of his software didn’t exist as .deb, and struggled to make .tar files work smoothly for him.

    He tried NixOS afterward. He really liked the whole immutability thing, as well as the idea that apps would have their own dependencies.

    His dependency problem happened in PopOS. If I remember correctly, it was a code editor that required a version of something that was different to what a package he used in his software was.

    I think the order he tried was Fedora -> NixOS -> PopOS -> NixOS -> ? (Haven’t talked to him about it recently)




  • Thanks for the reply! Here’s their 2024-5-8 reply for reference:

    Hi! Our engineers have conducted a thorough analysis of this threat, reconstructed it experimentally, and tested it on Proton VPN. We concluded that:

    • the attack can only be carried out if the local network itself is compromised
    • our Windows and Android apps are fully protected against it
    • for iOS and macOS apps, you are completely protected from this as long as you’re using a Kill Switch and a WireGuard-based protocol (our apps use WireGuard by default, and if a user wants to use something other than WireGuard derivates, they’d have to manually set it up). Note that Stealth, WireGuard TCP, and our Smart protocol on iOS/macOS are all WireGuard-based.
    • for our Linux app, we’re working on a fix that would provide full protection against it.






  • You seem to be doing quite some things well. Maybe pay attention to your brushing? My dentist once had me brush my teeth in front of her and identified why in some teeth I’d consistently be clean and in others I’d consistently build plaque.

    Her recommendations: brush from the gum to the tip of the tooth. Try to aim at the holes between teeth. Pay close attention to the part in front of your tongue, in your lower front teeth; that part can easily build plaque if you don’t use the tip of your brush well to get in the holes between your teeth.