Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Submission: Brock, "Naming Practices in Code as Rhetorical Strategies" #2

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

brocktopus
Copy link
Contributor

Submission on the rhetorical significance of naming (files, variables, functions) in code.

@steveklabnik
Copy link

I like it! An interesting example that is related is Ruby on Rails' Array#forty_two controversy. Here's the documentation. As you can tell 'the Reddit' is a reference to Reddit. rails/rails@e50530c is the commit that introduced it. rails/rails@22af62c is the commit that caused it. See the comments. Here is the 'the reddit' thread, and here is the thread after.

@WardCunningham
Copy link

The metaphorical naming of software elements has been discussed at great length on the c2 wiki:

http://c2.com/cgi/wiki?CategoryMetaphor

Extreme Programming specifically asks for careful choice of metaphor in its System Metaphor practice:

http://c2.com/cgi/wiki?SystemMetaphor

@brocktopus
Copy link
Contributor Author

I just wanted to note that those wiki discussions are fantastic. Thanks for the feedback--I am definitely taking that info into consideration as I consider how to improve upon this submission.

@WardCunningham
Copy link

I'm glad you found that discussion useful.

System Metaphor has been recognized as the least-practiced practice in extreme programming or any other agile method. Joshua Kerievsky founded a group conversation to explore why. I don't recall any conclusion but there is an archive waiting to be explored.

https://groups.google.com/forum/?fromgroups=#!forum/softwaremetaphor

@brocktopus
Copy link
Contributor Author

I've added in an extra example (Roedy Green's "How to Write Unmaintainable Code" and briefly referred to Ward's note on system metaphor in my introduction. I continue to welcome any and all comments, concerns, questions, critiques, etc.

inducing cooperation in beings that by nature respond to symbols."[^burke]. The
construction of meaning through language relies on what that language
represents, and this is no different in the source code of software than in any
conventional form of discourse. In fact, as Ward Cunningham has pointed out in

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love it when scholarship references in-process review material! It heightens the awareness of writing as not being a monolithic event.

revised submission based on reviewer comments and concerns
revised submission based on reviewer comments and concerns

tweaked university affiliation

tweaked university affiliation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants