Yeah, I use TW and it just works. I game on it with no issues.

Do questions really need to be answered outside of work time? Are blockers identifiable in advance so a plan can be put in place. Not many things need to be done outside work hours and team members can cover vacation if something desperately needs to be done.

Codeberg, or failing that, GitLab, or BitBucket. Allowing MS to control all FLOSS software, means they might probably secretly get consent to use your code for copilot training without respecting licences. I have no idea if this happens, or might in the future, as I ain’t reading the terms of service for something I do not use, however, I have little trust for them enough for air on the side of caution.

I use OpenSuse for gaming. A great distro.Highly recommend. An up to date kernel, stable and just works.

Had bad experiences with Manjaro so personally wouldn’t recommend.

Nothing says innocent like threatening with lawsuits…

It’s got big corp, reputation at all costs over doing the right thing vibes. The latter is reflective and willing to improve even if things aren’t bad, but could be better.

People will make their minds up based on how much they trust them. Personally, I don’t.

Oof. No ability to learn. It was bad. The cover up/fob off just makes it worse.

Same here. Dreadful name. Classic open source.

deleted by creator

Lol nah. But Lemmy world has a somewhat rude intolerant moderation policy and often users mirror that. There is good people on there, of course, but a reasonable percentage of folk who’d be at home on reddit and Xitter.

Removed by mod

!degoogle@lemmy.ml

Happy to chip in, but not as sole mod. I ressurected the DeGoogled community on lemmy.ml and overseeing it since then.

Completely self serving though. Mobile is a personal data goldmine and Google gotta dig into that one way or another and if folks can contribute to that side with bug fixes, great.

Do you really need to make a case? Does your company not trust devs? Is there people leading that have no idea about technology? SVN is dead. Many devs won’t touch it. It’s best way to say to new candidates your company is backwards. Many would refuse to work in a company that uses a version control system that has been dead 7 years.

Because it does the things well gamers want. They want to play together, and talk together (voice chat), and stream showing them bossing or doing something IG. It does those things very well. If matrix gets seemless voice calling and video/screensharing at the click of the button, they would find it easier to make inroads.

It also has sensible defaults for managing users etc. and it’s effortless.

It’s not about features, it’s just about getting the basics right.

Matrix is the best choice we have. Embrace it or make better because we can only use what is out there.

You didn’t even need to read the article. That information was in the preview…

What IDE is this?

Usually when you change your database structure, you would change the object that this is mapped into. If you were to change one without the other, that would be a monumental developer oversight. Adding a field without using it in many frameworks wouldn’t necessarily break it, so it wouldn’t be a bad change per se.

Any change you make to persistence should reflect as a bare minimum, the object data gets mapped into. This would likely be part of the same branch, and you probably shouldn’t merge it until it’s complete.

You’re looking for tooling to protect you from human errors, and nothing is going to do that. It’s like asking, how can I stop myself from choking when eating. You just know to chew. If this isn’t obvious, it’s a good lesson in development. Make one change at a time and make it right. Don’t rush off to presentation changes or logic changes until your persistence changes are complete. When you get into habits like this, it becomes steady, methodical and structured. Rushing is the best way to make mistakes and spend more time fixing them. Less haste, more speed.

For example, if I add a new field. I’d write the SQL, run it, populate a value, get that value and test it. Then I’d move on to the object mapping. I’d load it into the code, and get a bare minimum debug out to see it was loaded out, etc. etc… Small tweak, test and confirm, small change, test and confirm. Every step is validated so when it doesn’t work, you know why, you don’t guess.

Most languages have an IDE which will manage the import of that object and when you rename incorrectly, it’ll flag it up. If you’re calling an incorrect function or variable, it’ll flag it etc. Many will have refactoring tools so when you rename something through this, it’ll rename all instances of that.