Skip to content

Instantly share code, notes, and snippets.

View onealexharms's full-sized avatar

Alex Harms onealexharms

22 followers · 0 following
View GitHub Profile
@onealexharms
onealexharms / Adventures.md
Last active July 10, 2016 16:51
tl;dr: looking for stable pay-as-you-go housing in NYC

Update: I think we got it. Not confirmed yet but looking good. Thank y'all so much!

I always told my kids I thought the "don't tell anybody your birthday wish" rule was stupid. If nobody knows your wish, that could make it pretty hard

@onealexharms
onealexharms / readability
Created July 19, 2014 18:48
which is more readable?
(cond
(includes-failure-message?
(set! message (car args))
(set! condition (cadr args)))
(else
(set! condition (car args))))
(cond
(includes-failure-message?
(set! message (car args))
@onealexharms
onealexharms / keybase.md
Created April 7, 2014 18:12

Keybase proof

I hereby claim:

  • I am angelaharms on github.
  • I am angelaharms (https://keybase.io/angelaharms) on keybase.
  • I have a public key whose fingerprint is 3091 6289 62BE 1B60 E173 88A9 AD61 E929 B4DD 20F0

To claim this, I am signing this object:

@onealexharms
onealexharms / gist:7374118
Created November 8, 2013 17:00
Session title: "Wow! That was a great retro!"
Do your retros suck? A little?
It's often said that if you can only introduce one agile practice, the retrospective is most important. We have whiteboards, stickies, and lots of activities, so what isn't working? How do we manage to create stale retros that don't produce any visible changes or improvements?
Learn how to go beyond exercises and activities to get your team talking, exploring together, and creating real improvement. We'll talk about building trust, encouraging learning & embracing mistakes. Learn how you can create a retrospective culture where every observation is valued, saying "uncomfortable" things is welcomed, and improvement is a given.
@onealexharms
onealexharms / gist:5473536
Last active December 16, 2015 17:50 — forked from elight/gist:5473485
removed 1 comma removed 1 space replaced 'confuerence' with 'conference' replaced 'redress' with 'address' suggested this: And while you address it yourself, remember to continue to treat the other party with kindness and respect.
## Front matter
I am proud to say that, while I have asked repeatedly over the years, I have never heard of a single incident where a participant has harassed another.
@onealexharms
onealexharms / apology.
Created April 29, 2012 12:09 — forked from unclebob/apology.
Apology to Women Programmers.
Today I gave a keynote at ACCU in Oxford. In the midst of it I made two (count them) two statements that I should have known better than to make. I was describing the late '70s, and the way we felt about the C language at the time. My slide said something like: "C was for real men." Emily Bache, whom I know and hold in high regard, spoke up and said "What about women?". And I said something like: "We didn't allow women in those days." It was a dumb crack, and should either not have been said, or should have been followed up with a statement to the effect that that was wrong headed.
The second mistake I made was while describing Cobol. I mentioned Adm. Grace Hopper. I said something like "May she rest in peace." I don't know that any of the words were actually demeaning, but the tone was not as respectful as it should have been to an Admiral in the United State Navy, and one who was so instrumental in our industry; despite what I feel about Cobol.
I am a 59 year old programmer who was brought up