I'm not sure this is the right place to post this, but I couldn't find a better place. I have this idea for a series of nodes to posts and wanted feedback before I got started.
My idea is to show various uses of Perl for my cryptogram hobby. In each article I'd show how I did it and invite improvements. I have several "chapters" of ideas to post, and the (not) working title is something like "How I did it - you can do better: Goibhniu's Cryptogram applications for Perl - Chapter 0: Introduction", etc. I like all the parts, but that's obviously too long for a node title. I imagine standard sections a) motivating and describing the problem in cryptograms, b) presenting my solution and how I use it, c) inviting improvements from code eficiency to redesign.
Some nodes might be:
-
Chapter 0 - Introduction to ACA cryptograms hobby (little or no Perl)
-
Chapter 1 - Monoalphabetic substitution key alphabets
-
Chapter 2 - Word matching
-
Chapter 3 - Frequency analysis
-
Chapter 4 - Variety of Contact analysis
-
. . .
ok, that's not very informative if you're not into the cryptogram stuff already, but suffice it to say (for now) that these bring up slightly different areas of Perl to discuss as well. Also, my coding is horrible, so I'm sure there will be much helpful advice for improvements that others could learn from (if there's interest).
I guess I have some questions to help decide whether to get started:
-
Would this be of interest to the community? Has something like this been done before (not sure what to look under)? Was it well received?
-
What section should it post under (Cool Uses?)
-
Are there problems with the approach (standard sections listed above)? Are there suggestions for improvement?
-
If I get started, the title obviously needs work as mentioned above.
-
How frequent should I try to post (weekly? monthly? not more often than I'm ready?)
-
Are there traps I'm not thinking of? I'm still new to the site, so (how to put this delicately?) is there some lurking flame war I'm going to step on or some issue I should avoid?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.