pauamma: Cartooney crab holding drink ("Cartooney crab holding drink")pauamma ([personal profile] pauamma) wrote in [site community profile] dw_dev_training,
@ 2011-09-21 12:11 pm UTC
  • Previous Entry
  • Add to Memories
  • Tell someone about this!
  • Next Entry
Entry tags:questions
I just came across To Answer, Or Not To Answer. The gist of it is: someone asked "Should I answer a perl question when I'm not sure of the answer or when I can only answer part of the question?" and got overwhelming "yes" answers (and very good suggestions on how to handle uncertainty), because even if your answer doesn't help the person asking, researching your answer (and thinking about the question) may well help you. So as an experiment, I'd like to try something similar in this entry:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in the discussion I linked to above.

If this works, I'll try to make it a regular feature of this community. (How often should it happen?)

(Read 23 comments) - (Post a new comment)
(Flat) (Top-level comments only)

jeshyr: A flower with text "In life's name" (Young Wizard, Young Wizard - In Life's Name)


[personal profile] jeshyr
2011-10-01 10:22 am UTC (link)
How do you start individual bits like that anyway?I 've only got as far as "worker-manager --debug"

(Reply to this)  (Thread from start)  (Parent)  (Thread) 


pauamma: Cartooney crab holding drink ("Cartooney crab holding drink")


[personal profile] pauamma
2011-10-01 12:40 pm UTC (link)
Pasting from the wiki page about that topic I'm working on:

=== Individually ===

You can also start individual workers from the shell prompt, by typing:

<syntaxhighlight lang="bash">$LJHOME/bin/worker/(worker-name)</syntaxhighlight>

Most workers accept the <code>-v</code> or <code>--verbose</code> flag to request extra debugging output and stay in the foreground when started from the shell prompt, so ^C should work to kill them.

(Reply to this)  (Thread from start)  (Parent) 


(Read 23 comments) - (Post a new comment)
(Flat) (Top-level comments only)