jessekv

Generally speaking, UTC + localization works for past events, but not future ones (see sibling comments)

Pyrefly is better than ty for my use cases. Maybe ty will get there some day.

In the great lakes you have low-head dams keeping lampreys at bay:

https://publibrary.sec.usace.army.mil/api/download?id=52f6cb...

But oxygenation not really an advantage of low-head dams, when the dam is often contributing to the oxygen depletion in the first place. Free-flowing streams are typically adequately oxygenated.

Small dams raise the temp of the water and decrease the dissolved oxygen, so removing the dams can improve ecological resilience in a warming climate.

I like this analogy. Another one I have used is double-entry bookkeeping.

When learning kayaking you have to practice a water escape, I wish there was something similar for driver's ed in the Netherlands. Thinking about it is terrifying.

That device's legacy lives on and is still in active use, though the main customers are now cows:

https://www.dutchnews.nl/2021/05/rotterdam-floating-farm-cri...

Most likely the latter. Thousands of bikes, a hundred people, and more than thirty cars fall in to Amsterdam canals each year. "What to do if your car falls in the water" is part of driver's ed.

Very cool! Have you considered rendering clouds?

p.s. thanks to all those working this week :)

A tiny bit more context here:

https://github.com/nats-io/nats-server/discussions/3312#disc...

(I opened this discussion 2.5 years ago and get an email from github every once in a while ever since. I had given up hope TBH)

I hate to admit it, but flaky tests almost always highlight weaknesses in my software architecture.

And fixing a flaky test usually involves making the actual code more robust.

> Who tests the tests?

To me it's a bit like double entry bookkeeping. Two layers is valuable, but there's rapidly diminishing returns beyond two.

I think it's relative, right? That's how abstractions and interfaces work.

I can write a module with integration tests at the module level and unit tests on its functions.

I can now write an application that uses my module. From the perspective of my application, my module's integration tests look like unit tests.

My module might, for example, implicitly depend on the test suite of CPython, the C compiler, the QA at the chip fab. But I don't need to run those tests any more.

In your case you hope the in-memory database matches the production one enough that you can write fast isolated unit tests on your application logic. You can trust this works because something else unit-tested the in-memory database, and integration tested the db client against the various db backends.

My guess is the tunnel will become the preferred roosting spot for the bats.

> We once saw a comment in the generated code that said "I need some coffee".

B1M covered this. The video has a fun animation of the political history too:

https://www.theb1m.com/video/italys-12bn-bridge-mystery

Yep! But I don't.

I usually just use asyncpg.

Why is the first one needed?

Don't sprinters start with 4 limbs on the ground? The advantage of the 4 limbs seems to be gone by the second step.

Trail runners often run with poles on up or down hills. Not sure about top speed, but from experience the poles definitely help with endurance.

related: https://bdickason.com/posts/speed-is-the-killer-feature/

Sebastián Ramírez created FastAPI and SQLModel, and was an early adopter of Pydantic. Samuel Colvin created Pydantic.

At a smaller scale, the efficiencies gained from properly designing the system are not a major savings.

That said, if I had a garden with a big fountain I absolutely would try to model it in EPANET ;)

Just how fancy is your irrigation system?

I suppose it's correct to say EPANET competes with expensive commercial offerings, but it's actually available completely free:

https://www.epa.gov/water-research/epanet

I know someone who uses it to design clean drinking water distribution systems in rural communities in Central America. They would not be able to do what they do if they had to pay for an expensive commercial licence.

Desktop EPANET is still windows-only though, so having a browser version is pretty cool.

related: https://news.ycombinator.com/item?id=40757996

It would be a fun callback if the demo was a factorial server:

https://joearms.github.io/#2013-11-21%20My%20favorite%20Erla...