As configured in my dotfiles.
start new:
tmux
start new with session name:
Max Glassie maxglassie
maxglassie
/ tmux_cheatsheet.markdown
Created
August 22, 2017 23:35
— forked from henrik/tmux_cheatsheet.markdown
tmux cheatsheet
maxglassie
/ gist:ef4ae069e4edab64c17e265e349e33b2
Last active
June 7, 2017 03:55
Merging Two Worlds: Combining Chinese and Code in An Open Source Contribution
I lived in Beijing for two years and studied Mandarin Chinese. It was an amazing and humbling experience. After a time, I used the skills I'd picked up studying Mandarin to learn to program at the Turing School of Software and Design.
As part of our final graduation requirements, we're asked to contribute to an open source project. In my research, I started exploring the Faker gem.
The Faker gem is a program that Ruby developers can add to their projects which allows them to generate "fake" data for testing and demonstration purposes.
But perhaps the best part is the wide variety of ipsems available. Developer culture loves its humorous fake examples and Faker provides. There are fake names taken from Harry Potter or Star Wars. Fake filler text full of Chuck Norris programming jokes (yea, you read that right). It adds a spark of fun to client meetings, that's for sure.
maxglassie
/ qs_max_spencer_reflection.markdown
Last active
May 18, 2017 05:38
Quantified Self: Max // Spencer Reflection
What do we want to work on / or continue learning?
- How to get better troubleshooting techniques
- Better at unit and model testing in Node
No excuses: What could we have done better?
We ought to have committed to ES5 or ES6 syntax, regardless of whether or not it causes technical issues, we were told to stick to one style and we didn’t do that. When using researched code for inspiration, either from lessons, Stack Overflow, or instructor code, it would be good to study this code more for understanding and then we’d be better at translating into the style (ES5 or 6) that was the best for us.
We also felt like we started off not as strong organizationally and we steadly improved, but some of those habits would have been helpful in the beginning. In the beginning, be stronger at asking questions and making sure, especially in regards to testing, that our setup was done properly. Asking better questions in our pull requests, for example in model testing, where we could have been more specific about
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
| ## Contributing to ManageIQ | |
| * Why: This is a well backed, well written open-source Ruby project for project management, working with the Github API | |
| * What: I found a refactoring request at https://github.com/ManageIQ/miq_bot/issues/305 that sounds approachable and interesting. It asks for refactoring the GitHub service, using a new module. I can engage the thread and get some more details on what they want. | |
| * I Need: To pull this project locally, run the tests, and explore the code to understand precisely what they're doing and how to refactor it properly. I should also use the tool. | |
| * When I'm Done: It isn't a pressing need by definition but if I am able to write code up to their standard, I imagine they will be grateful for some refactoring in a good PR. | |
| ## Contributing to CBRAIN |
maxglassie
/ recursion_workshop.markdown
Last active
March 7, 2017 16:04
Running a Recursion Workshop
One of the highlights of module Two at Turing was running a recursion workshop with Courtney Meyerhofer. Recursion can be tricky. We wanted to give an understanding of how recursion works and to provide tools for approaching writing recursive procedures. We used examples in LISP from the Structure and Interpretation of Computer Programs (SICP) by Hal Abelson and Gerry Sussman for the workshop.
You can checkout our Github Repo for implementation of some simple recursive procedures in both LISP and Ruby.
- Learning to read code
- Learning to run code on a whiteboard
- Tools: patterns to use
maxglassie
/ setting_expectations.markdown
Created
February 21, 2017 20:35
— forked from Carmer/setting_expectations.markdown
Setting Expectations
Group Member Names:
-
When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed?
-
How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
-
Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
maxglassie
/ empathy_reflection.md
Last active
November 27, 2016 03:58
Turing - Empathy reflection - Glassie
Turing - Empathy Reflection
What role does empathy play in your life and how has it helped you?
Empathy is the only way to really make a connection with others. Without the ability to empathize with others, to feel what they are feeling and experience what they are experiencing, even to the limited extent that I am able, I would never get beyond my own little bubble and my self. Empathy has helped me relate to others when I've traveled or lived overseas; to contemplate how my colleagues are feeling and to craft my efforts to those circumstances; and to navigate complex personal dynamics to find a loving solution to problems. I try to develop my ability to empathize with others and I find just acting in a way that demonstrates understanding of others changes the environment I'm in.
How does empathy help you build better software? The whole purpose of software is to take a model of a human reality and make it something we can interact with and use. The best models come close to accurately represe
maxglassie
/ max-glassie-prework.md
Last active
November 27, 2016 22:27
— forked from mbburch/prework.md
Pre-Work Gist