wfh, work from home
Yeah, Okay.
Sureeee.
https://cdn.meme.am/instances/66329129.jpg
http://gifrific.com/wp-content/uploads/2012/04/Jon-Hamm-Sure-Thing.gif
http://i.imgur.com/seh6p.gif
http://www.reactiongifs.com/wp-content/uploads/2013/11/yea-k.gif
// Just before switching jobs: | |
// Add one of these. | |
// Preferably into the same commit where you do a large merge. | |
// | |
// This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
// and then it quickly escalated into more and more evil suggestions. | |
// I've tried to capture interesting suggestions here. | |
// | |
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
wfh, work from home
Yeah, Okay.
Sureeee.
https://cdn.meme.am/instances/66329129.jpg
http://gifrific.com/wp-content/uploads/2012/04/Jon-Hamm-Sure-Thing.gif
http://i.imgur.com/seh6p.gif
http://www.reactiongifs.com/wp-content/uploads/2013/11/yea-k.gif
# I know dict's have `.get()`, this example was made to break if the key is not | |
# there to show the use of multiple try/except's | |
# Yes I know that having the except and else on 1 line each does not fit with PEP8 standards. | |
# But when you have many of them it helps reduce the size of the file and is no harder to read | |
data = {'some_key': 'key value'} | |
key_data = None | |
for _ in range(1): | |
try: | |
key_data = data['someKey'] |