Code Bash Competition – Feb. 7

This event has been cancelled.

Code Bash Logo2025 Code Bash

Team-Based Coding Competition

Friday, February 7, 2025 | 9 a.m. – 2 p.m.

Scott Community College Urban Campus
101 W 3rd St, Davenport, IA 52801

 

Are you passionate about IT? Now’s your chance to show off your coding skills at Code Bash! This exciting team-based competition invites area high school students to create innovative web or mobile applications. Whether you're a coding novice or an experienced programmer, there's a place for you. We've split the contest into two categories: "bits" for beginners and "bytes" for seasoned coders. Each school can assemble up to one team per category, with a maximum of ten students per team.

Help Along the Way

Leading up to the event, students can get help with any aspect of application development, from coding queries to design dilemmas. EICC IT students and high school club advisors will be on stand-by to address team inquiries via email at codebashFREEEICC.

Drumroll, Please

This year’s Code Bash theme is Robot Revolution! The possibilities are endless, and teams are encouraged to think outside of the box and create applications that leave a lasting impression.

Teams will develop a mobile phone and/or tablet application. Permitted platforms include and are limited to Google Android or Apple iOS™.

Specifications

  • The team will create a mobile application. The team will create the application in a platform of the teams' choosing from the list of platforms designated in the technical specifications.
  • The projects may be cross-platform compatible between Google’s Android or Apple iOS®.
  • The application may not be deployed as a web application, delivered over HTTP.
  • The application must be installed on one of the team’s mobile devices.
  • The team must demonstrate the application from the team’s mobile device for presentation to the judges at the event. Projection equipment may be used.
  • The application need not be available for download from a digital-distribution multimedia content service, such as Google Play® or Apple App Store®.
  • Must be easy/intuitive to use and function in a logical manner.
  • Must use styles that are consistent throughout the application, including:
    • The use of capitalization. (E.g., title case vs. sentence case)
    • The use of punctuation. (E.g., consistent use/no use of colons on labels)
    • Error messages must appear in a consistent location and style.
    • Layout/spacing. (E.g., the space between a field label and input control)
    • Descriptive metadata titles and descriptions.
    • Must adhere to industry best practices.
    • Form controls that are not available must be hidden--no use of inactive controls.

It is the policy of Eastern Iowa Community Colleges to comply with state and federal copyright law. Federal law pertaining to copyright, as contained within the United States Code, is available at https://www.copyright.gov/title17/title17.pdf. Participant(s) will be disqualified for violations of the guidelines.

The team will create a client-side web application. The team is provided with the opportunity to design, build, and present a working web application.

Specifications

  • Team name and team member names must be included on the website. This information can be included in any format and location.
  • Teams may make use of an application programming interface (API).
  • The web application must be available for viewing on the day of the event.
  • Must be easy/intuitive to use and function in a logical manner.
  • Must use styles that are consistent throughout the application and within the associated website, including:
    • The use of capitalization. (E.g., title case vs. sentence case)
    • The use of punctuation. (E.g., consistent use/no use of colons on labels)
    • Error messages must appear in a consistent location and style.
    • Consistent use of any web document notations. (E.g., PDF, DOC, etc.)
    • Layout/spacing. (E.g., the space between a field label and input control)
    • Descriptive metadata titles and descriptions.
    • Must adhere to industry best practices.
    • Form controls that are not available must be hidden. No use of inactive controls.
  • Every web page in the application must have one or more links, or control buttons, that allow a user to navigate back and forth within the application without having to use the back button or other browser navigation functionality.
  • The HTML code in all web applications must be valid via a reputable validation technique, such as W3C.
  • Form fields must be validated to ensure required fields are completed, numeric fields have numeric data, and data input is properly formatted. (E.g., date, email address)

It is the policy of Eastern Iowa Community Colleges to comply with state and federal copyright law. Federal law pertaining to copyright, as contained within the United States Code, is available at https://www.copyright.gov/title17/title17.pdf. Participant(s) will be disqualified for violations of the guidelines.

Competition Day

On competition day, each team must bring their project for evaluation. All necessary hardware to operate the web or mobile application should be provided. What's more, students will have the opportunity to network with like-minded peers from other schools.

Here’s a quick-glance agenda:

  • 9 a.m. – Arrive, set up application
  • 10 a.m. – Judging
  • 12 p.m. – Lunch
  • 1 p.m. – Awards presentation

Prizes will be awarded for 1st, 2nd, and 3rd place, for each category. Evaluation will be based on the following criteria:

Competency 4 3 2 1
Design Aesthetics — The application’s design is visually appealing, using appropriate colors, fonts, and spacing. Excellent choice of color, font, and spacing. Good choice of color, font, and spacing. Inconsistent choice of color, font, and spacing. Poor choice of color, font, and spacing, making it challenging for the visually impaired.
Functionality — Does the project do its intended purpose? All features work exactly as intended during the demonstration. Runs but one feature does not work during demo. More than one feature does not work during demo. The application fails to perform.
Ease of Use — Application is intuitive, focuses on the needs of your target audience, has offline access, and prioritizes security. The application is very user friendly, by being intuitive and focusing on user needs. Also allows for offline access and prioritizes security. The application is mostly user friendly, by being intuitive and focusing on user needs. May potentially have the capability of adding offline access. Has low security risks. The application poses a lot of challenges to users, is somewhat intuitive, meets some user needs, has no offline access, and has high security risks. The application is not user friendly or intuitive, does not focus on user needs, has no offline access, and does not prioritize security risks.
Creativity — Is the project an original idea? The project shows originality in all areas by being unique in its design and user interaction. The project shows originality in most areas by being unique in most of its design and user interaction. The project shows little originality by not being unique in most of its design and user interaction. The project is not at all original.
Professionalism — Did the team conduct themselves in a professional manner? All team members are respectful to judges and other team members and have a positive attitude. Are focused on the task at hand. Most of the team members are respectful to judges and other team members. Have a mostly positive attitude and are focused on the task at hand. Some of the team members are not respectful to judges and other team members. Have a somewhat positive attitude. Some are not focused on the task at hand. All team members are not respectful to judges and other team members and do not have a positive attitude. Are not focused on the task at hand.
Communication — Could the team explain their project clearly? Project was clearly explained in a concise way and was easy to understand. The presenter was coherent, and information was presented in a logical sequence. Project was explained concisely but needed some clarification. The presenter was coherent, and information was presented mostly in a logical sequence. Project was explained using a lot of time and also needed lot of clarification. The presenter was somewhat coherent, but information was not presented in a logical sequence. Project was not explained clearly and was not understood. The presenter was not coherent, and information was presented in a random sequence.

Code of Conduct

EICC is committed to accepting all participants for who they are, and providing an environment where everyone with a passion for technology is comfortable, safe, and included. To achieve this goal, we require your participation abides the code of conduct during all EICC events, and by encouraging your teammates to do the same.

We want everyone to have a good time at the Code Bash. What is accepted or tolerated in your
culture may be different from the other teams at the Code Bash. Be respectful of differences both
with your actions and your words.

We treat everyone as equal human beings. Please reach out to people who may be excluded or
objectified due to their gender, nationality, culture, religion, belief, disability, or sexual
orientation, and try to include them.

Do’s:

  • Enjoy being around new people.
  • Start conversations with members from other teams.
  • Be respectful.
  • Adjust your behavior if you are making someone feel uncomfortable.

Don’ts:

  • Make offensive verbal or written jokes, remarks or gestures related to gender, sexual orientation, disability, physical appearance, body size, ethnicity, or religion, including through online means such as WhatsApp groups or Wi-Fi hotspot names.
  • Harass or give anyone unwanted attention, for example by following them, calling out their
    name or photographing them when this is unwanted.
  • Touch anyone who does not want it.
  • Exclude anyone because of who they are, for example their gender, sexual orientation,
    disability, physical appearance, body size, ethnicity, or religion.

 

We will not tolerate intimidation, harassment, or any abusive, discriminatory, or derogatory behavior at EICC. The consequence of such behavior, depending on its severity, will range from a warning to disqualification from the event.

 

  1. All projects must be completed by the time of the event.
  2. All teams must provide hardware to run their project.
  3. All team members must be enrolled in the school their team represents.
  4. All team members must be present on the day of the event. In cases of emergencies or illnesses, all absences should communicated.
  5. Code can only be written by student team members.
  6. Each team must have a school mentor or advisor.
  7. Each school is allowed two teams.
  8. Each team can have up to 10 students.
  9. Plagiarism will not be permitted.
  10. Judging is based off of rubric.
  11. Multiple submissions cannot be accepted.
  12. All work must be original.

Code Bash Sponsorship

Are you or your organization interested in sponsoring Code Bash? We'd love your support and have several ways to get involved. Gain recognition in printed event materials. Showcase your brand with a vendor table. Contribute financially toward competitor t-shirts. Donate items or services to be awarded as prizes. The opportunities are endless.

To get started, please email codebashFREEEICC or call 563-336-5226. We look forward to partnering with you!