One of my own favorite explanations of meter in English is Timothy Steele's All the Fun's in How you Say a Thing: An Explanation of Meter and Versification [0].
I'd be interested if anyone has other recommendations?
I've been programming for a long time and had to learn R a few years back for a series of projects. The documentation and community seemed to me, as a newcomer, to be very focused on how to solve particular statistical and modeling problems, and I was almost always able to do what needed to be done relatively quickly. (Python documentation and communities, in contrast, span all kinds of applications that can be difficult even for an experienced programmer learning Python to sort through and evaluate. I can also imagine the migration to 3.x has been a challenge for newcomers.)
Although I enjoyed learning and using R, as a CS person I was bothered that I understood how to do X in R, but I had no clue about what was happening when I did X. I found this paper to be particularly useful in describing R from a CS perspective: http://www.lirmm.fr/~ducour/Doc-objets/ECOOP2012/ECOOP/ecoop...
In case you are a casual observer or are new to Scheme and are wondering why this might be particularly important to the language, wikipedia explains:
"The R6RS standard has caused controversy because it is seen to have departed from the minimalist philosophy [of scheme]. In August 2009, the Scheme Steering Committee ... announced its intention to recommend splitting Scheme into two languages: a large modern programming language for programmers, and a subset of the large version retaining the minimalism praised by educators and casual implementors;"[1]
Perhaps the history of Scheme standardization itself has something to teach us about the challenges and rewards of openly balancing a wide range of interests and agendas over the long term?
I have had the same experience after deleting my account several years ago (for different reasons). I do keep wondering if it will pop up as an issue, so I'm very curious about other people's experiences when not participating in LinkedIn.
Yes, I agree. The history of philosophy is an important part of philosophy, not all of philosophy. I studied the subject nearly 30 years ago and can only recall the history courses as having a decisive Western bias (though not a monopoly). I believe all the courses were correctly labeled, and I can remember at least one embarrassed explanation that other traditions could not be included.
I am curious how the bias might affect topics like contemporary epistemology, logic, or the philosophy of science or of mathematics?
Agreed, andr, that the number of new good talks can continue to increase. This is an interesting story and relates to a variety of other organizations seeking to scale quickly, whether from necessity or ambition. Is there an ongoing discussion of it as it pertains to TED & TEDx anywhere?
As the number of conferences and speakers grows, are you concerned that the Law of Large Numbers will exact its toll and make the sample of speakers more typical of the population as a whole? Inviting the flashiest of SF and NYC to speak is quite a builtin selection bias, but there seems to be no apparent strategy for preserving the distinctiveness of speakers as TEDx scales.
I do share your sentiment! The shorter "MyMail" makes the same point without needing the profanity, and your more emphatic name would then be available for the most desirable MyMail client...
Answering "In the context of an interview, [I get] frustrated because my default response to not knowing the answer to a question ... is to go out and research the problem [and I cannot do that in an interview]" is a nice response to not knowing an answer and would get bonus points for honesty and self-awareness.
The best candidates will recognize and comment on the ways in which frustration can be either constructive or destructive.
"This contrived situation is not one that applies to the average day in the workplace," is a serious over-generalization. Enormous amounts of code are written based on contrived beliefs about the way business does or should operate. The world would be much better off if programmers were better at recognizing and constructively commenting on these artificialities.
If the motive is laziness or the objective is to trick or intimidate a candidate, then I agree that the method deserves scorn. But I disagree with your position the technique is never reasonable. I like to hire people who know more than I do, and in this circumstance puzzles occasionally help learn about a person.
As a candidate I'm not particularly good at solving puzzles in this kind of situation, but I'm not bothered when people present them because the discussion and interaction about the puzzle matters more to me than getting the answer.
As an interviewer it is important to ask questions that a candidate cannot answer to see how they react. Since I'm a slow thinker myself, I must sometimes resort to "unfair" questions. I don't expect an answer, I expect a reaction.
After establishing a friendly rapport, finding common technical background, presenting an "unfair" puzzle, and discussing the puzzle a bit, then a discussion like this is golden:
Candidate: "Do you believe my ability to solve this puzzle indicates how well I could do this job?"
Me: "No. Though I often enjoy puzzles, I'm not particularly quick with them myself."
Candidate: "Then why ask a question like this?"
Me: "Because I want to see how you react when you don't know an answer right away. In your case, I had to resort to tricks."
One might charitably speculate that these are organizational challenges related to growing and being part of Salesforce.com. Things that were simple for a small, dynamic company can become shockingly complicated as the number of interests and priorities increases.
We might also consider the potential for a clash of cultures: Heroku has been relatively open about implementation details. Salesforce, on the other hand, has shown an extreme reluctance to share this kind of information.
I confess I can't help but wonder if the new willingness to make this kind of surreptitious change might in any way be connected to Byron Sebastian's sudden resignation last September. Is that nutty of me?
I can't help but wonder if this kind of surreptitious change to the platform might in any way be connected to Byron Sebastian's sudden resignation last September from Salesforce. Is that nutty of me?
I have had similar periods of time in my own life, but even these have begun to fade over many years. Luckily, there are plenty of techniques to avoid this and many are not new. E.g., Diarists have used writing to remember day-by-day for centuries. For travelers like you, remembering or recoding locations by date definitely helps to organize memories.
Unlike a written diary, which is conceptual, I like how Cesar is systematically compiling small visual queues using a discipline amounting to a form of sampling or measurement. I'm not sure how a video beats a photo-of-the-day, but perhaps it simplifies the overall process of selecting images?
I'm also guessing that his daily sampling method might control for the natural tendency of sensational moments and aspects of life to eclipse the less sensational parts over time.
I don't think that Bill Gates claims decent measurement is sufficient for the kind of progress he seeks but rather claims that (in most cases) it is necessary.
I suspect one answer to Mathbabe's question "what can a non-academic mathematician do that makes the world a better place?" might be to highlight and explain the kinds of logical dependencies that are so often obscured by polemics.
I cringe at the suggestion Bill Gates is naive. Anyone who has spent the time he has in corporate America will be well aware of the challenges and politicization of measurement.
I'd be interested if anyone has other recommendations?
[0]: https://www.ohioswallow.com/book/All+the+Fun%E2%80%99s+in+Ho...