henvic

bun, I'm looking at you...

* IMHO there is not even any good reason to use an ORM whatsoever (unless, perhaps, you're building something very very very very very specific that needs to deal with very very very generic data).

If you take the biggest countries worldwide, this doesn't apply.

They changed their license from Apache recently. https://en.wikipedia.org/wiki/MinIO#Re-licensing

Don't want people writing code similar to yours? Don't publish anything. Force people to sign contracts before having contact with your source code.

I've resorted to something similar when making my tangerine juice: I put some water, ice, and a sugar cane "square" in the jar or cups first, and then go to squeeze the juice. By the time I'm over making lunch or dinner, the juice is ready without having to use a spoon to mix it.

Buying frozen solid means cleaning up your mixer. I also bet it's easier to lose some fiber.

Either way, the taste isn't the same as freshly made juice.

I'm from Brazil and loved tangerine/mandarin juice since when I was a kid. Now I've moved to the Netherlands and love it even more. How come, you may ask? In Brazil, we usually find tangerine pulps. Here, I buy fresh tangerine in the supermarket. Sure thing, it takes much longer to squeeze them and clean things up... but the taste is 5 times better.

There will be more: https://henvic.dev/posts/bitcoin/#scarcity

They'll find a way to convince more suckers to adopt the shitcoin.

Granted, I don't see Hershey's as much... and I've seen some times Lindt for way cheaper than I expected in the street market, but even so I had no idea...

I'd argue that needing this enums safety so bad that you go out of your way to create a struct with a protected field also lies in the same category of something you need that is mostly in the theoretical realm too.

Don't get me wrong, sometimes you want that kind of protection indeed and it's easy to mess up if you need to add validation everywhere. However, most times you can get away with just rethinking your code.

More importantly, I think the downside of using variables rather than constants makes it less safe than the alternative of relying on you always having to do validation.

I think he's talking about a different Merlin engine, though:

https://en.wikipedia.org/wiki/SpaceX_Merlin

Of course he wants to draw attention, and that's fine. People understand he's acting, besides doing a professional work.

No. Gold standard has none of the properties you told. Fiat currency is a disaster and evil. Besides, it's also likely the only reason why cryptocurrency is drawing attention to anyone.

https://henvic.dev/posts/bitcoin/

This Monday they assigned a VIN, and called me to let me know that if I wanted there was a car waiting for me, and I could pick it up the next day. I had to refuse as it wasn't possible for me at the moment, and asked them for a later delivery date.

* I ordered the white Tesla Model 3 with white interior, and nothing else.

It seems people rush to publish version 1.0 (or 2.0, etc.) of their libraries, when they'd be better off just sticking with version 0.x.

It's not like that a package isn't ready for production because it is < 1.0. It might as well be. If you're an early adopter, I'd say that is even welcome: you're aware that its API might chance, that its quite new, etc. It gives more confidence than a package with version 7.x (at least in informing you that it's prone to changes, and allowing you to make an informed choice), IMHO.

I'd say: Tailscale.

I'd also add Kafka for integrating different systems/databases, etc.