Git Product home page Git Product logo

statefarminscodingcompetition / 2023-statefarm-codingcompetition Goto Github PK

View Code? Open in Web Editor NEW
7.0 6.0 51.0 347 KB

Welcome to the 2023 State Farm Coding Competition. If you have questions during the coding competition, please contact [email protected] or you can submit an issue through GitHub.

Home Page: https://codingcompetition.statefarm.com

License: Apache License 2.0

Java 49.68% JavaScript 23.28% Python 27.04%
2023 coding competition state-farm

2023-statefarm-codingcompetition's Introduction

2023 State Farm Coding Competition - Round 1 and 2

This is the GitHub project for the 2023 State Farm Coding Competition Round 1 and 2. This will be the same project you'll use once Round 1 begins.

Please be sure to read this entire document PRIOR to moving into one of the language-specific folders.

Change Log:

Getting Started

Selecting a Project Folder

Based on the language you are the most comfortable using, pick one of the following folders to begin:

Inside each folder is the specific instructions for that language for:

  • What software you need to build and run the project
  • Commands for running unit tests
  • Considerations for that language

Use Visual Studio Code (VSCode)

We recommend using VSCode, our editor of choice. Several reasons are:

  • Support for extensions that we'll recommend for each project to reduce time spent on environment setup and syntax issues
  • Great support and performance across multiple platforms
  • What we used to setup and test these projects

More on using other editors below.

Git

You will need to have Git installed on your machine. It is supported on many platforms. For more on Git and VSCode, see this guide. For other editors, you will need to search around the Internet.

Considerations

Using Editors Other Than VSCode

We primarily use and heavily recommend VSCode for this competition, especially if you run into any problems relating to software and your workstation. We cannot help with every issue that may arise, but by using VSCode, we can hopefully get to a quicker solution for certain edge cases (environment not setup correctly for example).

We also cannot guarantee that these projects will work with other editors. Your mileage may vary.

Plan to Carry This Project into Round 2

Plan accordingly to use this project for round 2 of the competition. You'll want to make sure your code is reusable and easy to understand, tweak, and maintain. Otherwise, you may have a difficult time with the round 2 problem set.

Dealing with new line characters

https://help.github.com/articles/dealing-with-line-endings/

Questions?

E-mail [email protected], or to post a public question or report a problem, open an issue.

Feedback

At the ends of Round 1 and 2, we need you to fill out FEEDBACK.md. It includes a few questions such as team name, number of unit tests passed, any notable characteristics. Please

2023-statefarm-codingcompetition's People

Contributors

cschwirian avatar j1411 avatar tanman987 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

2023-statefarm-codingcompetition's Issues

Contradictory method documentation

The method get_top_three_months_with_highest_num_of_claims_desc and return hint in the documentation (three strings of month and year, descending order of highest claims) implies that we need to find the months with the most number of claims, but the method description states Gets the top three months with the highest total claim cost. Do we need to find the three months with the most disasters or with the highest claim cost?

Most spoken language method

For def get_most_spoken_agent_language_by_state(self, state):

Do we account for secondary languages as well?

Java - Accuracy issues for Estimate Cost

the getTotalClaimCostForDisaster method is of float data type so accuracy does not match expected value in TestSet2 so test4_getTotalClaimCostForDisaster fails for getTotalClaimCostForDisaster(56).

image

I tried changing estimate_cost data type in Claim.java and the return types of the methods that depend on it from Float to Double. This fixes the test and it works expected

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.