Could be a crypto key, or a randomly distributed 64-bit database row ID, or a memory offset in a stack dump of a 64 bit program

And then JSON doesn’t restrict numbers to any range or precision; and at least when I deal with JSON values, I feel the need to represent them as a BigDecimal or similar arbitrary precision type to ensure I am not losing information.

That’s because the nearest representable float to 0.99999999999999 is 1.0 - not because Python is handling rationals correctly.

This is a float imprecision issue that just happens to work out in this case.

It’s worth wondering why, if Python is OK with “/“ producing a result of a different type than its arguments, don’t they implement a ratio type. e.g. https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node18.html#SECTION00612000000000000000

How would you implement this in code?

JavaScript is truly a bizarre language - we don’t need to go as far as arbitrary-precision decimal, it does not even feature integers.

I have to wonder why it ever makes the cut as a backend language.

You have to explicitly check if the return value is an error and propagate it. You write the same boilerplate if (err) return err over and over again, which just litters your code.

That’s only true in crappy languages that have no concept of async workflows, monads, effects systems, etc.

Sad to see that an intentionally weak/limited language like Go is now the counterargument for good modeling of errors.

👌🏻

ż̸̬̪̾̔̏͝a̴̛̙͈̦̟͎̓͐͗͘͜l̴̙͈͙͍̓͒̆g̸̠͑͝ô̷̬̭͑̋͘ ̴̘̰͎̤̒̈́̅͐͜ǫ̵̻̭̯͎̒̍͘͠b̶̹̟͍͓̻̐͐́ŝ̸̭̦̰͘e̶̠̝͙̳̽̃̇̑͆r̴̜͇̼̯͈̈́͛̅̾͝v̶͉̲̥̈́̈́̓̽ę̸̡̧͇̊̓͂̑s̷̠̑̉̈́̂̂͠

You are seeing changes in the refractive index of air as a result of heat lowering the density of the air. As air comes in contact with the hot surface, it becomes heated and rises through otherwise cool air - The rising air causes eddies and vortexes that lead to light bending in weird ways as it passes through.

The shadows are much like the shadows on the bottom of a pool when there are waves on the surface. Incoming wavefront of light are distorted from planar and sent in different directions, some directions get less total light, some get more.

Yes, it is a huge pain, especially if you want to have round-trip interoperability with humans using markup. Wikipedia had a major challenge with this when they decided to add a rich text editor alongside wiki markup.

yeah, communities should have subject tag sets. I don’t care for anime or sports or video games - i should be able to turn off those tags. Not block 50 different game communities ad hoc

Surge suppressors do not drop extra voltage to ground. They selectively short out surges between whatever two conductors have a high potential between them.

No ground conductor means there cannot be a high potential between it and anything else!

They should make up 7% - 10% of all such representations, right? I think I have seen that many, but I mostly watch nerdy youtube stuff, where the presenter’s sexuality is either not mentioned or several instances of them undergoing a gender transition, which is noticeable.

It’s just that 20+ posts a day is kind of a lot. You’re dominating the feed.

Removed by mod

yeah they are selling “wireless home internet” hard now, can’t have people using their phone hotspot for that.

Can’t wait for consoles with the injectables pack-in

I know something that will clear those sinuses up!

Guys, he made the joke!

If your company is using story points to “measure” developers, they are completely misusing that concept, and it probably results in a low-teamwork environment (as you describe).

The purpose of story points is so a team can say “we’re not taking more than X work for the next two weeks. Make sure it’s the important stuff.” It is a way to communicate a limit to force prioritization by the product owner.

And, in fact, data shows that point estimation so poorly converges on reality that teams may as well assign everything a “1”. The key technique is to try to make stories the same size, and to reduce variability by having the team swarm/mob to unblock stuck work.

Who creates these tasks? They need to close the year old items, reevaluate the work and break it down into sub-5-day chunks. If there are so many unknowns that it’s impossible to do that, the team needs to brainstorm how to resolve them.