Git Makes Me Angry Inside @emmajanehw http://drupalize.me http://developerworkflow.com/ room password: psav1755 Does Git make you angry inside? In this workshop you will get a gentle introduction to working efficiently as a Web developer in small teams, or as a solo developer. We'll focus on real world examples you can actually use to make your work faster and more efficient. Windows? OSX? Linux? No problem, we'll get you up and running with Git, no matter what your system. Yes, this is an introductory session. This is for people who feel shame that they don't know how to "clone my github project", wish they too could "get the gist", and get mad when people say "just diff me a patch" as if it's something as easy as making a mai thai even though you have no rum. No, you don't have to have git installed to attend. You don't even need to know where the command line is on your computer.
Does Git make you angry inside? In this workshop you will get a gentle introduction to working efficiently as a Web developer in small teams, or as a solo developer. We'll focus on real world examples you can actually use to make your work faster and more efficient. Windows? OSX? Linux? No problem, we'll get you up and running with Git, no matter what your system. Yes, this is an introductory session. This is for people who feel shame that they don't know how to "clone my github project", wish they too could "get the gist", and get mad when people say "just diff me a patch" as if it's something as easy as making a mai thai even though you have no rum. No, you don't have to have git installed to attend. You don't even need to know where the command line is on your computer.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Does Git make you angry inside? In this workshop you will get a gentle introduction to working efficiently as a Web developer in small teams, or as a solo developer. We'll focus on real world examples you can actually use to make your work faster and more efficient. Windows? OSX? Linux? No problem, we'll get you up and running with Git, no matter what your system. Yes, this is an introductory session. This is for people who feel shame that they don't know how to "clone my github project", wish they too could "get the gist", and get mad when people say "just diff me a patch" as if it's something as easy as making a mai thai even though you have no rum. No, you don't have to have git installed to attend. You don't even need to know where the command line is on your computer.
It’s not your fault. Honest.The way we teach web stuff isn’t the way that you probably need to be exposed to the information in order to learn it.Blame the teachers, not yourself.Or maybe not blame but, be persistent when working to solve important and sticky problems.
How we typically teach people how to tech has nothing to do with adult education best practices.
RTFM: read the manualHere are all the commands, here are all the options. Memorize everything, and figure out later how to apply the knowledge.
Self-taught learning involves a lot of Googling, guessing, and teeth gnashing.
Guess at what the problem is.Search on the internet.Find someone else’s description of how they solved, what you hope is a similar problem.
Adults learn best when they can be selfish.
Andragogy assumes the following about the design of learning:Adults have the need to know why they are learning something.Adults learn through doing.Adults are problem-solvers.Adults learn best when the subject is of immediate use.
This is not your problem:My client wants me to memorize all the parameters for using Git at the command line.
Your problem might sound like: My client keeps changing his mind, and but they don’t want to pay me to redo the work.Your problem doesn’t sound like: My client wants me to memorize all the parameters for using Git at the command line.
Solve. Real. Problems.
Define your real problem clearly.Learn how to use a tool to get your problem solved.Try solving the problem. Take notes about how smooth it was to solve your problem. Write recommendations to your future self on how you’d solve the problem in the future now that you know what you know.
Agenda
• Work flow and branch management
• Disaster mitigation
• Q&A / therapy session
Your problems are 90% social.
What’s your role?
What are your tasks?
download work
create snapshot
share work
What’s your workflow?
How do we make Git do that?
Set the stage!
Before we can set our workflow we need to know who we’re dealing with and what they’re supposed to be doing.
Who’s on your code team?
Write down a list of all of the people on your code team. This list may include:
• developers
• designers
• project managers
• clients
Time: 5 minutes
Where do you fit in?
Maybe you do everything. Maybe you only do some things. Write a list of all the tasks you are actually responsible for. This might include:
• Writing code.
• Reviewing code.
• Pushing tested code to the server.
• Fixing broken code.
Time: 1 minute
What are your tools and restraints?
Often there are other things we need to fit into our workflow. Create a third list of any tools and restraints you are aware of. This list might include:
• Version control software (we’ll always assume Git)
• Code hosting system (Bitbucket, GitHub, self-hosted)