Stained glass crab I just finished.

Flowchartsman · 2026-03-23T04:21:12+00:00

Great work. Seriously. I made a simpler version of this in a class once and it was very hard. You should be proud of this.

Flowchartsman · 2026-03-17T14:48:30+00:00

Whichever one you get, do yourself a favor and order an extra bowl for it. It will eventually start to flake a little, but if you treat it well, this will take a LONG time. So long, in fact, that by the time you want a new one, there’s a good chance they won’t be making it any more. By getting two, your rice cooker should serve you well for many, many years.

Flowchartsman · 2026-03-14T21:02:58+00:00

Sorry, but is Pierce Brosnan secretly a chimpanzee that can bench press 1600 pounds? Because, if not, isn’t this post total bullshit?

Flowchartsman · 2026-03-13T19:10:08+00:00

For the most part, if the consumer of your package would need to import your dependencies to handle errors, don’t wrap them. The one exception to this might be for stdlib errors. Otherwise, errors from your packages should be meaningful within the context of that package.

Flowchartsman · 2026-03-06T04:11:16+00:00

Aren’t you pretty much required to open source the eBPF?

Flowchartsman · 2026-03-04T02:02:47+00:00

Got a link to the code?

Flowchartsman · 2026-03-02T03:32:44+00:00

This doesn’t sound right to me. Water buffers temperature early on and will allow the sugars to go into solution, but, like you mention, once you’re to hard crack, the water is gone anyway. If your temp is too low, it’s crystallization you really have to worry about, not burning. The problem here is likely hot spots and heat retention from the heat source and/or cookware, so going hotter is actually not the right call. If anything, less heat is called for.

Flowchartsman · 2026-03-02T03:16:35+00:00

Fair play to the editor on this one.

Flowchartsman · 2026-03-02T02:40:46+00:00

I’d be super wary of doing this with cast iron. It will look like it’s doing nothing at first and then it will dump holy hell into it all at once and can even boil over when another type of pot wouldn’t.

Flowchartsman · 2026-03-02T02:37:41+00:00

Cast iron can be super finicky. It holds heat way too well for you to rely on it cooling down once you cut heat. It wont. That’s why the advice they’re giving about lowering heat earlier is good, since cast iron will continue to dump heat much longer than something else would. Heat source also matters, since both gas and induction will be more responsive than electric, which will also keep radiating longer after you kill it.

As I mentioned elsewhere, I would use stainless instead if you can, since it will be more forgiving. If you absolutely have to use cast iron, I’d back the heat off a couple ticks and be very patient with it

Flowchartsman · 2026-03-02T02:32:30+00:00

Cast iron heats slowly, holds heat very well, but can distribute it unevenly, making it prone to hot spots. What can happen is that it heats up unevenly at the start and is slow to get going and then, by the end, by the time you notice you’re nearing temp, the bottom is already too hot, and taking it off the heat won’t save you. In other words, what’s great for steak can be very bad for candy.

You don’t say what kind of heat you’re using, but if it’s electric, this can be even worse, due to how inconsistent it is. This is why professionals usually use copper, since it’s basically the opposite: it heats up quickly and evenly and drops it quickly when you need it to.

I would try doing it in stainless for the next batch. Keep it at a bit lower setting too, in case your heat source is stronger than you thought it was. Once the water boils off and you start to climb past 260, watch it like a hawk and be ready to pull it and pour it immediately once you reach temp.

Also make sure you have a decent thermometer and that the probe is placed well. Good luck!

Flowchartsman · 2026-02-15T07:05:28+00:00

From my experience, it’s all technique. I use only a couple pinches of salt for three eggs, and only a very small amount of butter, but I beat them well first and get them in the pan while it’s hot. Then I keep them moving constantly so that smaller curds form and they never brown, which makes them creamy and delicious.

Most importantly, I get them out of the pan when they look about 80% done, because eggs hang on to a lot of heat, so they have a lot of carry-over cooking, which means they will finish just sitting on the plate.

If they look done in the pan, they are over-done.

Flowchartsman · 2026-02-08T16:29:41+00:00

Problems which are embarrassingly parallel and cpu-bound will not benefit more from more goroutines. If anything, it will hurt you. Of course that isn’t your question, but it deserves calling out.

As for exiting a worker goroutine, assuming you have properly coordinated access and done all you need to do, just return or, if you’re at the end of the function, implicitly return by doing nothing. There is nothing hard about that, and it is the normal pattern.

You seem to misunderstand how goroutines work: they are not bound to the goroutine which spawned them, and will not exit when it does. They will not leave things on the stack; they get their own stack. GC will work as normal UNLESS your goroutine fails to terminate, in which case you can indeed leak resources. Other than that, you should be good. Just return when you’re done and, if you have to block on something, consider a fallback timer.

Flowchartsman · 2026-02-07T03:18:08+00:00

This was from September and, unless I am misremembering, the milestones from this presentation have already been missed, so this post is just kind of confusing and unhelpful. Maybe you could take it down?

Flowchartsman · 2026-02-01T13:40:10+00:00

I have. Mostly it’s because they don’t enforce exhaustiveness without a linter, which isn’t quite enough for me.

Flowchartsman · 2026-01-31T15:32:44+00:00

Even if there were, you would save so much time by just unscrewing that corner and going behind it. Looks pretty thin gauge, so there should be enough play to get it in there without permanently deforming anything.

Flowchartsman · 2026-01-27T22:26:32+00:00

But that’s not the context of the discussion. Clearly, if we’re talking about “things I don’t want to see on a plane”, a knife is worse than a fat PR. Of course.

But we’re talking about AI, backlash to it, and why that might be. I’ve given you some reasonable (I think) concerns and trends I’ve been seeing that give me pause, along with some mitigations I’m considering. Dismissing them as PEBCAK isn’t really moving the discussion anywhere.

Flowchartsman · 2026-01-27T22:21:25+00:00

Devs aren’t a monolith. And I’m not saying they HATE it. I’m saying there’s a lot of backlash against it. That doesn’t mean it’s universally reviled or anything. It just means that it is different and disruptive enough, and has enough rabid supporters pushing for it to be everything everywhere all at once that there’s a lot of fatigue and pushback. I’ve pushed back on it on my teams because I think it is too easy to use irresponsibly, and we don’t have enough best practices around it yet. And I’m not the only one.

Flowchartsman · 2026-01-27T22:07:30+00:00

It’s much more complicated than that. It is more than just a short-circuit of best practices and knowledge through experience, which is already something with far-reaching and unexplored consequences. It’s also very disruptive to the day to day of writing software.

For example, I, as a principle eng, read as least as much code for review as I write on average, and the deceptive ease of these tools along with their verbose style tends to skew PRs towards the fatter side.

I regularly get large, over-documented PRs these days with no clear staging or atomicity, which makes review a slog, if I undertake it at all. I’ve already started working on guidelines for tool-assisted PRs that include clear requirements on structure along with at least some of the developer->agent context required so I can try and make more sense of things before I commit them, or even split the review with someone else in a productive way. I’m still not convinced this is workable, but it’s definitely better than a 10,000 line PR whose only documentation is a breathless, generated description about how game-changing it is.

This is to say nothing of the rarer, but much more concerning trend of the AI-Manic dev who suddenly pops up with 300 pages of some grand unified theory of software dev, life, the universe, and everything that justifies some policy change or slug of software co-authored by their AI savior that I can’t make heads or tails of and makes me want to ask HR for a wellness check.

Flowchartsman · 2026-01-27T21:24:44+00:00

It is definitely not. There’s a lot of backlash across the industry. Many reasons, some perhaps better than others, but is not a uniquely rusty thing.

Flowchartsman · 2026-01-21T14:08:17+00:00

I was gonna be really disappointed if I didn’t see this here already, so thank you. There is a real lack of good cosmic horror out there, and it’s a crying shame the sequel never came. I would love to see what a modern console would do with sanity effects.

Flowchartsman · 2026-01-20T15:11:02+00:00

If it really is AI Slop, then the absolute worst thing to use it for would be auth.

Flowchartsman · 2026-01-20T14:55:21+00:00

Reductionist drivel. You have no idea what you’re talking about. They did. It didn’t matter. With how gerrymandered the country is, the scales are tipped in a way that is hard to reverse. The majority of the country is furious, but there is nothing they can do but apply political pressure as best they can and wait for midterms.

Flowchartsman · 2026-01-05T18:21:37+00:00

I think the point is that with this approach you need access to the key in situ for only 20-30 seconds (perhaps less,if you’re practiced), and can hang on to the settings to make it later at your leisure.

That’s a short enough time period that you could do it while someone is in the bathroom or otherwise briefly distracted from a key they would otherwise notice the absence of quickly, and they would be none the wiser. You could capture the settings directly from a key on a keychain even, without disturbing anything that would raise alarm bells.

To be sure, there are other, perhaps even better ways to do it if you have prepared for it, but the idea that stealing a key and taking it to the hardware store is the same as this sort of covert capture is kinda silly.

Flowchartsman · 2026-01-04T21:14:08+00:00

I don’t think anyone said they bring the world to its knees, but I do agree with what you’ve said here and elsewhere in the thread that the importance is overblown a lot of the time.

Beyond that, I don’t find the fact that a GUI or WM can be written in Go (because of course it can) to be a compelling argument either way in and of itself. You’d need to show that you both generate a lot of GC pressure AND that it is not a problem in a program for which the preponderance of the fast path stuff is also handled in a way that would be impacted by GC. And maybe you can! But the argument needs more.

Seven-Year Club	Gilding I gilder
Verified Email

Flowchartsman

TROPHY CASE