Ah, I see how my wording was confusing. I mean planning in the sense of “How will we complete the work that we already committed to?” and “What will we do today to achieve our Sprint goal?”

I arrived at the word planning because Scrum is sometimes described as a planning-planning-feedback-feedback cycle. You plan the Sprint, you plan daily (Daily Scrums), you get feedback on your work (Sprint Review), and you get feedback on your process (Sprint Retrospective).

lol I hope your standups are not actually like this! The purpose is to, as a team, plan what the team will do today to achieve the Sprint goal

On mobile atm but there’s the Princeton books on Computer Science

Agile is indeed more of a mindset than a rigid system. In my recent experience helping a tabletop game team, we applied Agile principles to great effect. Rather than trying to perfect every aspect of the game at once, we focused on rapidly iterating the core mechanics based on player feedback. This allowed us to validate the fundamental concept quickly before investing time in peripheral elements like the looks of the game.

This approach embodies the Agile value of ‘working product over comprehensive documentation’ - or in our case, ‘playable game over polished components’. By prioritizing what matters most to players right now, we’re able to learn and adapt much more efficiently.

Agile thinking helps us stay flexible and responsive, whether we’re developing software or board games. It’s about delivering value incrementally and being ready to pivot based on real-world feedback.

I appreciate your candor about not wanting to speak on topics outside your expertise. That’s commendable. I wonder if we can still talk with the understanding that we may not know it all. I truly believe curiosity is able to sidestep many of the problems related with ignorance.

You’re right to be cautious about appeals to authority. My intention wasn’t to suggest NASA’s use of Agile validates it universally, but rather to counter the OP comic’s implication that Agile is inherently incapable of achieving significant goals like space exploration.

Regarding Agile-like practices in earlier NASA projects, you’re correct that concrete evidence is limited. However, we can analyze their approaches through the lens of Agile principles. Scrum, for instance, aims to foster characteristics found in high-performing teams: clear goals, information saturation, rapid feedback loops, adaptability to changing requirements, and effective collaboration. These elements aren’t exclusive to Scrum or even to modern Agile methodologies. The key is recognizing that effective project management often naturally gravitates towards these principles, whether formally adopting Agile or not.

It’s an interesting area for further research: have complex engineering projects historically incorporated elements we now associate with Agile? If so, how?

Your skepticism is valuable in pushing for a more nuanced understanding of project management across different domains.

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.

Edgy meme: agile bad

NASA: “Yep, we use agile” https://ntrs.nasa.gov/api/citations/20160006387/downloads/20160006387.pdf?attachment=true

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.

The way string of any material is woven should be durable. But plastic can be a magical material. It doesn’t cool when wet, regardless of whether it’s got fat on it (unlike wool, which requires lanolin). And its cheapness makes it readily available to billions of people.

To be clear, yes, we should avoid overproduction and overconsumption of plastic. Yes, we should research cheap ways of making durable and waterproof/still-warm-when-wet clothes that are biodegradable. Yes, we should require good filters in every washing machine and dryer so that we don’t get full of microplastics.

Sometimes I don’t either…

I think most of the criticism on Telegraph regarding how Matrix handles rooms and events are addressed by the work behind linearized matrix: https://www.qwant.com/?l=en&q=linearized+matrix+messaging&t=web

EDIT BEINGS HERE

So I actually watched a talk by the person who coinded “enshittification”, Cory Doctorow, recently, and I have changed my perspective about Kagi. I no longer think Kagi is doomed to enshittify.

Enshittification requires advertisers. As long as Kagi finances itself with money that does not come from advertisers, it will not enshittify.

This does not mean that it’s not problematic that their code is closed-source.

EDIT ENDS HERE

I like what I hear about the user experience, but there are many problems I see with the service.

For one, it’s based in the USA, so it is legally subject to the insane, antidemocratic, and awful state surveillance there.

It is also a corporation, so it is subject to enshittification. Currently, it is giving users loads of stuff so that users use it, but sooner or later investors will want their money back and Kagi will enshittify.

Finally, these two problems would be mitigated by open-sourcing and making libre their software. With that, alternatives in more sensible legislatures could open. Users could migrate to instances that are still libre and not enshittified.

It is really unfortunate that Kagi is doing so many things well while doing some fundamental things terribly. As it stands, Kagi is doomed to enshittify.

Except a restaurant is not asking to log every word of yours in exchange for pizza.

Pro tip: think of a bracket as an S and a 2 on top of each other. Which one is on top of which will depend on whether you’re writing an opening bracket or a closing bracket. Just try it out and you’ll see which is which.

After you try it out, as another comment pointed out, think of your 2s and Ss as surrounding a circle. That way your traces get closer to the actual shape.

And hello post-quantum encryption ✌️ https://www.youtube.com/watch?v=-UrdExQW0cs

I remember a Mastodon thread where this same issue was brought to the table. The thread talked about how before there were classes of bugs that would mess up RAM. Today, we eliminated a whole class of bugs by checking RAM. That is why our software is less snappy.

I wonder to what extent zero abstraction languages like Rust could make software much snappier by minimizing memory-related problems at compilation time rather than run time.

Thanks for the recommendation. I didn’t know such little reduction in quality meant so much savings with JPGs and PNGs!

Yeah. Avif gave me some nasty artifacts on some pictures that I wanted to save long term. Not using it anytime soon… or at least until those issues are fixed.

Why do you dislike WebP? I can see that it isn’t widely used, so if longevity is my goal JPGs and PNGs are a better bet. But am I missing something about WebP?