495 karma · joined October 17, 2016
Maybe you're looking for something like "Natural Perspective"?
9 is 1 digit, takes 9 steps.
99 is 2 digits, takes 99 steps.
999 is 3 digits, takes 999 steps.
An input d decimal digits long takes O(10^d) steps.
The runtime is exponential in the "size of the input", because the size of the input is usually taken to be the length of the binary or decimal representation of the number rather than the magnitude of the number.
From the original article https://mega-awry.io/ (emphasis mine):
> Since the server code is not published, we cannot implement a Proof-of-Concept (PoC) in which the adversary actually controls MEGA. Instead, we implemented a MitM attack by installing a bogus TLS root certificate on the victim.
> ...
> The log in attempt fails, which is only a limitation of the MitM setting. A malicious cloud provider can perform this attack without the user noticing.
Easier to digest I think to break TFA into two conceptual pieces
1. the representational complexities of roman numerals (remember not to use prefix notation; what does each character mean)
2. the actual meat of the multiplication algorithm (russian peasant method)
Maybe a nice middle ground would be for more language runtimes to have an equivalent to perl's `-p` flag. https://perldoc.perl.org/perlrun#-p
This flag is so convenient that I mostly use `perl -pe` instead of `sed` for regex search-and-replace.
Reminds me of this Tadashi video: [How do fish swim so quickly?] https://www.youtube.com/watch?v=wYDh5d9pfu8
Tadashi shows that fish turn drag into thrust by swapping the positions of the vortices they shed. Low effort, high output.
TFA takes this one step further--fish bodies are shaped to effortlessly harvest thrust from drag. No effort, free energy!
I think there's a typo here. This should go in the "Pros" section
As to the source of my confusion... I think I was skimming and about to turn back to work and not thinking too deeply.
At the time I wrote that edit I had just gotten as far as "pagerank values links whereas marketrank values upvotes" (heavily paraphrased interpretation of 2.1 here: https://dkb.io/post/market-rank). My reaction was "oh, maybe that means links are bad... that's an interesting perspective but I don't have time to digest it right this moment. I'll put a pin in it and return to this article later to better understand, and hey I should add an edit to my comment to signal reading comprehension."
That last thought seems pretty ironic in retrospect.
My use case: often times blogs will respond to other blogs, linking to the original post in the process. The nature of linking means it's very easy to follow threads backwards in time, but given the original post it's often hard to discover the responses and ongoing conversation to follow things downstream. I'd like that downstream browsing to be easier.
My hope would be that such a tool could unlock higher-quality discourse. As a reader, this would let me hijack my natural tendency to follow comment threads, and redirect that attention towards slower-paced, more nuanced, more focused writing.
Edit: hmmm... though looking further, maybe this goes against your MarketRank philosophy.
0. Given a prospective rental house. (And therefore a known set of rooms and a known total rent)
1. Each person "bids" by pricing every room in the house. Goal: each person should be looking for "break-even" pricing. Try to price such that all the rooms feel "equally good" at your given prices.
2. Just one restriction on the pricing: each bidder's room-prices must sum to the house's monthly rent.
3. Reveal all bids.
4. Choose the room-assignment that yields the highest total price. Because of the restriction in [2], we're guaranteed a surplus over the true total rent. (Unless everyone somehow put in identical bids)
5. Split the surplus evenly. Everyone gets a room at the price they bid for that room, minus 1/nth of the surplus. Effectively, everyone gets an identical surprise discount.
We lived together for over 10 years, through 5 different rentals. We split up when it came time to start families and buy houses.
It bugs me further that browsers don't let me decide whether the top bars get shown. Sometimes it'd be really nice to toggle off all the browser chrome and just have a true full-window view of a page (Full-window, not full-screen: in particular if I'm opening multiple pages and tiling them vertically, all that browser chrome starts taking up a lot of space really quickly).
Dear browsers: this is hopelessly backwards! Websites should never be allowed control my browserchrome. I should always be in control my browserchrome. Given that this is already configurable per-window, put that switch solidly in my hands!
Their first night, a fire starts in the house. The engineer wakes up, sees it, douses it in buckets of water, puts it out, and goes to sleep.
The second night, another fire starts. This time, the physicist wakes up, sees it, calculates exactly how much water to use to put out the fire, pours exactly that much water on the fire (plus or minus experimental margin of error), puts it out, and goes to sleep.
The third night they decide to search for fires before bed.
The engineer does a quick sweep of the house, convinces themself there are no fires, and goes to sleep.
The physicist searches a while longer, convinces themself there are no fires, goes to sleep.
The mathematician searches and searches, but can't prove there are no fires, and so can't go to sleep. After some thought, they set their own fire and go to sleep, thus reducing it to an already solved problem!
I respect your long experience moderating HN, so asking mostly with the intent enrich my own intuition. Not a rhetorical question.
looks like someone has already implemented this: https://www.reddit.com/r/emacs/comments/orgzoc/org_roam_and_...
I'm curious to try it but I'm not well-enough versed with nyxt yet
Anyone else get immediately sidetracked by how metal the name "Carbon P. Dubbs" is? (and how unexpectedly apropos it is to chemical engineering?)
https://digging-history.com/2016/01/18/tombstone-tuesday-car...
Apparently his full name was "Carbon Petroleum Dubbs" and the relation to chemical engineering isn't really coincidental.
- Kartik argues for better mutual understanding and additional communication
- Team Topologies states you should match system boundaries to team boundaries, specifically when cognitive and/or communications load have grown unmanageable due to team size and/or software complexity
On the surface, Kartik is arguing against abstractions and Team Topologies is arguing for abstractions, but both stances feel valid to me. It feels like there's a spectrum of tradeoffs here. Is this essentially an analogue to the tradeoffs of monolith vs services?
- For small teams, by all means keep abstractions low and communication high--monolithic systems and less division of labor is ideal and your team will gel better for it. Your team is probably not large enough to warrant either services or division of labor, so stick with the monolith.
- As an organization scales, you end up with an n^2 communication edges problem, and at this point division of labor is necessary to limit the cognitive and communications loads.
EDIT: on closer examination, not sufficient... fails to turn up expected backlinks in many cases.
I think it's neat they exist, but they don't really live up to the "curated" promise in my mind. Mostly they seem to be a grab bag of everything under a topic, and it's left to the reader to sort through. As such they've never come to mind when I'm actually researching anything.
1. Good: Nitrites produce that pink color and particular salty flavor.
2. Good: Nitrites suppress bacteria growth.
3. Bad but outdated? In large enough quantities, nitrites will kill you. I seem to recall this being the main issue, but a quick google now mostly turns up the next point:
4. Bad: Nitrites also produce nitrosamines, which may be carcinogenic [citation needed].
5. Mitigation?: According to wikipedia, "The production of carcinogenic nitrosamines may be inhibited by the use of the antioxidants vitamin C and the alpha-tocopherol form of vitamin E during curing."
People are worried about some combination of [3] and [4], and so some meat producers use variations of "(dehydrated|fermented|cultured) celery (juice|extract|salt)" in the ingredients lists instead of directly listing nitrites as chemical names.
The counterreaction is to be suspicious of odd celery ingredients.
Since nitrites are essentially synonymous with cured meat though (must be used to prevent spoilage, no available substitute as far as I know, but also no significant other usages as far as I know), I'm not sure you actually need to go to the ingredients list here. Rather than memorizing synonyms for nitrites, I'd say a better rule of thumb is probably:
worried about nitrites ? stop eating cured meats : don't worry about it
EDIT: I just thought of another place they exist: celery salt. So, if you're worried about cured meats, also avoid the celery salt.
Did this work? Is Kevin still getting enough sleep nowadays?