forked from barryclark/jekyll-now
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Here goes my initial blog upload - Blog barryclark#6
- Loading branch information
1 parent
e2d0436
commit 9d8182f
Showing
1 changed file
with
9 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
--- | ||
layout: post | ||
title: Highlights my my What Do I Like | ||
--- | ||
<img src="https://github.com/snwarner22/snwarner22.github.ioOLD/assets/137221902/b14ab7e0-1c9e-45f7-98e9-31920f6ffc5b" width="60%"/> | ||
#### While reading the book, How to Open Source, was brought up to speed with an unfamiliar term to me. The term was nonviolent communication (NVC) for short. My curiosity was sparked when Richard Schneeman, the author of HTOS, explained why NVC is valued in community-driven spaces such as open-source communities. I have already begun my plunge into the unknowns of this topic. I plan to read a book on this concept to solidify my roots within this knowledge. The book is titled Nonviolent Communication: A Language of Life and is authored by Marshall B. Rosenberg PhD. | ||
#### I am grateful for the opportunity to sit down and conversate with Richard. While speaking with the group, Richard shared a unique insight; he briefly explained the notion of always acting like people can see your code. I find this insight helpful and agree with his message. This approach to coding makes me want to be a perfectionist at my craft. Like Michelangelo crafting the infamous David, treat your code as a gift to humanity, treating your work as if it were visible to the world is a reminder to programmers everywhere. Give It Their All! | ||
#### In the near future I may find myself pulling an all-nighter tirelessly working on a program assignment. It would be foolish of myself to not think back to this lesson. I will carry this knowledge throughout time of low morale. | ||
#### To Richard, time has shown trends which make him believe “The longer I’ve been employed as a professional coder, the more I realize that I’m paid […] for my ability to figure out things that I do not know quickly.” Our catalyst summer program has shown how this can be true to a person. During the program I found myself in unfamiliar territory (a lot). Troubleshooting errors, finding clever work-arounds, and reading (lots of reading) made me believe this. Quite honestly, I only utilized information from one particular Norfolk State class which happened to teach unix basics. While it did help how quick and fluid I could obtain new information, my prior knowledge was less useful than my ability to learn new material and ask thought-provoking questions. |