Sw: *creates feed algorithm*

@helenS Stop telling everyone how I implement "features" for my customers 😬

@Elessar I probably know what you mean 😏
Another good idea is to include an unnecessary loop in the program, which slows everything down, and to reduce the number of cycles in an upgrade. "Hey your program has become so much faster now! The upgrade was well worth the price!"

@helenS "Optimisations and bug fixes" 😌

@helenS

Just found this 😌

@Elessar Nice! 👍
I would not use a system call though. Just a loop where I would decrease j_max with each upgrade.

@helenS With these days hardware(*) the overhead is basically nonexistent. Let's say that a sleep() call would be more suspicious, your approach shows a higher CPU load on the task manager so the user may have the impression the program is actually doing something 😌

(*) Unless you're targeting embedded devices, and stuff that isn't particularly powerful

@Elessar Yes, a system call is suspicious and that's why I would avoid that. It's much better to malloc and free a huge amount of memory in a loop. You can also swap the content of two memory blocks back and forth j times before deleting the memory.

@helenS Your customers can potentially identify a system call? 😯 Over here they can't even tell you on the phone which operating system they're using, I legit have to ask them to email me a photo of their screen 😅

@Elessar Me: What's on your screen now please?
Customer: a cup of coffee.

@helenS Me: click on the file and hit "Del" on the keyboard. Now you can empty the bin
Customer: *goes away from the phone to empty the bin under the desk*

(From a real story 😬😬)