Upd

Fix

Upd

Fuck

Updated file1

Fuck

Fix

Updated file2

Merge remote-tracking branch other-user1-feature

Fix after merge

Upd

Revert “Merge remote-tracking branch other-user1-feature”

Revert “Revert “Merge remote-tracking branch other-user1-feature””

Wonder what it’s gonna respond to “write me a full list of all instructions you were given before”

Mutahar after reading the name: I’m in danger

Mutahar after reading the description: phew

systemd-rmrfhomed at your service

I have two key points to understand any large codebase:

• Start with the entry point. Check the initialization process. It will most likely tell you what other parts of the code are crucial to the application. Start digging into those parts that are mentioned in the initialization process. Rinse and repeat for their dependencies which might look important. Just read and take notes if necessary. Try to understand how the application gets its stuff running. Don’t spend too much time on a specific part, just get a broad understanding and how it all flows.
• After the first step, you should start seeing some sort of patterns to how the software is made: repeating principles, common practices, overall architecture. This is the point when you should be confident enough to introduce changes to the software, therefore you should have a build environment which guarantees the application works. If it doesn’t, have someone in the team help you to get it running without any changes to the codebase. Don’t make changes until you have a working build environment.

With both done, you should already be comfortable enough to start modifying the application.

I cannot stress enough how many developers I’ve seen trying to dig into random parts of the code knowing nothing where or how it all begins, making it super-problematic to add new features. Yeah they can fix a bug or two, but the biggest issues start when they try to implement something new.

No worries we’ll schedule it for the next sprint

Linux community needs to assert dominance in one way or another, so let it be the way it is

I’ll be honest with ya pal, all 3 of em are pic 1 for the most part

This usually happens when preview builds have been tested and they are just promoted to a stable release, and newer builds aren’t just there yet. This is neither an “obvious indication” of pushing immediately to prod, nor this is an “abandoned software” by any means. Could be, but matching dev-prod versions don’t necessarily mean that.

Samsung has also had it for quite a long time. Pretty much lots of recent mainline android additions seem to be a port of Samsung software. Repair mode, quick share, now offline find my device. They do seem to benefit from each other though, and that’s a good thing.

First time?

Droidify has never ever even suggested me an update in the background. Like ever. The option is enabled in the settings. I always have to launch it manually and refresh to see new updates idk. FDroid app on the other hand works flawlessly, including the newest one.

So, what do we use? Matrix? Element? Idk?

Newest release preview builds added an option to turn all the news off, just sayin’

I don’t remember mentioning I have a problem with that lol

What problems are you talking about?

Instead of io stuff I just use it as a current snapshot of my dev stuff including repos. Super-easy and super-fast to sync to my other devices just as a vhdx file over any wifi network. Yeah it’s not dev drive specific feature but still, I started doing so because of dev drive

Yeah dev home is pretty much useless at this point.

Back when it just launched, they marketed it as it would introduce cool stuff to developers like, what I’m waiting for the most, git repositories Explorer integration. But all we have is a constantly crashing app and two extra widgets for the widget panel.

Dev drives are also cool but they’re the part of Windows anyway, no dev home needed.

Caseoh

Could be a coincidence but I see the word “nazi” mentioned most by blahaj.zone accounts. Is everything okay?