I’m subscribed to !programmer_humor and !programmerhumor and you often cross post to both of them at the same time. Could I ask you to use the build in cross-posting functionality in lemmy so it only shows up once in my list? Otherwise I’ll need to unsubscribe from one.
I humbly beseech your indulgence and extend my sincerest apologies for the inconvenience caused by the recurrent cross-posting of content on the esteemed platforms of !programmer_humor and !programmerhumor. I am acutely aware of the vexation such redundancy may cause, and it is with the utmost regret that I admit my failure to employ the built-in cross-posting functionality within the esteemed realm of lemmy, which would ensure the display of said content in your esteemed list but once.
Pray, permit me to express my profound remorse for any distress or disarray this predicament may have occasioned. I implore your benevolence in granting me the opportunity to rectify my missteps and adhere to your esteemed request for the exclusive manifestation of content on a singular occasion within your discerning domain.
Verily, should you deem it necessary to withdraw your subscription from either platform owing to this grievance, I shall ruefully accept your decision whilst bearing the burden of my own negligence. Nevertheless, I earnestly beseech your forbearance and entreat that you afford me the opportunity to make amends, so as to retain your valued patronage.
Please accept, dear Sir/Madam, the most sincere apologies of this humble servant and trust in my unwavering commitment to rectify this issue posthaste. Your considerate understanding and magnanimity in this matter would be esteemed beyond measure.
It’s really not that hard. Authentication is about proving the identity of the subject e.g. logging in using information only known / in possession by the subject (password, mfa etc). Authorization is about establishing what permissions that identity has in a given context. E.g. is this identity allowed to create/read/update/delete these resources. Authorization is typically done through roles (RBAC) or more granulary through attributes (ABAC).
If it results in death when the controller stops working, you have a serious issue with the system architecture and should work on that instead of trying to improve the controller.
I remember using them in my high school robotics club. And honestly, I think the controller was probably one of the least sketchy things about the sub. Lots of fields use game controllers to handle equipment since they’re well designed for that. There were many other things that were far worse.
Yep, I’ve seen reporting of Navy’s using them for controlling periscopes on submarines (now that most are drive by wire), or Air forces using them for piloting drones, as well as for teleoperated robotic thoracic surgeries.
The widespread user familiarity and benefits in transferable hand coordination skills with common gaming based HID economics is hard to refute. Although, I’m guessing the market for safety certified joysticks will uptick.
That wasn’t the dumb part of that submersible. Game controllers are actually really good at what they do. The dumb part is that it was built like an airplane.
Nevertheless, there is the one hidden advantage of this approach: You learn new things while trying to automate everything. Remember, that it is the journey that is important, not the destination ;)
I know this is a humor subreddit and this is a joke, but this problem wasted a huge week of mine since I was dealing with absurdly small numbers in my simulations. Use fsum from math library in Python to solve this people.
Yeah, this works especially well for currencies (effectively doing all calculations in cents/pennies), as you do need perfect precision throughout the calculations, but the final results gets rounded to two-digit-precision anyways.
quite a horrible hack, most modern languages have decimal type that handles floating rounding. And if not, you should just use rounding functions to two digits with currency.
Not sure what financing applications you develop. But what you suggest wouldn’t pass a code review in any financial-related project I saw.
Using integers for currency-related calculations and formatting the output is no dirty hack, it’s industry standard because floating-point arithmetic is, on contemporary hardware, never precise (can’t be, see en.wikipedia.org/wiki/IEEE_754 ) whereas integer arithmetic (or integers used to represent fixed-point arithmetic) always has the same level of precision across all the range it can represent. You typically don’t want to round the numbers you work with, you need to round the result ;-) .
The lesson here is that floating point numbers are not exact and that you should never do a straight comparison with them. Instead check to see if they are within some small tolerance of each other. In python that is done with math.isclose(0.1 + 0.2, 0.3).
Please don’t try to approximate. Use the decimal module to represent numbers and everything will work as expected and it has a ton of other features you didn’t know you needed.
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.