have you read up on the new rave of having all your public interfeces declared bassed on a CRUD setup, and move all implementation details in the private parts.
For example if you have a subscription functionality , instead of doing
def subscribe , you would do it like:
def create_subscriprion.
This in turn is advocated on the bases that it will improve readability and lessen confusion amongst programmers. What are your thoughts on that?
"ncreasing obesity played only a part in this deterioration of midlife self-assessed health, mental health, reported pain, and difficulties with ADLs. Respondents with body mass indices above 30 reported greater morbidity along all of these dimensions."
They managed to tie in morbid obesity with incresed (albeit self-assessed) mental health deterioration. Do they have a separate paper/source for that, I'm really curios to know
Going to come across as mean, but this post illustrates the difference between a sysadmin and a network engineer that specializes in things like this (and why you should not be using dumb unmanaged switches in an enterprise environment).
Remove the stuff about wireless repeaters and pallets of shampoo and this is a basic l2 loop that should have taken 10 minutes to track down.
Yes, as pointed out on many debugging stories: problems are easy to find if you look in the right place (hint: knowing where to look is the hard part). Unfortunately for the people living them, there are wireless repeaters and pallets of shampoo that make looking in the right place harder. You might as well have said that Waldo is easy to find if you remove all of the other people on the page.
As for it being "a basic L2 loop that should have taken 10 minutes to track down." If it were a "normal" L2 loop, and he could have taken 10 minutes tracking it down; sure. But when it only happens for ~2 minutes at a time, getting 10 minutes of actual tracking in is hard.
Sure, having managed switches would have made finding it easier. But most debugging stories have something that could have made them easier if done beforehand.
This was my thought as well. Then I started thinking about the huge amount of moderation effort to make sure that comment sections stay civil. From where I stand it seems like for most writers offering a comment section is a lot of work for a very small payoff.
If you think of it from the perspective of "building and maintaining a jail" yes, it is hard. You as the blog admin represent the warden, and as such are the enemy
But if you have the inmates police themselves (like the reddit community), problem solved.
"Solved" only in the sense that "the community" polices itself to become something that most in "the community" consider desirable (or at least acceptable). But that might not be the kind of community the blog author/owner wants.
To put it in concrete terms: HN is moderated. Reddit is policed by the inmates. Which is a better community? I'll take HN by a fair distance.
For example if you have a subscription functionality , instead of doing
def subscribe , you would do it like:
def create_subscriprion.
This in turn is advocated on the bases that it will improve readability and lessen confusion amongst programmers. What are your thoughts on that?