echindod @ echindod @programming.dev

Posts

0

Comments

50

Joined

2 yr. ago

I'm glad you bring up Google Books in this. Those lawsuits in the early teens about this issue are really important. But two things bother me: Google really won the case, but then basically abandoned the project. It's still there, but a shell of what it used to be. I wonder if the case may be, even though they won, they really lost. Or it could be Google just abandoning another project because they never cared about it.

I think AI for searching books like Google books would be an a amazing use case, and really, it is t that much different than what Google books is: an index of all of the published words. In fact, I can imagine AI being able to help you figure out if this book has the info you actually need from the book. That's not what GPT is, but one could make one that could do it.

I am torn. I am sort of a GPT may sayer, but on the other hand, is it really all that philosophically different than what humans do? I don't think it is materially different, but it is a little.

I am curious why you think that. I download Bandcamp files and place it on a home server, and I have never had any problems. It is conceivable that they have a tracker or some bull shit connected to it, but more than a little unlikely.

Bandcamp files play fine on non bandcamp-approved playing devices. This is a big win on my book.

Fish? I like fish.

What is it about go that doesn't feel good? I have this feeling myself.

I didn't enjoy parsing JSON with Go, and I the documentation sucked. But it was really really easy to stand up a simple API endpoint. I would have reached for go for the project I am currently working on, but it didn't have the libraries I needed. It's interesting.

I worked in an excavating company for a bit. One old crochety guy worked 12 hours every day running an excavator. A younger guy who had stake in the company (also drove an excavator), who never worked more than 8 in a day, looked at him and said: "Why do you only get half as much done, but it takes you twice as long?"

The young guy wasn't wrong. Being tired does slow you down. But yeah, a four day work week in construction, might slow the project down a bit. But they should just hire more people. And on top of that 6 hour days with additional staff would make the work go a lot faster.

And as Teams continue to downgrade it's markdown support, it is becoming less and less appealing. I hate that I can't add language tags to code block with the triple back ticks, but it turns some of my code snippets to emojis. What the fuck man?

Maybe it's because I have only ever been in free plan slack channe's, but I have never understood the appeal. Maybe it's the bots? I looked into making a teams bot, and it was a horrendous experience.

Your not wrong. But hot take: it's better than slack.

This is an interesting article. I don't know anything about kernel development, but I wonder if it's still true?

And sometimes coding habits are obtuse to people with different coding habits. These habits aren't bad per service, but can be difficult to grok.