News for hackers. Stuff that matters.

mdwhatcott

Re:Golfing Is Not Rowing on Monday December 29, 2025 @11:31AM (#46422263)
> There are real tigers in those woods.

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

Re:Next Steps for the Caddy Project Maintainership on Wednesday October 15, 2025 @10:36PM (#45600845)
> Congrats to Mike...

It's actually Matt :)

Re:Flattening Rust's Learning Curve on Tuesday May 13, 2025 @09:17PM (#43979711)
If a language needs an article like this, absolutely begging people to bite the bullet to learn it, maybe that's a language design smell.

Disclaimer: I haven't taken the time to learn Rust so maybe don't take this too seriously..

Re:Computers and Mice – Mister Rogers Neighborhood on Saturday March 15, 2025 @12:42PM (#43373603)
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.

Re:Building Websites with Lots of Little HTML Pages on Wednesday March 12, 2025 @05:59PM (#43348068)
Very cool, thanks!
Re:Building Websites with Lots of Little HTML Pages on Wednesday March 12, 2025 @05:16PM (#43347762)
> "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?

Re:Building Websites with Lots of Little HTML Pages on Wednesday March 12, 2025 @05:14PM (#43347746)
What exactly do you mean by "part of the same context"?
Re:Show HN: A Database Written in Golang on Thursday February 27, 2025 @12:32AM (#43191647)
Best part: a go.mod with 0 dependencies!
Re:Learn Perfect Pitch in 15 years on Monday December 02, 2024 @07:30PM (#42301899)
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.
Re:Starship will attempt a launch this weekend on Tuesday November 14, 2023 @10:18AM (#38264294)
Also not a bad thing to remain childlike in some ways.
Re:Backward Compatibility, Go 1.21, and Go 2 on Monday August 14, 2023 @03:51PM (#37125949)
I knew it was too good to have been original.
Re:Backward Compatibility, Go 1.21, and Go 2 on Monday August 14, 2023 @01:48PM (#37124134)
To coin a phrase, "Go 2 considered harmful" :)
Re:Advent of Code 2021 on Saturday November 20, 2021 @11:26PM (#29294188)
I likewise hope for Michael Fogleman's participation: https://github.com/fogleman?tab=repositories&q=advent
Re:Advent of Code 2021 on Saturday November 20, 2021 @11:24PM (#29294179)
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
Re:Discipline Doesn’t Scale on Tuesday October 20, 2020 @09:14PM (#24843968)
The lack of discipline doesn't scale even more than discipline.
Re:Exploring Error Handling Patterns in Go on Thursday August 16, 2018 @11:42AM (#17775622)
> 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)`...
Re:Teach Yourself Programming in Ten Years (1998) on Tuesday March 13, 2018 @10:26AM (#16576336)
It was about 10 years ago that I read Norvig's "10 years" post: https://michaelwhatcott.com/10-years/
Re:Advent of Code 2017 on Thursday November 30, 2017 @10:35AM (#15816492)
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
Re:A curated list of Go frameworks, libraries and software on Saturday July 12, 2014 @04:21PM (#8025682)
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.