Fork me on GitHub
#adventofcode
<
2020-12-06
>
Vincent Cantin05:12:56

Good morning !

😁 4
fingertoe05:12:23

Hello! Today’s problem was pretty straightforward.. I am tied with the amount of problems I finished last year.. Not close to burning out.. I wonder if it is going easy on us this year?

Vincent Cantin05:12:26

I am awaiting the difficult problems like a surfer awaiting its wave.

alekszelark05:12:20

You can pick one from the last year ^_^

👍 1
💯 1
Vincent Cantin06:12:36

I will keep them for January.

mchampine05:12:36

Agree! #6 usually starts ramping way up.

kenj05:12:25

why give us a difficult problem on the weekend when you can save it for a weekday…

😆 2
Vincent Cantin06:12:17

During the first 1 min 30, I was staring at a blank page, waiting for the page to load.

plexus06:12:10

AoC really starts the first time you add

(set! *unchecked-math* :warn-on-boxed)
(set! *warn-on-reflection* true)
to a namespace

😏 3
👟 1
1
Vincent Cantin06:12:33

I like @dos’s solution, which did not separate the input loading from the processing for the solution. It might be faster to type in that way.

james06:12:21

This is the first year I'm (seriously) trying to do this. Does it usually get harder day by day?

james06:12:36

(Today's puzzle was pretty easy, but if they're going to get difficult I might not have time to see it through.)

markw06:12:57

Problems have been surprisingly simple so far this year

markw06:12:13

Last year for me, was by far the most difficult of them all

alekszelark06:12:10

That’s probably because we’re going to vacation 😃

😄 1
markw06:12:36

that or he’s lulling us into complacency just before dropping the hammer tomorrow

markw06:12:57

oh you got work Monday morning? Hope you remember A* search

😁 4
plexus06:12:40

I skipped AoC last year because the year before I ended up spending sometimes multiple hours on a single solution. If it gets like that again I'm out, but a bit more challenging than today's would be nice too 🙂

markw06:12:09

I’ve done them since 2015, finished most but not all of them.. Except last year i bailed very early

plexus06:12:34

Today's video: https://www.youtube.com/watch?v=b0a5siw85N4&amp;feature=youtu.be I also talk a bit about the different ways that people solved yesterday's puzzle

👍 2
plexus06:12:34

Many thanks to folks who dropped into the live chats or left comments!

Vincent Cantin07:12:42

Let me know if I leave too many comments during the streaming 😅 I have a hard time holding them while excited by the contest.

plexus07:12:58

All good, it's nice to see some activity :)

markw06:12:37

they definitely get difficult and I was spending hours on problems routinely, but i’m not a fast solver

markw06:12:34

last year by like day 14 you had implemented a VM for a made up language, and then implemented pong using that language

james06:12:39

I'm not a fast solver either, and also I'm doing them in Clojure, which I don't really know, so I'm extra slow.

markw06:12:11

i know the feeling… i’m trying to go back and do them in Go after I finish in Clojure, and it is … painful (i don’t know Go)

markw06:12:21

lots of typing

Stuart19:12:27

I've learnt a few neat functions from looking at you guys solution so far this year 🙂

💯 1
tws22:12:58

In case you haven’t seen it, I highly recommend being well versed in all these base functions, really helps to know what’s possible. https://clojure.org/api/cheatsheet

👍 1
st3fan22:12:35

I am doing 2015 in parallel 😕

Vincent Cantin06:12:24

split keyboard? 😉