Brittany Dionigi brittanydionigi

A sample UI/UX rubric for projects. Feel free to modify per-project as you see fit.

4 - User interface is intuitive and the instructor can easily use it on their own without guidance. Styling is consistent and call-to-action elements are obvious. The application provides the user with relevant feedback based on interactions.

3 - User interface is mostly intuitive, though the instructor might need some guidance on interactions. Styling is mostly consistent, but could use some clean up. Application may be missing some relevant feedback that would help guide the user.

2 - User interface demonstrates some effort, but is not intuitive and the instructor needs help figuring out how to use the application. Styling has several inconsistencies and it's sometimes unclear what elements a user can interact with. Application lacks useful feedback for the user.

1 - User interface does not demonstrate effort and is unintuitive. The instructor cannot use the application on their own. Styling is incon

A sample Workflow rubric for projects. Feel free to modify per-project as you see fit.

4 - Developer(s) make many small, atomic commits that clearly document the evolution of the application and do not contain irrelevant changesets that aren't reflected by the commit message. Commit messages are concise and consistent in syntax and tense. Developer(s) effectively use git branches and pull requests when applicable to incorporate changes into the application, and are not pushing directly to master. There are no instances where the developer(s) have committed source code that should be .gitignored. There are no instances of "dead" or commented-out code and debugger statements like console.log.

3 - Developer(s) make many small, atomic commits that document the evolution of the application but sometimes contain irrelevant changesets and inconsistent commit messages. Developer(s) use git branches and pull requests when applicable to incorporate changes into the application, and are not pushing fresh cha

Who is a senior engineer?

Someone who is...

consistently trying to help other developers improve through mentorship, community involvement or teaching opportunities
has the foresight to predict edge cases and trade-offs for solutions to technical problems
has experienced many failures and is able to recover from them quickly when they arise
can clearly articulate their knowledge and explain technical concepts in multiple ways
has confidence in admitting what they don't know and the ability to ask questions when they need help
has familiarity with common patterns of programming, application architecture and structure so they can easily navigate new technical environments and tools
knows how and when to refactor code without burning things to the ground (or knowing when to just burn things to the ground)

The Game of Life

Write some code that evolves generations through Conway's "game of life". The input will be a game board of cells, either alive (1) or dead (0).

The code should take this board and create a new board for the next generation based on the following rules:

Any live cell with fewer than two live neighbours dies (underpopulation)
Any live cell with two or three live neighbours lives on to

Example 1

Before

if (this.explode === 'no') {
  let playerImage = new Image();

  playerImage.src = 'assets/airplane.png';
  context.drawImage(
    playerImage,

Read/Review

Practice

Often times, you'll be jumping into a pre-existing codebase and working with other people's code rather than writing a fresh app from scratch on your own. Sometimes the code is poorly tested or documented, and the previous developers may have moved on and taken their domain knowledge with them.

Navigating other's code, especially when it's broken, can lead you down some frustrating rabbit holes. Having solid debugging skills and understanding error messages will make this part of your job much easier.

	{
	"short_name": "hotMark",
	"name": "Your Favorite MarkDown Previewer",
	"background_color": "#dcaffd",
	"theme_color": "#74c7fd",
	"display": "fullscreen",
	"icons": [
	{
	"src": "img/icon-48.png",
	"type": "image/png",

	// HTML SECTION

	<h1>Papa Turing's Pizza</h1>
	<h2>Review Your Order</h2>
	<ul id="order-details"></ul>
	<button id="submit-order">Place Order</button>


	// JAVASCRIPT SECTION

	// Given an array of categories and an array of trivia questions,
	// return an object that summarizes the number of questions in each
	// category and the average difficulty of those questions like so:
	{
	"Entertainment": {
	"numberOfQuestions": ?,
	"averageDifficulty": ?
	},
	"General_Knowledge": {
	"numberOfQuestions": ?,