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?
To get started, pair with your partner on any problems they may have encountered while trying to style task manager last night.
Help each other answer any questions you may have about CSS/HTML. MDN (mozilla developer network) is a great resource for anything web related if you need a reference for anything.
Please bring any question you may have to our HTML/CSS Review.
If you are having trouble getting started here are some things to think about:
Now open the project. This is a Rails project, but you don't need to know rails to do these exercises. Navigate to the /spec directory. Within the /models directory you will see a file named activerecord_obstacle_course_spec.rb. Open it and read through the tests. If you want to know more about RSpec you can find it here. With RSpec, :let declares a variable but not until it is called in the code. The :let! declares the variable right there on that line of code.
First, take about 30+ minutes and do a retro about your group experience. What's a retro? Think about our friday whole module retro - positives, negatives, and so-sos and actionable things you can improve to better the situation for next time. Here is a short read that may help define retros if you need a little more context. It may be helpful to revisit your DTR conversation too.
"By not giving me feedback, you're preventing me from growing." -Anonymous Student
The learning at Turing extends beyond technical training. Equally as important is developing professional skills and creating an environment that encourages learning. As a precursor to a professional career as a Software Developer, we would like to emulate practices followed in a professional work environment. A professional work environment consists of a community of people. In addition to creating software developers, we want to simulate an industry we want to work in. We want to also concentrate on creating thoughtful, engaging developers, to add to the tech industry. Here are a few things that make a good community member at Turing:
If you are unable to attend a day of instruction, let your instructors know as soon as possible. It is your responsibility to stay up-to-date on lessons that you miss. If you need anything or have questions, let your anchor or supporting instructor know. They’ll be happy to help. When on group projects, be sure to l
This is a guide to keep you busy over intermission. What you choose to do here will be highly dependant on what you need to review, ramp up on, or learn.
You don't HAVE to do any of this. You will not be graded, but most likely there are some things here you SHOULD do. I would suggest you do something over break to keep the rust off. At this point you are almost finished with Turing, and you should be a self-sustainable learner. That means you should be able to judge what you need to do. Here is what I would suggest: