Brilliant lol.

I’m absolutely terrible with image editing software, but I use gimp on occasion.

It’s so few and far between that I want to kill myself everytime I need to do something in it and can’t remember anything at all.

You’re D:\ has been deleted. I’m very sorry.

Friends at uni handled that problem by disallowing landscape view instead of handling it hahah

😭

Such a tragic and common ‘solution’ because it doesn’t actually solve it, it just delays it until someones minimizes the app for 30 minutes and re opens it, or one of the many many other ways that also trigger it.

I’ve had some apps that I do lock to portrait, but I would disable that flag on debug builds, since rotating the phone was the easiest way to test for some of those bugs. I didn’t worry about a good looking UI since it’d be locked in portrait, I just used it to test for bugs.

Pretty sure there was one over 100k file at one of my old workplaces. It kept growing and growing and was the most critical file in the business. Like if that file suddenly vanished, the business would be done or shut down for at least a year, maybe two kinda thing. Re-certifying the output of that file would probably take 6 months alone.

It had a partner file, also very important, but not as, which was much smaller around 20k-25k

For anyone who knows and understands Android development, process death, and saved state…

The previous dev had no understanding of any of it, and had null checks with returns or bypassing important logic littered all over the app, everywhere.

I could only assume he didn’t understand how all these things were randomly null or why it was crashing all the time so he thought oh, i’ll just put a check in.

Well, you minimize that app for a little bit, reopen it, and every screen was fucked visually and unusable, or would outright crash. It was everywhere. This was before Google introduced things like view models which helped but even then for awhile weren’t a full solution to the problem.

It was many many months of just resolving these problems and rewriting it the correct way to not have these problems.

I had some absolutely beautiful RxJava2 chains in an app I worked on once. Can definitely be abused and done poorly though.

The first time something goes wrong with that complicated setup, it probably pays for a decade half a century or more of it’s fee.

I went to a tech event recently and got to chat with other other tech people, and it’s been awhile since I’ve been able to do that. We nerded out talking about caching. It was great.

And now the source code is part of copilot

Bus factor.

I’ve had recent problems with FedEx like this as well. Like 3 of the past 4 deliveries it says it’s going to deliver maybe a day early, then just fucking sits in the depo in the city ALL DAY while still saying it’s going to be delivered today, until it’s the end of the day and it switches to tomorrow.