659 karma · joined September 11, 2020
Edit: I like the post, but it didn't need to be padded with fluff.
I try a lot of obvious things when debugging to ascertain the truth. Like, does undoing my entire change fix the bug?
It taught how to memorize stuff: spaced repetition and semantic encoding. Spaced repetition is reviewing the thing at increasingly spaced intervals of time. Semantic encoding is coming up with connections to the idea. The wilder the better as that tends to be memorable.
The class taught some strategies for creativity such as use of analogies and trying to combine disparate ideas.
The class also taught cognitive biased, like loss aversion.
This class was life changing. It was also easy because the teacher applied the best practices she was teaching.
I would say something like that class is the basis for teaching people how to think.
Avoid time wasting nit-picks on PRs.
Consistent formatting may be easier to quickly read.
Why not:
Avoid taking a dependency.
Avoid "fix formatting" commits (or the complexity of having a system auto-apply formatting).
Formatters don't always make the most readable code. Sometimes non-standard formatting actually communicates more clearly.
Consider airline miles. Each time I purchase a ticket, instead of choosing the best deal (fair competition), I am incentivized to choose an airline I have chosen in the past so as not to fragment my points across several accounts. And of course, these "rewards" are all a price passed on to the consumer.
This is good for use cases where you want to assert that an organization says something about you (e.g., you have a degree).
It is not good for use cases where you want to assert that you say something (e.g., I voted for Blah, or I authorized this transfer).
I wonder where this line of thinking will lead. Will content licensors start demanding logs from streaming services and go after vpn users directly?
I love this. I wish more software was built with limited scope. Not every application needs to grow larger and change forever.