Well Devops isn’t a role. It’s an approach in which bridges development and operations and integrating it in the team. It isn’t sticking a cloud engineer (cloud biased sysadmin) in the team. It’s about collaboration and delegating and supporting.

Cloud engineer is unfortunately what many orgs think devops is.

Ah interesting. Appreciate the clarification. Not seen much from Beehaw in a while.

Lemmy.world has a higher percentage of questionable users for sure.

Separate point, but are beehaw now not defederated from the world? When did this happen?

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.

Same here. Dreadful name. Classic open source.

deleted by creator

[email protected]

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

Probably just process. They’ll send an updated fob off letter. Right wing gov that represents business, not people.

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.

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

What IDE is this?

Ah, apreciate the clarification.

Why does this feel lie a viral marketing campaign to get people to watch stuff on X?

“I interviewed Elon, got cancelled and he mad. Watch on X”. It just doesn’t add up to me.

Edit: It’s not on X, apparently. It’s on YouTube. So I was probably a little out on this. Very clever viral marketing still, but hopefully not to the benefit of X.

They sunset Atom to push VS code despite assurances they wouldn’t.

Co-pilot slurping open source code and spitting out code without license attribution. One example of this was when it spat out Quake 2 code and comment verbatim.

Enshittification started, you just ain’t ready to see it yet. MS has a track record and will continue.

2 git hosts is just 2 tabs and by the time federation happens, you’ve already got vendor lock in because of all the issues. I doubt migration of those will be straightforward.

Interesting project and good luck on this.

Did you not consider something like Codeberg to host this? Many open source devs do not trust MS or their stewardship of Github, and considering the aim of this project is against American control of information, surely this really needs serious consideration.

Many open source devs do not want to use Github at all now.

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.

Most users find mobile banking works out of the box on GrapheneOS.

I’m not disputing the last stuff is not fun. Matrix works quite well and you can set up a bridge with discord. Using spaces correctly cuts down spam easier also. The problem remains, even if you set them up, my experience is 92% of users come in through Discord. I’d love that to change, but it’s just a fact of the matter.