# About Advent of Code
Below are copied from Eric Wastl's introduction to Advent of Code.
Hi! I'm Eric Wastl (opens new window). I make Advent of Code. I hope you like it! I also made Vanilla JS (opens new window), PHP Sadness (opens new window), and lots of other things (opens new window). You can find me on Twitter (opens new window) and GitHub (opens new window).
Advent of Code is an Advent calendar of small programming puzzles for a variety of skill sets and skill levels that can be solved in any (opens new window) programming language you like. People use them as a speed contest (opens new window), interview (opens new window) prep (opens new window), company training (opens new window), university (opens new window) coursework (opens new window), practice (opens new window) problems (opens new window), or to challenge each other (opens new window).
You don't need a computer science background to participate - just a little programming knowledge and some problem solving skills (opens new window) will get you pretty far. Nor do you need a fancy computer; every problem has a solution that completes in at most 15 seconds on ten-year-old hardware.
If you'd like to support Advent of Code, you can do so indirectly by helping to [Share] it with others, or directly via PayPal or Coinbase (opens new window).
Advent of Code is a registered trademark in the United States.
# General Tips
If you get stuck, try your solution against the examples given in the puzzle; you should get the same answers. If not, re-read the description. Did you misunderstand something? Is your program doing something you don't expect? After the examples work, if your answer still isn't correct, build some test cases for which you can verify the answer by hand and see if those work with your program. Make sure you have the entire puzzle input. If you're still stuck, maybe ask a friend for help, or come back to the puzzle later. You can also ask for hints in the subreddit (opens new window).
# Frequently Asked Questions
Why was this puzzle so easy / hard? The difficulty and subject matter varies throughout each event. Very generally, the puzzles get more difficult over time, but your specific skillset will make each puzzle significantly easier or harder for you than someone else. Making puzzles is tricky (opens new window).
Why do the puzzles unlock at midnight EST/UTC-5? Because that's when I can consistently be available to make sure everything is working. I also have a family, a day job, and even need sleep occasionally. If you can't participate at midnight, that's not a problem; many people use private leaderboards (opens new window) to compete with people in their area.
How does authentication work? Advent of Code uses OAuth (opens new window) to confirm your identity through other services. When you log in, you only ever give your credentials to that service - never to Advent of Code. Then, the service you use tells the Advent of Code servers that you're really you. In general, this reveals no information about you beyond what is already public; here are examples from Reddit (opens new window) and GitHub (opens new window). Advent of Code will remember your unique ID, names, URL, and image from the service you use to authenticate.
I find the text on the site hard to read. Is there a high contrast mode? There is a high contrast alternate stylesheet. Firefox supports these by default (View -> Page Style -> High Contrast).
I have a puzzle idea! Can I send it to you? Please don't. Because of legal issues like copyright and attribution, I don't accept puzzle ideas, and I won't even read your email if it looks like one just in case I use parts of it by accident.
Can I stream my solution? Please try to avoid giving away the solution while people are competing. If a puzzle's global daily leaderboard isn't full yet and you're likely to get points, please wait to stream/post your solution until after that leaderboard is full. If you are unlikely to get points or the daily leaderboard is already full for the puzzle you're working on, streaming is fine.
Puzzles, Code, & Design: Eric Wastl (opens new window)
- Tim Giannetti (opens new window)
- Ben Lucek
- Andrew Skalski