JFL I give up on performance coding (Android)

[AsiaCel]

Yes, I'm a slopcoder, yes I use AI code. Yes I used to value consistent code styling.

For non-codecels, a listener is a piece of code that fires when something changes. For example: a doorbell code that fires every time the door opens.

On one Android app involving drones, I handle more than 30+ listeners for logging and other purposes, some listeners have very similar purposes but subtle differences, while others are only needed for niche situations.

I will you one concise example; to be honest this isn't the best example, because speed is a variable I need 90% of the times; there are variables I only need for specific scenarios, like monitoring the temperature/camera status.

(this is AI generated code so I don't share my IRL work code)

I found out that one-time get values work horribly especially in looping functions (the delay of result of callback may be slower than loop itself)

public void getDroneSpeed() {
// Create a key for velocity
DJIKey velocityKey = FlightControllerKey.create(FlightControllerKey.VELOCITY);

KeyManager.getInstance().getValue(velocityKey, new GetCallback() {
@Override
public void onSuccess(Object value) {
if (value instanceof Velocity3D) {
Velocity3D velocity = (Velocity3D) value;
double vx = velocity.getX(); // forward/backward speed (m/s)
double vy = velocity.getY(); // left/right speed (m/s)
double vz = velocity.getZ(); // up/down speed (m/s)

double horizontalSpeed = Math.sqrt(vx * vx + vy * vy);
double totalSpeed = Math.sqrt(vx * vx + vy * vy + vz * vz);

System.out.println("Drone Speed: " + totalSpeed + " m/s");
}
}

@Override
public void onFailure(DJIError error) {
System.out.println("Failed to get velocity: " + error.getDescription());
}
});

There is another way: listen for the speed continiously (the optimal way is to add this code only when you need it and remove it when you don't)

KeyManager.getInstance().listen(velocityKey, new KeyListener() {
@Override
public void onValueChange(Object oldValue, Object newValue) {
if (newValue instanceof Velocity3D) {
Velocity3D velocity = (Velocity3D) newValue;
double vx = velocity.getX();
double vy = velocity.getY();
double vz = velocity.getZ();

double totalSpeed = Math.sqrt(vx * vx + vy * vy + vz * vz);
System.out.println("Updated Drone Speed: " + totalSpeed + " m/s");
}
}
});

But because the complicatedness gets on my nerves, I just rig the listeners to constantly update the variables in all situations. I hook these listeners to my Application layer, so no need for cleansing them between activities (think them in pages). Not neat, and probably inefficient, but I don't care. Just download more RAM.

private double vx;
private double vy;
private double vz;

KeyManager.getInstance().listen(velocityKey, new KeyListener() {
@Override
public void onValueChange(Object oldValue, Object newValue) {
if (newValue instanceof Velocity3D) {
Velocity3D velocity = (Velocity3D) newValue;
vx = velocity.getX();
vy = velocity.getY();
vz = velocity.getZ();
}
}
});

Managing all this shit is impossible, optimizations make it 80% harder to read for 5% performance gain (in the era of modern CPUs). I don't care anymore; management is throwing me around different apps/domains while being overly ambitious with the features/deadlines. If code quality suffers, so be it.

(I manage unreal 5, 2x drone apps, command line apps, auth app, and more other apps that I get tasked to work on)

Just realized I have so many apps to maintain

In my company, I created some apps for it specifically, some are meh, some are critical, some can downright kill a person. I maintain all sorts of apps, and add features if I'm asked to. It's fatiguing. I personally wish I could return to the day of specializing in Java spring. I'm only in my...

incels.is

Especially when I have heard of a developer colleague telling that he had been cursed at and screamed at by a customer, in person, when the server went down which was nobody's fault (Pretty nice when you have psycho customers, no wonder some colleagues get so upset at fuckups when they have to answer the phone)

I in fact, got pushed to make a feature to "fly around buildings" in ALL BUILDINGS (actually requested; no joke) in the world safety by the customers! I shut him up by referencing Africa's lack of quality building data (lol). Have bro heard of radar clutters? Yeah you're not doing it safety with cameras in urban environment.


More if you're interested :

The "ideal" design pattern is one time get i.e. when you actually need it.

My flight logger logs at about 0.1s; due to the huge amount of listeners I have, I actually find that I'm running the callbacks after the loop is completed and the function runs again.

Perhaps the correct course of action is to just update regardlessly.

The thing is, there are variables like isTakingPic that I don't really need to know whether the value has been changed until I'm on an autopilot (this is useful so if a pic is currently being taken, I don't risk double taking photo which doesn't work)

Instead of adding the isTakingPic listener during a mission, I add it at the beginning when you launch the app; I can just pack all these listeners into the "real time listeners" in the same place, instead of adding and removing them depending on mission status.

The ease of read and maintainability makes this worth it. I'm the sole person working on the two drone apps and I get called every time something goes wrong.

 

[Sex-Starved Beast]

Dude I don't understand anything, the most I did was porn games with GDScript

 

[AsiaCel]

Dude I don't understand anything, the most I did was porn games with GDScript

I'll explain this in real world example.

You want a door with a doorbell that rings every time someone opens.

However, if no one is at home, there is no point, because the doorbell consumes energy (even if very little)

But the complexity of making the doorbell detecting people at home (doppler radars, lasers, cameras etc) makes it unworthy and harder to fix.

 

[wereq]

There is another way: listen for the speed continiously (the optimal way is to add this code only when you need it and remove it when you don't)

Isn't this the right way? I mean, listeners should be listening continuously for updates for responsiveness. What design pattern is the ideal best practice here?

 

[AsiaCel]

Isn't this the right way? I mean, listeners should be listening continuously for updates for responsiveness. What design pattern is the ideal best practice here?

The "ideal" design pattern is one time get i.e. when you actually need it.

My flight logger logs at about 0.1s; due to the huge amount of listeners I have, I actually find that I'm running the callbacks after the loop is completed and the function runs again.

Perhaps the correct course of action is to just update regardlessly.

The thing is, there are variables like isTakingPic that I don't really need to know whether the value has been changed until I'm on an autopilot (this is useful so if a pic is currently being taken, I don't risk double taking photo which doesn't work)

Instead of adding the isTakingPic listener during a mission, I add it at the beginning when you launch the app; I can just pack all these listeners into the "real time listeners" in the same place, instead of adding and removing them depending on mission status.

Sounds complicated? Yup.

 

[wereq]

The "ideal" design pattern is one time get i.e. when you actually need it.

My flight logger logs at about 0.1s; due to the huge amount of listeners I have, I actually find that I'm running the callbacks after the loop is completed and the function runs again.

Perhaps the correct course of action is to just update regardlessly.

The thing is, there are variables like isTakingPic that I don't really need to know whether the value has been changed until I'm on an autopilot (this is useful so if a pic is currently being taken, I don't risk double taking photo which doesn't work)

Instead of adding the isTakingPic listener during a mission, I add it at the beginning when you launch the app; I can just pack all these listeners into the "real time listeners" in the same place, instead of adding and removing them depending on mission status.

Sounds complicated? Yup.

Its a little bit brute force but not too much.

 

[AsiaCel]

Its a little bit brute force but not too much.

The ease of read and maintainability makes this worth it. I'm the sole person working on the two drone apps and I get called every time something goes wrong.

 

[wereq]

The ease of read and maintainability makes this worth it.

 

[AsiaCel]

The best part is that they forced the pilots to use my shitty app or the pilots will have their missions disqualified. They put lots of stakes on the app, calling it most impressive app (in some aspects; telling it would doxx me).

The app description straight up calls itself super accurate, professional, approved by multiple certificates, industrial standards blah blah blah (paraphrased to prevent doxx)

I have never tested it on anywhere more than the shipyard/mountain LOL. Certainly not certificated (kek)

I repeatedly told my pilot-tester colleague to have devs use Litchi/DJI fly in case my app crashes (my app works ok on simple testing places but had issues in new areas)

 

[wereq]

The best part is that they forced the pilots to use my shitty app or the pilots will have their missions disqualified. They put lots of stakes on the app, calling it most impressive app (in some aspects; telling it would doxx me).

I repeatedly told my pilot-tester colleague to have devs use Litchi/DJI fly in case my app crashes (my app works ok on simple testing places but had issues in new areas)

 

[RandomGuy]

Dur goiyms don’t know about .

Claude vs ChatGPT vs Gemini: Why Anthropic’s AI Outcodes the Rest?​

 

[NEB.feelsdevil]

This is good for the incel community, it is good for me to see talented smart incels, it proves we have a SOUL, we have skills, desires. Our SOULS need acknowledgement.

 

[The Death Devil]

The best part is that they forced the pilots to use my shitty app or the pilots will have their missions disqualified. They put lots of stakes on the app, calling it most impressive app (in some aspects; telling it would doxx me).

The app description straight up calls itself super accurate, professional, approved by multiple certificates, industrial standards blah blah blah (paraphrased to prevent doxx)

I have never tested it on anywhere more than the shipyard/mountain LOL. Certainly not certificated (kek)

I repeatedly told my pilot-tester colleague to have devs use Litchi/DJI fly in case my app crashes (my app works ok on simple testing places but had issues in new areas)

That's honestly kind of terrifying. Don't you live in China? I wonder if every country does stuff like this...

 

[TooSomething]

I unironically plan on buying the Commodore 64 Ultimate and use the guide that comes with the computer to learn to code in C.

That is all I can say about coding.

I used to code in Java, a freaking long time ago.

It was fun, while it lasted.