2,781 karma · joined February 21, 2019
That's like 90% of the people I know outside of computer/engineering circle. Most of people probably have never opened a plaintext file in their life. They would have no idea what to do with a `.md` file.
In fact, some older engineers would not know what markdown is either, since it's only been around for two decades or so, but they can probably work with it anyway (the strength of plain text).
If that happens to me, I would kindly invite them to talk about it elsewhere and give me pass, because the fact that you guys are still debating it, means that it's not a decided thing, and you can't prosecute me with a law that hasn't passed yet. Once it's actually settled, I'll be happy to go back and refactor it, but it is illogical to make it a blocker in the present.
It also sounds like something is wrong with the on-boarding process. The first PR should not be of such a nature that would invite loads of comments. It should be something that is functionally simple, and already has an agreed-upon design.
I mean, it seems to me that any script that tries to do something with git remote URL, should deal with any string that git thinks is a valid remote URL. `ssh-host-name:owner/repo` is not exactly an edge case.
[includeIf "hasconfig:remote.*.url:gh-work:**/**"]
path = ~/.gitconfig.d/gh-work.inc
So, any git repo cloned with the ssh identity defined under `gh-work` will take on the config of `gh-work.inc`, which includes the git identity, and also the same signing key as in the ssh config.Essentially, the name `gh-work` becomes the distinguishing element in both my ssh identity and my git identity, and I find this easier to think about.
Automatic transliteration seems to be very dangerous (wrong name on bank accounts, for instance), and not always feasible (some unicode characters have more than one way of being transliterated).
Should we apologize to the user, and just ask the user twice, once correctly, and once for the bad computer systems? This seems to be the only approach that both respects their spelling, and at the same time not creating potential conflict with other systems.
Large open source projects can survive, but I'd imagine it will lean much more towards being developed mainly singular organizations. Without the internet, we don't just lose contributors, but also a lot of testers. The feedback loop will probably shrink, such that the software is mainly based on the need of the organization itself, and the perhaps a selected few collaborators who are very involved.
[^1]: https://github.com/PowerSnail/PowerSnail.github.io/blob/mast...
The reason I think this is worth saying, is that sometimes, to break the vicious cycle of [stress -> sleep-deprivation -> more stress -> ...], you need to shift the focus to tackle the real life problem first, and don't beat yourself up for not being a good sleeper. Trying and failing to develop sleep hygiene can pile on the frustration and worsen the vicious cycle.
For example, searching for recipes sometimes shows me Political News, and sometimes the news is even in a different country, and in a language that I don't speak.
Sometimes I also get a few results that are not just irrelevant, but intentionally made to have a visually repulsive thumbnail, like a zoomed-in shot of some skin pathology, which is something that I never search for or click upon. No idea what is happening there.
It was mostly a prank on the music industry, but nonetheless, mimicry of style was involved, and was enough to fool many people for years.
But health-wise, yeah, it would not be a good idea to eat out often. High blood pressure is a very, very salient health problem, on par with obesity in the public consciousness.
This is different from eating one really salty thing, like smoke salmon, where the saltiness is very pronounced. When salt is evenly distributed in every dish and meal, it's a lot less salient that you've consumed too much of it. It's a common experience when eating out, to not feel like I have had too much salt during the meal, but be very thirsty afterwards. (It's also why I dislike eating out back home, but sometimes it's inevitable)
I find myself living in the same town in years without finding a single restaurant that I can call "truly exceptional". They range from "I'd rather eat cup noodle", to "the food is worth the money". I don't know if I'm just unlucky, or if I lack some sort of culinary detective skill.
Hope it works out for them, though. It's a good product.
I'm not a lawyer, but I'm quite skeptical of the outcome. Is it really going to produce a valid GPLv3 licensed client? To me, it seems like the whole thing is just going to be a combined proprietary + GPLv3 license, which will contradict itself.
But again, I'm not a lawyer, so my understanding of this might be way off.
Anyway, my point is that, I can't see how to go from "I observed something with small probability happening to me" to the conclusion that "MWI is correct". There is no logical connection between the two statements as far as I can discern.
Obviously, during the first read, my understanding of those concepts would be full of holes. And I plug them as I continue reading the API references and later when I start to try it hands-on.
I really need the "core concept" first, before diving into examples, (unless the core concept is extremely simple).
Many tutorials are like hand-holding Lego building. Here's your Lego pieces, watch me and follow me in building this toy project, and you'll know how to Lego at the end of the day.
I just don't function very well in this model. I want to know how and why decisions are made. I want to see things from the author's perspective. I want to know how the Lego pieces each feels like, and how they connect to each other, and how you arrive at certain designs in a certain way. Trying to follow tutorials before at least some high-level, conceptual discussion, feels to me like I'm trying to reverse-engineer something that I shouldn't need to.
Most of the time if I'm approaching a new library or framework, I read read the introduction texts, and skip the "Getting started" code samples. Usually, there's going to be some sort of "Advanced" section where a lot more talking and discussing of concepts happens, and that's what I'd like to dive into first. I'll go for the API references next, try to grasp what the important interfaces look like, and finally I'll get back to the basic code samples in the beginning of the tutorial.