mdwhatcott

> There are real tigers in those woods.

Nice little nod (on a post about Golf) to Tiger Woods.

> Congrats to Mike...

It's actually Matt :)

[flagged]

From the episode: "You know, your own imagination is far more wonderful than any computer could ever be. You know why--you're a living human being, and a computer is just a machine. Human beings are far more wonderful than machines!" -Fred Rogers

I appreciate that a computer has become such a wonderful tool for realizing ideas that come from my imagination.

Very cool, thanks!

> "I build separate, small HTML pages for each “interaction” I want, then I let CSS transitions take over and I get something that feels better than its JS counterpart for way less work."

I'm not understanding how you are achieving the css transitions between what look like new page loads under the hood...Can you elaborate on how that works?

What exactly do you mean by "part of the same context"?

Best part: a go.mod with 0 dependencies!

Yeah, this advice doesn't hold up--even the OP mentions learning the clarinet, which is a B-flat instrument. I also play the clarinet and developed the same ability to detect each note by its timbre. I also think there is a kinesthetic element to each note--the way the instrument vibrates, the back-pressure or resistance you feel while playing, that becomes associated with the timbre the longer you play.

Also not a bad thing to remain childlike in some ways.

I knew it was too good to have been original.

To coin a phrase, "Go 2 considered harmful" :)

I likewise hope for Michael Fogleman's participation: https://github.com/fogleman?tab=repositories&q=advent

Check out a few problems from a previous year to get a feel for the difficulty. Generally, the puzzles get harder as the month progresses. Here's last year's calendar: https://adventofcode.com/2020

The lack of discipline doesn't scale even more than discipline.

> The other bit of good news is that you can't unknowingly ignore a returned error, like you can with an unchecked exception. The compiler will force you at a minimum to declare the error as _, and tools like errcheck do a good job of keeping you honest.

Actually, we unknowingly ignore returned errors much more often than we think, like when we call a function and opt out of assigning any of the return values to variables. Consider this function, which returns a single value (being an error).

    func Failure() error {...}

You can always choose to call an error-returning function without declaring any placeholder (`_`):

    Failure()

There are several commonly used functions that return errors that are regularly ignored. How about `io.Writer`?

    writer.Write([]byte("Hello")) // returns (n int, err error)

It's quite common to call that function without feeling a need to check on the bytes written or a possible error. Or, consider whether you consistently check the return values of `fmt.Println()`, which also returns `(n int, err error)`...

It was about 10 years ago that I read Norvig's "10 years" post: https://michaelwhatcott.com/10-years/

If you feel the global challenge is out of reach, you can setup a private leaderboard for you and anyone you give the 'join code' to, localizing competition and points to your own circle of "AoC" friends: http://adventofcode.com/2017/leaderboard/private

What are your requirements? I'm one of the owners of the GoConvey project and I'm happy to answer any of your questions about that project. Ginkgo and Goblin are great choices as well.