Skip to content

Instantly share code, notes, and snippets.

@monstaro
Last active March 23, 2020 23:59
Show Gist options
  • Save monstaro/96e08aa4f7f8418f2a57ca2427e5d4b9 to your computer and use it in GitHub Desktop.
Save monstaro/96e08aa4f7f8418f2a57ca2427e5d4b9 to your computer and use it in GitHub Desktop.
Megan V + Cody S : VRAD DTR

Times Available

Expect occasional afternoon hours to be taken up for exercises (running, lifting, getting swole)

Available most of the time, Cody has occasional band practice and we will try and not go too crazy on the weekends. Get the bulk of our stuff done after class time.

Times to bust shit out: Work time, and we're okay with basically just sprinting after class into work time/into the early evening if needed.

Cutoff times: 7-9

Wireframing tools

Still deciding, but Cody has Adobe XD so we might try that.

Project Boards

We will use GH Pages to keep track of things.

Learning Goals

Get some more solid testing foundations.

Get more comfortable with components (class v functional, when / when not to create a new component)

Really think critically about use of color and UX.

Get better at using css-grid.

Consintely use ES6 syntax.

Lifecycle Goals.

Working with Promises/Async stuff.

Think more critically about components.

Other

We will, of course, be doing much/all of this project remotely. In the past, we have worked together with our partners for at least 50% of the project. Now, since we don't have that luxury, we want to speak up about things we want to work together on (ex. we wanted to get some grid practice together but could probably do other CSS things seperately) and be smart about what we can split up. If there is anything we can do remotely, we should, but also be certain to fill the other in on what we've done. Pull request templates help with this, and if we do decide to work on something we should tell the other partner we're about to work on ______ so that both partners aren't working on the same thing, and so that we can explain our logic behind the code that we wrote so neither partner feels left in the dark for large sections of the codebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment