News

Travis CI set up notes -- how to set up the Travis Continuous Integration server for building React apps and deploying to Firebase
Quick, React! -- my first draft at a modern React tutorial. Ready for review. Post questions, bugs, requests, on Piazza.
Learn React Task -- a personal activity to help everyone learn (or practice) building React apps the modern way
React: Old vs New -- a demonstration of how functional React is simpler to code than old React.
First Demo Task -- due Tuesday
Team React Setup Task and Four-Panel Storyboard Task -- What each team needs to have done before the second class!
Day One Task -- What each team needs to be ready to present on the first class!

When

TTh 11am - 12:20am

Where

Tech A110

Who

Chris Riesbeck

Resources

EECS 394 FAQ

How to I get access to the shared documents?

See these instructions.

Why did you return my email?

There are 3 rules for EECS 394 emails:

The first and second rules are so I can find and file your emails.

The third rule is so everyone knows you emailed me, I know everyone knows, and everyone sees my reply.

Note: if you create a Google email group for team, don't forget to add me! Otherwise my reply-all will bounce.

Emails that fail to do the above will be returned for repair.

The only exception to the CC rule is when there's some personal or inter-personal issue that you don't want the team to know about. These are very rare.

If you ask a really good question, I'm likely to tell you to re-ask it in Piazza.

Where did those team names come from?

In fall, the clients for EECS 394 come from the MPD2 program. Those students were traditionally organized into 6 teams: Blue, Green, Orange, Purple, Red, and Yellow. For simplicity, EECS 394 teams are given the same names as their clients.

I have no idea where the names came from in MPD2.