praash

I really enjoyed spending a bit of my morning with these two implementations of the concept.

I prefer your idea of treating the question as a proper puzzle with a 1-submission limit. The "calculator" UI took a whole 2 minutes to understand initially, but I really liked seeing the chain instead of having to mush all the factors in my head.

It's really nice to see the correct answer broken down to get a feel about the real numbers!

The current question's answer seems to contain big errors in magnitude in its factors:

"How many kilograms of skin does a human shed in their lifetime?"

    Skin cells shed per day: 5e8 / day
    Mass of one skin cell: 3e-6 g
    Years in a lifetime: 80 yr
    Grams to kilograms conversion: 1 kg / 1000 g

The final "correct" result is displayed as 44 kg, but these values result in 44,000 kg. It's also odd to show a conversion factor for kg/g, but not day/year.

The first two factors correspond to shedding 1.5 kg/day, which is definitely unrealistic!

> Hence I'm pro compression culture

I think the problem is that this compression culture is lossy and fragmented.

Summaries serve a purpose similar to thumbnails in an image gallery UI - the full picture is always available behind a click.

Imagine if you could only see them as 128x128 JPEGs at 50% quality - after they've been reposted with "deep fried meme" filters a few times. No links to the source, and the next bite-sized truncation pushed right after. Later someone reposts them upscaled to 8K.

This is exactly what I feel is happening with the written word.

> Say the most important things at the top that cover your topic entirely and then go into further depth.

A powerful trick in all forms and contexts of communication.

> -- eyes darting frantically across screens like a rat in a maze searching for the cheese of instant gratification.

I have lost the ability to search for information online when I'm not solving a specific technical problem. My eyes jump over paragraphs as if performing a binary search to find the sections I'm interested in - obviously a bad approach for less orderly documents.

Search Engine Optimized spam keeps me encouraged to habitually skip large chunks of text.

HN is mostly a safe harbor of high quality content, but I still have a bad habit of completely skipping most HN headlines, or jumping to read the comments before even considering to read the article. That's basically letting the crowd digest and summarize posts for me.

This was a satisfying read and worth the short time to patiently digest it.

The iffiest part is sharing a MS Office license key.

The post fails to mention any overview on what kinds of "debloating" the scripts are supposed to do.

My observation is that HN intentionally downranks highly commented threads. I used to think of it as unfair, but now it truly makes sense, considering:

- Posts with high comment-to-vote ratio often have political, scandalous or other kinds of heated themes

- Highly popular/engaging posts already act as self-amplifying snowballs

- High-volume discussion triggered by emotions is hard to navigate, is repetitive, and attracts the dumbest trolls even in HN

- The truly important topics tend to become visible anyway

> someone who spends all their time in Arizona would quickly get used to the fact that they now eat dinner at 12:00 UTC instead of 7pm. But it would make traveling more tedious: you'd have to re-learn the mapping every new place you went.

Following local times won't spare you from having to learn local culture anyway, such as Spanish dinner times ranging around 21-23.

You can make WoL work with a forwarded UDP port on your router. Most WoL tools also tolerate the use of a domain instead of an IP. Obviously this can't shut your server down.

Downside: unencrypted magic packets sent over the network could be captured and maliciously repeated for your annoyance.

No - the point is to quickly detect random websites that simply duplicate known favicons! Matching hashes can only occur in these cases:

- the site is a careless impostor

- the site is the real deal

- a hash collision

Don't check for Moiré patterns until you're looking at an image file at 1:1 pixel size. Moiré patterns can appear on top of a perfect photo whenever the image is naively downscaled without gamma correction. This also happens within the camera display - any Moiré visible while shooting does not necessarily need to be corrected.

There's nothing wrong with choosing to blur out the grill pattern - the photos probably represent the original display signal more accurately.

I love giving examples and context in a PR description. Squash-merged PRs can become cumbersome snowballs, but the final commit message should elaborate in proportion.

Maybe the flute's pitch could be decoded back into the required fingering combination. This way the player could treat each hole as an individual button. The actual notes might not all sound musical (or be properly distinguishable).

Good thoughts! I think there is much more nuance as I disagree with some of your points:

> I believe that impostor syndrome is a lack of overconfidence in one's abilities - that implies that you have the the ability to assess competence --

I think that competence in an ability is not perfectly synchronized with ability-assessment-competence.

I think ability-assessment-incompetence can result in both under- and overconfidence, before accounting for a self-esteem bias. Being underconfident is also an incorrect self-assessment, which doesn't imply ability-assessment-competence.

> If you lacked the ability to assess competence in yourself, then you likely would not have impostor syndrome.

Here I disagree the most. I think impostor syndrome can be the result of ability-assessment-incompetence, somewhat detached from their true competence in the actual abilities involved.

This would be required for a true DAC, but not here:

- A physical speaker already acts as a filter due to inertia

- The PWM frequency and its square harmonics sit far beyond the human hearing range

After all these years I still feel Excel cannot handle a fully compliant datetime string.

ISO 8601, ironically, also defined acceptable a (now deprecated) set of truncated date formats such as YY-MM-DD and YYMMDD.

A true observation, especially since many European countries (or just some citizens) wish to get rid of DST.

However, ±1 hour is not much of an error when talking about a time delay of at least a year.

This is the only sane policy. Timezone conversion must be delayed to the very last moment before displaying time to users.

If I needed to define a daily alarm in a local wall clock time, I'd happily deal with a zoneless dateless hour-minute tuple and determine the alarm time by combining a date and a time using a timezone. Right after I'd convert that and handle the rest in UTC.

I have used patch-adding almost exclusively for a few years. It really helps me stay aware of my workspace and avoid committing temporary tweaks. I can also keep semi-permanent personal tweaks uncommitted in my workspace and get constant reminders if I still have an inline debugging flag activated.

It's unlikely to remember this feature's existence and benefit from it without habitual usage.

Most (if not all) digital keyboards also support receiving MIDI which will be played by the piano's own sound engine!

This will probably require assigning the received MIDI to a different channel than 0 to allow simultaneous play without conflicting note offs and sustains.

The fact that weighted digital pianos are cheaper than equivalent plain MIDI keyboards is my pet peeve.

Wow. This site is stunning in both the variety and the number of articles.

Thanks for sharing!

I remember watching a surgeon-narrated YouTube video demonstrating eye removal, and didn't feel any stomach-turning horror from seeing the gore. I felt it when the narrator told to check something "to ensure the correct eye is being enucleated".

Is there any chance of the account being hijacked? It would make this act of self-destruction even more bizarre due to the massive opportunity for abuse, though.

That guy is literally providing technical support in GH issues. No way. People complain about logging into stolen accounts and the developer is happy to help. There's a pinned page on how to disinfect your system, accompanied with a vibe of "should've been more careful, idiot!"

Seeing this happy-OSS-community praise from someone providing a turn-key malware solution for even the most technologically incompetent jerks is just harrowing.

The major media outlets have clearly missed the chance to just call it x-twitter!

> 1. Always type in URLs manually

This is the time for typosquatters to strike :(

I'm also irritated by how the SI prefixes get abused here - saying TEN THOUSAND MILLIAMPERE-HOURS is just stupid when people rarely need to compare that to sub-Ah capacities. Why shouldn't we go further and start using nAh? Storage capacity seems to deserve proper prefixes instead of madness like 100 000 000 kB.

That's just one part of the issue - even after forcefully dropping Linux's caches, WSL has been unable to reclaim the memory back reliably. There has been a recent update that claims to finally fix this.

You might find this package helpful: https://github.com/arkane-systems/wsl-drop-cache

It's as if people have work to do and can only spend their paid time in OSS fixing problems blocking their work.

Having done all the debugging work and figuring out a way to fix it, it's a bit nasty of the maintainer to make a "better version" of it and rudely tell them to be "more useful. Basically it's the same as accepting the contribution and refactoring it afterwards.

If the author "only wanted Linux street creds", without the context of a problem, they could have searched for an easy issue to fix and contribute on that. No, wait, now you'd consider that an act of selfless OSS contribution, fixing random problems not related to you!