> The curse of dimensionality is not theoretical — it’s painfully practical. In high dimensions, naive distance metrics degrade quickly.
>
> Scaling and normalization are not optional details. They fundamentally shape the geometry of the space.
191 karma · joined December 26, 2017
> The curse of dimensionality is not theoretical — it’s painfully practical. In high dimensions, naive distance metrics degrade quickly.
>
> Scaling and normalization are not optional details. They fundamentally shape the geometry of the space.
I'm with the people who decided to ship this. The organization will need to fund more maintenance than they would if they waited, but that has real costs. And "keep your 1mm/revenue idea to yourself" doesn't sound like a healthy engineering culture either.
There have been a some novels and novel-length works written a chapter at a time in public. The Martian by Andy Weir, for example is probably the most commercially successful. Many works by qntm (https://qntm.org/fiction) that are popular in this community have been written that way too.
Because this post is here and not somewhere else. Strong network effects.
https://www.pbs.org/newshour/science/israel-trades-pfizer-va...
But is that really the right comparison? Lots of people just don't have the skills or time to build a specific applications. Without Excel, what would they do? There are some places where a 90% solution is worse than no solution at all (at least no solution is a forcing function for a "real" application), and in many ways Excel isn't the best expression of the _idea_ of an Excel-like, low-barrier-to-entry declarative programming environment with a built-in UI, but it's truly a wonderful tool. It makes a lot of automation possible for a lot of people.
Test prep companies have an incentive to overhype their services but research suggests the improvement isn't that much.
There's a Jacobin article making the case for the SAT that people following this debate might enjoy reading: https://www.jacobinmag.com/2018/03/sat-class-race-inequality...
Documentation is here for the curious: https://docs.python.org/3/library/functions.html#ord
https://www.haskell.org/tutorial/functions.html
In languages like Go, you'll write much more "composable" software by sticking to what the language gives you instead of trying to force this in.
Still if you really want to take the analogy further declaring technical bankruptcy could cause business bankruptcy (see Joel Spolsky). You probably want to refinance your debt and get onto a repayment plan (an incremental rewrite) instead.
Admittedly Python's facilities for doing that with some mutable state are pretty nice:
from itertools import islice
def fib():
a, b = 0, 1
while True:
yield a
a, b = b, a + b
list(islice(fib(), 10)) == [0, 1, 1, 2, 3, 5, 8, 13, 21, 34][1]: https://slatestarcodex.com/2015/07/22/freedom-on-the-central...
In fact, you could define a number of useful precondition functions in a single module and use them throughout a project. A couple of higher-order functions could make the post's examples safer and nicer-looking too. For example:
@precondition(starts_with('The year is '))
where the starts_with precondition is: def starts_with(param):
def test(s):
return s.startswith(param)
return test