Recently did this and yes it’s a pain. I don’t know if it’s going to help until next time we change phones, but what I did this time was name the device after the person, rather than the phone model.

The idea being that I can delete the old device in the future and replace it with the new device, named the same. That way I don’t have to change the device name in each automation every time. Hopefully that made sense. But I still haven’t tested it in reality.

Exactly, it was a crappy stop gap solution.

So a game could release an “update” with less content and charge for it, and that would be ok to call a DLC, because they charged for it?

It’s not a walled garden, it’s kind of the opposite. You can connect devices regardless of brand and it’s a server you can run locally. In theory you wouldn’t need to update it or ever connect it to the internet again, as long as your devices can run locally.

If you have an old laptop or a raspberry pi 4, you can always give it a try before scrapping what you’re currently using.

My comments are actually after seeing the local pricing. I still think it’s too expensive. Perhaps other locations are more affordable.

This post is asking what apps are worth paying for. Someone suggested Sync is worth paying for. I disagree and offered a different opinion. No one said you had to pay for it, just whether it was worth paying for or not.

I’m sticking with Voyager for now. Sync is too expensive for a beta app. There’s no post functionality in it yet. I’m also not sure how I feel about paying so much for an app to access Lemmy. I’d rather put some of that money into the instances themselves.

It already has it. If you click on your account and then edit, you’ll have the option to add another account.

It’s always hard when you leave a game. I left Sekiro for a bit over a month. The only reason I went back to it was because I was waiting for another game to install and thought I’d load it up again. I’m glad I did, because I didn’t drop it after that.

No that’s the first encounter. He’s hard, but it’s just a matter of learning the move set. You can do it!

I spent over an hour on one of the other bosses. I’m not good. I still managed to do it haha.

You can also look up some guides. Not to cheese him, but to help you get a look at the move sets so you aren’t in the thick of it while you’re trying to learn them.

Which Owl? I spent a lot of time on a couple bosses, sometimes it clicks and sometimes it doesn’t. If you keep at it you’ll eventually get into a pattern.

Yeah no worries. Sorry, still getting used to the crosspost stuff, so should have mentioned the Sekiro community.

Oh I already posted on the Sekiro community as well. Was just trying to test out the cross posting feature.

Oh right. I’ve been using Voyager so maybe that feature isn’t there yet. Will give it a shot on the web version.

How do I do that?

It doesn’t help that users might be split across instances. I posted recently over on this instance: !patientgamers@lemmy.ml

I didn’t want to repeat my post and annoy people who might see it two or three times.

https://lemmy.world/post/1977669

Agile isn’t meant to replace anything. You need to use the right method for your context. No one said the purpose of agile is to replace all other methods.

Agile doesn’t have to be implemented perfectly to work. You seem to be holding agile to some higher standard than anything else.

You have to get over the communism comparisons. They aren’t relevant.

Just because you haven’t worked in an agile environment you enjoyed, that doesn’t mean it can’t work. It can and does work. Just like any other method. And it can and does fail. Just like any other method.

OP didn’t work in agile. They were told that they were working in agile but it was just an excuse for the business to not have requirements and continually change their mind. Every one of the issues they raised could have happened in any other methodology. It’s poor management.

So if all approaches are poor, then anarchy? I think you need to move on from the communism comparison, and the idea that unless something is perfect it’s not worth doing.

Believe it or not, there are people working in successful agile teams right now. Just because you haven’t, that doesn’t mean it isn’t tenable.

I disagree. I’m currently working in agile and it’s the best team I’ve worked in/with. It can easily go wrong, but it can also work really effectively. Implementing agile in an “ok” way, is still better than waterfall in most instances. Of course it depends on the business context.

Take all of OPs complaints for example. Sure, they can be an issue if agile is implemented poorly (or not at all in OPs case), but all of them are inherent issues with waterfall. Developing something only to find out days before launch the business has something else in mind. There would be much less chance of that happening in an agile environment over something like waterfall.

There’s a big problem with people saying they work in agile, when they’re really not. Like in OPs instance. And that leads to the negative sentiment about agile never working. I get it, I’ve been there and had to work in agile teams that weren’t really agile. That doesn’t mean it can never work.

It’s a steep learning curve (was for me anyway), but it’s really rewarding when you get it.