As that site indicates, in X.org with the defaults, '·' is easily typed with 'Compose . -', 'Compose . ^' or 'Compose ^ .' (this should also work from the console in Debian, at least, which uses xkb bindings throughout).
I love the Compose key, and don't think I'll ever use a desktop without it.
I asked on purpose again for a couple of reasons: most of the answers were over 1 year old, most focus on why people shouldn't ask and not why they do ask or why they do sign.
Personal opinion, and it's very likely you know all this. I'm sorry in advance if it seems patronising, but here are my thoughts as they occurred. Even though some are invalid or unjustified, I thought there would be value in seeing them "up front" like this.
There would have been value in saying so in your question. I can imagine that most people would go - been there, done that - and just moved on.
From what you say you have done your homework and looked at the previous answers, but there would have been real value in collating the answers, presenting them, and then explaining why you feel the question is worth asking again. What do you feel has changed? Why are those answers no longer relevant, or complete?
Just asking the question with no reference to previous answers makes it feel like you haven't done any checking or research.
The document has its short-coming, and it's for a different context, but let me quote from "How to Ask Questions the Smart Way"[0]:
Before asking a technical question by e-mail,
or in a newsgroup, or on a website chat board,
do the following:
Try to find an answer by searching the
archives of the forum or mailing list
you plan to post to.
Try to find an answer by searching the Web.
Try to find an answer by reading the manual.
Try to find an answer by reading a FAQ.
Try to find an answer by inspection or
experimentation.
Try to find an answer by asking a skilled
friend.
If you're a programmer, try to find an
answer by reading the source code.
When you ask your question, display the fact that
you have done these things first; this will help
establish that you're not being a lazy sponge and
wasting people's time. Better yet, display what
you have learned from doing these things. We like
answering questions for people who have demonstrated
they can learn from the answers.
A lot of that is not relevant in this case, but enough of it is that it's worth knowing.
Thing is, it really is helpful when asking questions to provide a summary of what you've done, what you've found, and what remains to be answered or updated.
I'm sorry, I was trying to be funny. I really found your points valid, and the helpful reminder was very appreciated as it will get me better answers next time.
Indeed, and learning to use a debugger will allow you to gain fluency in new languages and frameworks much faster that the simple, albeit powerful, printf.
I remember needing to learn Ruby and Rails on an existing closed codebase and having the debugger take me right to the core of Rails several times to understand why certain things were done in a certain way in the top level code. This allowed me to get acquainted with internals of Rails and how Ruby's inheritance system much faster as well as the existing codebase that was built on top.
I go as far as to have a dedicated project notebook for big new projects, I write everything down that I come across that I need to remember or need to question.
I've often been dropped into codebases where there is only a month to question the previous maintainer before all the business knowledge is lost as they move on to bigger and better things. So getting all the questions/queries down asap is the fastest step to get the undocumented business logic documented.
Even when you can't ask the questions I like to turn all the unknown unknowns into known unknowns. :)
“The Statements of Accomplishment (free) and Verified
Certificates (signature track) will be provided to all
those who achieve 50% or higher grade, and will be released
within 1-2 weeks after the final submission deadline closes.
Everyone will be notified by email when they are ready. You
will be able to download the certificate from your course
records after they are released.”
I think binary logging is the wrong word to use. As far as I can tell it's not binary he means, but database logging. Storing things in a database sounds far less scary than binary.
At best it's a NUL separated database structure where the fields are not compressed, which IS greppable just use \x00 in your regexp. At worst he might mean BER, which is an ASN.1 data encoding structure.
I did too, until I found.
http://middot.net/