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

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.

It really isn’t. It inflates content from smaller communities.

New stuff in bigger communities won’t have as high a ranking.

Have you not checked scaled sort? It’s been around months and prioritises content in smaller communities over larger communities. Tie that with subscribed and you get exactly what is needed.

What IDE is this?

So you generalise anyone that uses an instance. I don’t think the problem is Lemmy.ml …

I don’t think you even see the irony in your post.

Care to explain…

I’m not a tankie, and I haven’t been banned.

You sure you’re not confused with lemmygrad?

Never seen evidence of that…

Try a better instance. Lemm.ee and Lemmy.ml are both run by competent techies and less knee jerk intolerance to anything other than the prevailing opinion there.

Examples?

I occasionally see this argument but not yet seen any evidence to back it up.

Lemm.ee is pretty sweet and well run. Ml and ee are superior to world IMHO.

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.

I take personal offense to that. How do you not?

Well, they run Afghanistan and af is the country code. They picked a domain that they thought was cute, funny or clever and didn’t consider longevity or risk. It’s on them. If I make a website. I won’t pick a silly extension that won’t survive long.

If you’re on the country code, you open yourself up to risk. ml has been a risk before.

Your headline is misleading though. Taliban didn’t kill it. Admin did.

Why not just use Reddit? It is huge, and mainstream?

Product owners, you mean. They are the ones that determine support level of browser and as a result, what testers focus on. Devs don’t focus on things that aren’t a priority because otherwise they’re working on that on the evenings and weekends free of charge.