To be fair: the fictional timezone PyTZ ends up using is meant to approximate the weird timezone Amsterdam used up to 1937, but even then: why does it default to ancient data? It's a disaster waiting to happen.

What happened to your legs?!?

Make sure the value of your product is not in the code, but in the people (you). If you have the knowledge, the customer service, and the community, the thief has no good way of competing with you.

If the only value of your startup idea is in source code, is is not a good candidate for open source.

I really like the markdown-first approach here. Jupyter is code-first, which leads to script-like code with little explanation. Your approach seems far more suitable for tutorials, documentation and reporting.

I'd love an #obsidianMD plugin that does this. :)

Does that really matter? If the end result is good, I don't really care much about the process that got you there.

Sure, there's lots of low-effort projects being published. AI did not start they, it just made them look better. Either way, you still need to look at the idea behind it.

Either that, or post a wrong answer, per Cunningham's law.

It is said that Eve doomed humanity's fate for an apple. It's a good thing that fresh stroopwafels don't grow on trees.

Any ideas how it performs relative to other models?

Tickets are a mixture of Dutch and English, as they often contain info provided by Dutch-speaking users. Code is English all the way. This leaves us the option of outsourcing future work.

I paid €3.49 for a 24 eggs. Northwest Europe. Seems like bird flu has skipped us for now. Farmers are under stringent preventative regulations though.

I believe the US agricultural sector would call those regulations gubernatorial overreach.

I similarly dislike "to be fair", to be honest.

You really can. Instead of iterating over foo's, you'd iterate over Result<foo>

Most iterator fns handle that just fine. For example: the sum of a result returns the first error, or Ok(...) if there were no errors.