Been nerd sniped recently so am working on a Rust version of markdownlint-cli2. I'm tired of having a node dependency in my projects and this seems like a constrained enough problem space that I'll actually get around to doing it.

10-15 hours is NUTS. I do mine by hand every year and I can get them done in about 3 hours. I would say my taxes are nontrivial thought certainly not super complicated (no K1s)

This has been my primary objection with Go, as well. I wonder if it's just a lack of practice and that I'd eventually git gud, but I find it so hard to flow through code to get a general idea of what's going on. It's basically impossible to use code "paragraphs" to separate logical groupings of functionality because of the `if err != nil` blocks, and leads to a very choppy reading experience. With any non-trivial logic, I've found Go to be detrimental to my understanding of what's going on.

This seems strange for me, though everyone jumps on this. Most Go projects will use something like:

Handle(err)

which may take a line, but isn't the 3 lines everyone refers to, and often has a lot of extra logic.

I did a similar experiment on myself. For songs I knew very well on good headphones, I could reliably distinguish up to 320 kbps on MP3 and 256 kbps AAC from the lossless copy. For songs I didn’t know as well, 128 kbps AAC was usually transparent.

My takeaway from the experience was that the bitrate didn’t really matter above 128 Kbps AAC. This was me paying super close attention and trying to find flaws in the encoding, not actually listening to music. I periodically rerun the test in myself as I get better equipment (laptop DACs are quite good now, for example) and get similar results. Age will be a limiting factor soon as it takes my hearing.

Ha, and I’m the opposite in a different direction. I _hate_ positive feedback. What motivates me is failure and a fear of failure. I go out of my way to downplay accomplishments but will talk your ear off about how and why I failed or almost failed or knew about a failure condition.

Maybe the actual takeaway is to figure out what kind of feedback a child responds best to and use that most of the time. You know, paying attention to the kid.

I would agree in principle, but from experience it seems people are less interested in the energy of the city as they age and acquire more things, and prioritize building their own space around them instead of utilizing the city around them.

Bingo. To someone like me, the "energy of the city" is a severe down-side. I don't want "energy" in my life. I don't care about "amenities". I don't want to hear my neighbors music, or smell their cooking, or deal with their drama. Where I live now, working from home, I could go an entire week without seeing another living soul, and it's wonderful. I value the ability to sit on my porch with a beer, hear nothing but birds and crickets and the stream behind my property gurgling away, smell nothing but the trees, and see nothing but the sunset.

The great appeal of San Francisco is that you don’t have to think about what you’re going to wear at least 300 days of the year. If you’re outdoorsy at all it’s very hard to go to the rest of the US and feel trapped inside. Unfortunately for me, family moved there after I moved to be close on the west coast, so I get to experience that 2 weeks every year.

I would also dispute “no natural disasters”. There are serious winter events in those regions (and crazy floods depending on where you are in the Midwest) that happen basically yearly.

I don’t think any part of the world is without significant tradeoffs, you just have to find the ones that matter to you.

Nothing is without trade-offs. We hardly notice the ones that come naturally to us.

I was lucky enough to dive Alexey and his mother 15 or so years ago.

I was terrified of swimming in open water so only joined the group for a deep dive once and my memories are mostly people talking and laughing on the boat, but I remember feeling crazy when people talked about air control. What do you mean I have to exhale into my mask at a certain depth? And I should inhale it back as I’m coming up? I need to take _too big_ of a breath on the surface so I can distribute it as the pressure increases?

With just a little coaching from Alexey’s mother and some encouragement from my family, a high school kid who couldn’t hold his breathe for much more than a minute spent almost 2 minutes underwater and dove to 19 meters on his first day.

I’m still terrified of deep water, but I gained a respect for the “weird” sports out there. It’s often a bunch of people just trying to have fun, and sometimes they turn out to be really, really good at what they do.

You are using gender to mean both sex and gender. You are assigned a biological sex by… biology. You get to choose your own gender.

Well, fair enough, that concept has never been discussed during my education(that ended 20 years ago), so I am not in the loop except from what I have seen online about it. It seems it got a bit traction in the US, in Europe is relatively unheard of as of yet.

The sunk cost fallacy is real.

Most important to me when I started tinkering with him was the speed/feature tradeoff, and portability. I was working on 7 machines at one point doing pretty quick edits of config files and Python scripts, so launch speed and availability across different environments drive me to vim.

Now there are alternatives, but back in 2015 these were all in their infancy. And now I _know_ vim and it keep adding more features. The incremental cost of adding language server support is much less than the cost of learning how to move around VSCode, so my (neo)vim config keeps growing slowly but surely