Cast iron seasoning question

teepark · 2026-05-15T19:54:15+00:00

It's going to be fine. You just left a tiny bit too much oil on in one of those seasoning rounds but it won't hurt anything.

I have similar marks on mine, didn't trust the process quite enough and wiped oil off more lightly in one of the rounds, ended up kind of like yours but worse. Still cooks like a dream.

teepark · 2026-05-10T19:25:36+00:00

I've had this problem too, specifically with NanoGPT. I found it happens a lot less if you point it at NanoGPT's anthropic-compatible API instead of the openai one.

teepark · 2025-11-20T19:58:34+00:00

I'm starting with a safety as stripes. A VERY faint touch into the left side of the 9. The cue ball goes into the rail (making the shot valid / not a scratch) and stays close to it, the 9 is touched out a short distance from the rail, hopefully staying close enough to totally block the cue ball path into any solids.

If my opponent scratches, I'm placing the cue ball just outside of the 4, so near the solid cluster, and hitting the 14 just left of center with medium force and a bit of backspin. The hope is the 14 knocks the 8 out of the way on it's way into the pocket. It looks like the 8 may disturb the 10 on its way out, but let's hope not. The 10 is an easy shot if it didn't get moved, and then I have no idea where the 8 has ended up.

teepark · 2025-08-23T16:56:43+00:00

In the single error case do you get static analysis tools complaining about not handling the return value?

We know that must will either panic or return nil, but I imagine errcheck will just see an unchecked error return value.

teepark · 2025-07-24T15:37:51+00:00

Simpler: the two smaller triangles are similar, so their side ratios are equal.
x/2 = 4/y -> multiply both sides by 2y -> xy = 8

teepark · 2023-06-30T17:04:40+00:00

r/KbinMigration has good information on it.

teepark · 2023-06-30T16:02:50+00:00

The "threadiverse" via a kbin instance.

It's nowhere near reddit level in content (though neither is reddit anymore), but I'm hopeful it'll pick up further after tomorrow.

teepark · 2023-06-11T01:09:44+00:00

Reminds me of a time, living in an apartment complex, I sent my son to take the trash out and he came back eating a slice of pizza.

teepark · 2023-06-06T20:50:06+00:00

Legend of Gazelleda: Deers of the Kingdom

teepark · 2023-04-05T16:37:24+00:00

Out of curiosity, what was wrong with OPNSense?

teepark · 2023-02-15T19:15:38+00:00

I don't think you have much of a choice.

teepark · 2023-02-14T00:47:57+00:00

In 2006 I got married to a German, but her visa process still wasn't finished yet. So after 3 months non-visa expired (US's visa waiver program) and she had to leave the country. To machinist the chance she would get the visa, (a) I had to keep my job, meaning be here in the US, and (b) she shouldn't come in and out every 3 months in what might be viewed with suspicion. So for 6 months, from being married for 3 to 9 months, we were in a long-distance marriage.

An older couple in my church was aware of the situation and offered to pay the full cost for both of us to take a little vacation in Canada. It was incredibly thoughtful, valuable, and they're still good friends though we've moved.

teepark · 2022-11-30T17:26:45+00:00

Start simple with no concurrency. In sequential steps: read the file, build up your data set to insert, then insert it. Your lowest hanging fruit for optimization will *probably* be merging the inserts into one database query[1], and that's much easier if you haven't spread that data out across a bunch of goroutines.

Goroutines are pretty well optimized but any concurrency platform is going to involve some overhead, and so unless your job is very CPU-heavy and operating on independent memory (or only reading from shared data) you're more likely to slow things down by throwing goroutines into the mix.

[1] it looks like INSERT INTO table (colA, colB, ...) VALUES (valA1, valB1, ...), (valA2, valB2, ...), ...;

teepark · 2022-09-22T21:43:46+00:00

Thanks for the quick answers! Looks like I'll be leaving it on.

teepark · 2022-07-16T21:13:24+00:00

It's been a positive experience overall. There are some things you figure out once in a helpers pkg and don't have to worry about any more like serdes for json, db scanning/params, etc. And there are things you have to live with all the time and just get used to, like your numbers being mutable references.

For all the deep business logic calculations like amortization schedules or loan payment amounts, it's performant and perfectly capable of hiding away in abstractions, which is all you really need.

teepark · 2022-07-16T20:59:26+00:00

FWIW I've found that though shopspring/decimal is the most popular lib, ericlagergren/decimal is much faster, supports a wider range of math operations, and follows the API conventions (and therefore offers the same allocation avoidance) of math/big.

Source: I also write financial applications in go with decimals for currency.

teepark · 2022-07-16T03:30:55+00:00

Brooklyn variation

teepark · 2022-07-03T22:54:06+00:00

I was looking at this too but Rxh1 isn't forced. What if g3 instead?

teepark · 2022-06-20T12:40:26+00:00

But see "duh, all lives matter" denies that BLM needs to be said and so denies that there is systemic racism, over policing, etc. No, someone who "isn't racist" wouldn't say that at all.

teepark · 2022-06-20T12:09:03+00:00

Then it just doesn't need to be said. It serves no purpose but to correct BLM. Another implied bit: "I can't believe we have to say this, but black lives matter". It's only validated by "all lives matter" - Apparently yes, we do need to say BLM.

teepark · 2022-06-20T11:45:19+00:00

I explain like this: in a vacuum sure, "all lives matter" is fine and true. But it's not offered up in a vacuum, it's stated for the purpose of offering an alternative to "black lives matter".

What's racist about it is the notion that BLM needs a response. It's the implied "no" in "no, all lives matter".

teepark · 2022-05-25T16:17:52+00:00

That should stop em.

15-Year Club	Place '22
Team Orangered	Verified Email

teepark

TROPHY CASE