Mike Katz

So it's all the same in that sense.

But a lot of it is just to mix it up.

I work for NOAA, the Ocean and Atmosphere Administration, and I do mapping programs and chemical databases for hazardous chemical response.

So that's just a completely different thing.

And then I'm working on a marketplace for psychologists to find clients.

So it's a completely different thing.

I think a lot of it is just driven by the desire to learn new frameworks.

You say, OK, I'm going to do this project and try to use this framework with it.

Okay.

Yeah.

I think that would more be related to, with the NOAA products, it tends to be,

just give me the answer as fast as possible.

So there's not a lot of, not a lot of game playing there.

The mapping component of it was informed by, you know, the graphics knowledge that I got from games.

So there's that, that overlap.

And then one tool that I'm building now is sort of a, a way for indie programmers and hackers to document their tech stack.

And so

You know, there's a lot of information that I want them to be able to document easily.

So I'd say the user interface design in terms of being as easy as possible to take those steps is... Where can people find that, the tool you're building for indie hackers?

That actually is not yet up.