link roundup
Two items seen in rapid succession today:
Can you help? Somebody asked a question recently on Writers about guidelines and heuristics for when to use screen shots in technical documentation. The question isn't looking for opinions or what you, personally, do but, rather, formal guidelines along the lines of what GNOME does for its documentation. So far it's only attracting opinion answers. I, too, have opinions and practices that I follow, but I can't source them either and I'd like to see the question get a good answer.
Speaking of Writers, I wrote a little something about writing good API reference documentation (like Javadoc), based on advice I've given informally over and over again -- finally wrote some of it down in a public place. Feedback welcome.
I recently saw an article with interesting-seeming observations and analysis of Modern Orthodox Judaism. I'm not all that tuned into the MO community and can't evaluate its credibility from inside, but I found it an interesting read. If any of y'all would care to tell me where on the spectrum from "yup" to "WTF?!" this is from your perspective, I'd be interested.
Finally, a little something for those who use the text editor vim (which I gather is related to vi?):
.
- Here's why you're not hiring the best and brightest: (Jeff Atwood) talks about making telecommuting work so that you really can hire the best employees, as opposed to the best employees willing to live in a particular location. I once applied for a telecommuting position at a company that seems to get it as far as that's concerned, and a lot of the stuff they do is reflected in this article.
- What do programmers care about? (20-minute video): Joel Spolsky (Stack Exchange, Fog Creek) talks to recruiters about how to recruit programmers. If you've read Joel On Software you already know a lot of what he has to say here, but I still found it interesting to watch.
Can you help? Somebody asked a question recently on Writers about guidelines and heuristics for when to use screen shots in technical documentation. The question isn't looking for opinions or what you, personally, do but, rather, formal guidelines along the lines of what GNOME does for its documentation. So far it's only attracting opinion answers. I, too, have opinions and practices that I follow, but I can't source them either and I'd like to see the question get a good answer.
Speaking of Writers, I wrote a little something about writing good API reference documentation (like Javadoc), based on advice I've given informally over and over again -- finally wrote some of it down in a public place. Feedback welcome.
I recently saw an article with interesting-seeming observations and analysis of Modern Orthodox Judaism. I'm not all that tuned into the MO community and can't evaluate its credibility from inside, but I found it an interesting read. If any of y'all would care to tell me where on the spectrum from "yup" to "WTF?!" this is from your perspective, I'd be interested.
Finally, a little something for those who use the text editor vim (which I gather is related to vi?):
.