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

Clarify value of "technical excellence" #148

Merged
merged 1 commit into from
Nov 23, 2015

Conversation

ehashman
Copy link
Contributor

Some people consider technical excellence to be a static quality,
set at birth, unchanging. But I believe technical excellence can
be achieved by anyone, through persistence, hard work, and a
supportive environment. This was not clear in the way this value
was stated, so I've addressed this.

See also
http://akaptur.com/blog/2015/10/10/effective-learning-strategies-for-programmers/

Some people consider technical excellence to be a static quality,
set at birth, unchanging. But I believe technical excellence can
be achieved by anyone, through persistence, hard work, and a
supportive environment. This was not clear in the way this value
was stated, so I've addressed this.

See also
http://akaptur.com/blog/2015/10/10/effective-learning-strategies-for-programmers/
@fboxwala
Copy link
Contributor

lgtm

fboxwala added a commit that referenced this pull request Nov 23, 2015
Clarify value of "technical excellence"
@fboxwala fboxwala merged commit ba93507 into wics-uw:constitution Nov 23, 2015
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.

2 participants