Meet the Survey Says Team

Who We Are

We are Max Barker and Eli Parker, and we are students at the University of Utah. We are a part of this course together.

Survey Says is coursework for CS 3550 at the U of U. Our goal is to learn server-side web development with ASP.NET Core MVC by building a working survey application end to end.

Team name
EPMB
Course
CS 3550 - Web Development I
Institution
University of Utah
Team formed
How we divide the work
Equally - both of us contribute to every part of the application.
Project
Survey Says, a web application for creating and answering surveys
Repository
Survey Says source code on GitHub

Team Member Profiles

Eli Parker

A head-shot of Eli smiling in front of some foliage
Eli Parker, co-creator of Survey Says.

I'm a senior at the U and I work part time as a Software Engineer for a startup called Ambrook. I'm interested in building systems that are simple and intuitive for the people who interface with them.

Major
Computer Science
GitHub
Eli Parker on GitHub

Skills and Technical Interests

  • Frontend development (React, TypeScript, GraphQL)
  • Systems design (APIs, architecture, data structures)
  • People and communication

Learning Goals for This Project

  • Create a portfolio project which I can post to my website
  • Learn more about backend web systems & deployment

Max Barker

A headshot of Max smiling in front of a white background
Max Barker, co-creator of Survey Says.

I'm a junior studying Software Development at the U. I got into computing because I enjoyed solving programming challenges, then realized how many layers of the field there were to explore. I especially enjoy learning how computers and software work under the hood.

Major
Software Development
GitHub
Max Barker on GitHub

Skills and Technical Interests

  • Low-level programming with C
  • Linux and how software works under the hood
  • Computing history

Learning Goals for This Project

  • Better understand how web servers work
  • Gain experience building a backend
  • Practice working with an AI coding agent for the first time

How We Work Together

We meet roughly twice a week to talk. We sometimes pair on issues but mostly utilize GitHub pull requests to understand the code we push out.

Our Workflow for Every Change

  1. Make the changes on a new branch, formatted name/purpose-of-change
  2. Make a pull request for those changes, with a description which notes the purpose of the change and any areas of note for the reviewer.
  3. The change goes through review cycle(s) which allow the other person to understand the changes and agree on formatting, purpose, etc.
  4. The change is approved and merged!

Shared Team Expectations

Communicate early and often
We want to understand problems and help create solutions together.
Ownership
All code/writing PR'd by you is owned/understood/defended by you, even if it's AI generated.
Teamwork
We seek to help each other learn and grow as developers.