Even if it was (a lot of similar designs are due to common inspirations such as folk tales, but also a lot are direct parodies, and parodies can be made legally distinct) (but also, the Pokemon team itself rejected the copyright suit suggested by the public in their own public statement a while ago) the lawsuit is over parents, not copyright. Patents implies technological theft. Or bogus patent claims, more often than not. (Patenting math should be illegal, for instance.)

It’s a very hard game. I really got into it playing with the Noita Together mod, and the Spell Labs mod when I was playing solo, to really figure out the game. Then once I felt I had a good grasp, I beat it, did the sun quest, eventually beat 33 orb Kolmi… Lost all my progress and had to do it again.

If you can’t tell, I love Noita, but I fell in love with the wand building first. Spell Labs has excellent tutorials on improving your wand builds too. But I now have modded the game, so I’m not a casual player of it either.

I’ve seen a few, but it’s still kind of controversial. That being said, there is a time and a place for agile where it works, but also there is a team composition and a style of agile which works and that style tends to piss off micromanaging middle managers, so it rarely is allowed.

I had an article saved in my work slack before I left that company (for health reasons), but a currently popular one seems to be this one: https://johnfarrier.com/agile-failure-what-drives-268-higher-failure-rates/

My take is based on years of interaction with companies and friends in other companies. The biggest problem isn’t necessarily Agile, but instead that agile is not intended for long term projects. Agile is fantastic in short turnaround interactions such as web dev, and because these short turnaround places have such easily visible results, managers take them to be gospel. Thus comes Corporate Agile: https://web.archive.org/web/20240524230754/https://bits.danielrothmann.com/corporate-agile Link is from the Internet archive because I can’t find his new site if he moved.

Long story short, corporate agile is the agile the bosses want, as it allows them to be constantly involved with more and more “agile” meetings. You know. Meetings. The antithesis of Agile. The place productivity goes to die. I had to remind our bosses that Agile dictated that stand ups included the developers and the scrum master ONLY multiple times and pointed them to the agile training they gave me. Didn’t matter. They’re the boss. This is a pretty common breakdown in Agile. So, that turned daily standup into daily meeting, since the quick status updates now had to be broken down for the boss. Every. Single. Day.

Agile at its most basic is intended to reduce meetings to once a week so the rest of the time can be spent developing. Every company I know starts including devs in at least 300% more meetings (even junior devs) after switching to Agile for at least 6 months. And on average, it takes half an hour for a programmer to return to the level of productivity they hit before any interruption. This is generally due to the limitations of working memory. (Many research papers on this if you want.)

But to get back to the original point. Because agile concentrates on short immediately tangible and verifiable benefits, any progress that takes longer than a sprint isn’t allowed. (It actually is, with proper implementation, as Agile is supposed to be edited on a team by team basis to make things work, but companies want everyone on exactly the same page.) Guess what doesn’t have immediately tangible and verifiable benefits? That’s right, research. Guess what it’s still in a research phase? Aside from basically anything that isn’t in market yet, self driving technology is very much research driven. Lots of trial, error, and long development cycles. Longer than a sprint for sure. And anyone who says self driving is in market should try an exercise if finding one level 5 self driving car that hasn’t been recalled due to false marketing or safety concerns. The technology isn’t there yet. It could be getting there, but profits are getting in the way of progress.

Realistically. Trains will revolutionize road transport of goods and people if the train industry properly maintained their rails, operated above board (unlike the one that had the chemical spill in Ohio and other issues), and expands a bit. The largest expense in good transport is long haul and no one wants to drive long haul. Last mile will probably need trucks and drivers for at least 3 to 5 more decades. And taxi services have similar challenges to last mile delivery. Personal self driving systems need even more consideration than taxi services, and will likely take five to ten years after taxi services become recognized as safe.

In my (in the industry) experience: Agile killed safe development by pushing superficial internal deadlines that look good instead of are good. Safety requirements therefore are never met, but people keep looking like they’re approaching at least one, but end up sacrificing other things that no one is concentrating on, causing more set backs than improvements. Self driving will not be legally commercialized until either someone lobbies bad development onto the roads, or capitalism realizes that quarter profit isn’t as important as ten year profit and Agile finally burns in a god damn fire.

I was told in 2009 “Why optimize? Hardware upgrades will make your efforts obsolete anyway.” So… I devoted my time to optimization, because fuck that. I ended up doing algorithm optimization in my first full time job, and loved… That part of the job at least.

Indie games and co-op games are my jam. I feel for all of this comment.

He got free food and a bed? Jealous.

The master branch in git isn’t the same though. It’s closer related to the word “remaster.” Master used to mean the original document is still used everywhere in tech and outside of it.

Main makes more sense since a master copy should be something that doesn’t change in my opinion. But that’s semantics…