1,079 karma · joined February 16, 2012
>In general, no single section has both write and execute permissions as this could compromise the security of the system.
After you read something once you don't strictly know it. However if you run into a related problem down the road, you have a good chance that you can remember enough of what you read once to put a Google query together and find the original article.
After thinking about it a little more, what they probably mean is that while most programmers will forget most of what they read here (because they don't use it day-to-day) it is reliable information that will help shape their intuition about how memory works. That is probably what they mean about every programmer and this article.
Every programmer ought to read and test their intuition about how memory works against the content in this article. If they are surprised by something they read, they have the chance to adjust their intuition so that it is closer to the truth.
While you have a career or if you have a hobby, I suspect any new skill that you practiced would lead to similar mental simulation.
From a customer perspective, this practice feels very disingenuous. The 5.95 should be labeled as part of a delivery fee.
If somehow DoorDash was the first link a user visited after searching for "donut plant", they would need information to decide whether to visit the restaurant or to order online.
The transparent thing to do is to list the 5.95 markup as DoorDash-imposed. That way the user can easily see their choice
https://www.reddit.com/r/startrek/wiki/where_should_i_start
For DS9 in particular, this link was helpful for me:
https://www.reddit.com/r/DeepSpaceNine/comments/1fkijc/ive_m...
There are 3 episode lists in there and a user named Algernon_Asimov has a "Hmph!" comment with a link to detailed episode lists for TNG + DS9
For no discernable reason, I have never gotten into using voice commands for everything.
Can you tease out this distinction a bit more? It reads like you are saying, due to their nature, people learned how to use Unix service handlers, without a good understanding of how they were designed. It could also mean that people learned how Unix service handlers worked by using them, through trial and error, because the documentation was scattered and not entirely comprehensive.
: )
I commented because I didn't want the top comment to devolve into a Perl v. Python argument because I love both.
Looking at my comment now, it doesn't read as on topic.
Thank you for moderating. HN is my favorite place to read the news!
"You can fool all of the people some of the time, and some of the people all of the time, but you can't fool all of the people all of the time"