Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Section Descriptions

by swiftone (Curate)
on May 31, 2000 at 17:36 UTC ( #15610=monkdiscuss: print w/replies, xml ) Need Help??

The Snippets section has a wonderful description of what it is for. A few other nodes do as well. Many, however, don't. I think that either
  • Each section (Code, Library, etc) should have such a description, OR
  • The Site How To should have those descriptions.
This node says "(I realized that this is Code instead of Craft..." and I'm wondering how they came to that realization, since I have no clear idea what the difference between the sections is (they both appear to have postings of code and discussion about it)

Replies are listed 'Best First'.
RE: Section Descriptions
by muppetBoy (Pilgrim) on May 31, 2000 at 17:53 UTC
    I agree that the distinctions between code and craft are pretty blurred. Also Seekers of Perl Wisdom and Q&A are similarly, er, similar.
    Perhaps the Craft section should consist of shining examples of code which high level monks have selected from throughout the rest of the monastery and is not posted to directly? ie a sort of moderated 'hall of fame' for code.
    Update: I've just noticed that the Guide to the Monastery gives a brief outline of each section.
      Good find. I did a search, but didn't think to look for "Guide". Vroom, can we link to this via the Need Help?? link?

      Update: Taken care of. Thanks Vroom!

Separation of Craft and Code
by Corion (Pope) on May 31, 2000 at 18:15 UTC

    I created that node as I first posted my Code under Craft.

    The criterion I used for discriminating was, that Craft seems to be more like a snippet and not always full working code, but all in all, it should be (IMO) short code, no longer than 20 lines.

    Code on the other side can be whatever it takes.

    Of course, that's just my opinion and not the official statement ...

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: monkdiscuss [id://15610]
Approved by root
[shmem]: well finally.
[stevieb]: nice! I just finished a GPS "take me home" device last week, and did a bunch of software updates to it yesterday. I also created a pseudo chip with an Arduino to simulate an IC, where it responds to register read/writes over the I2C bus...
[stevieb]: ...from an I2C master. It's ugly and there are many changes I'm going to make, but I had not done anything like it before. It's designed for my RPi:: automated test platform; a system that does CI on *all* my RPi modules.
[shmem]: pseudo chip?
[stevieb]: well, what happens is the Arduino 'listens' for requests r/w, and does the appropriate thing when it's interrupted based on the 'register' address sent in. It's ugly as it was my first attempt, but I've got great new ideas I'm just sitting.
[stevieb]: ...down to implement now. Here's the sketch as it currently sits
[shmem]: well I use I2C and SPI and stuff, but creating a pseudo chip looks to me like lot of indirection and memory clutter... not?

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (6)
As of 2017-06-25 22:40 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (572 votes). Check out past polls.