Skip to content

featherstonej/EnergyCodeChallenge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 

Repository files navigation

Instructions

  • You will need Visual Studio to complete challenges outlined below. We suggest you utilize one of the community editions provided at https://www.visualstudio.com/downloads/
  • Clone this repo to your local machine
  • Use it to create a new repo on GitHub under your own account (please don't use GitHub fork to accomplish this)
  • Complete the challenge below or provide an alternative representative sample of code or classes that is solely your work product. (If you maintain a github project where you are the sole contributor, please feel free to submit a link and description of what we should review in the repository.)
  • Send us an email with a link to your repo and any instructions or details you want to share about key features, performance optimizations or creative problem solving skills that they exemplify.

Also Energy Code Challenge

Please review the projects in the Challenge solution and perform the following tasks. Please feel free to be creative and simplify when possible.

  1. Add a PermissionSet class to hold a fixed list of 100 user permissions (i.e. perm1, perm2, ...). The PermissionSet should be able to serialize as a byte array.

  2. Add the ability for the BlobIO class to append and retrieve the new user permission class.

  3. Add a User class that serializes as a BlobIO and includes username, permissions, create date, timezone, and favorite color.

  4. Fix the bug causing the existing test to fail and add a new unit test to verify the functionality of steps 1 through 3.

  5. Add a web or api project with an endpoint that returns the user details when api/user/{username} is requested. The endpoint should generate random values on a new user if the username has not been previously requested but once retrieved, the same user properties should result from subsequent calls. Persistance beyond an app restart is not required.

  6. Provide a brief comment for each of the following:

    • Concept or element that was unfamiliar or unexpected

    • Constructive review or recommended improvement

    • Opportunity or future enhancement

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages