@solopribuilds boring tech=good enough
it was used to make a million $ business, probably good enough for your project as well.
you don't need the latest and the greatest tech to succeed.
you need things to work, and some tech has decades of proof for that.
Something I keep running into: I'm working on enough different things that I forget context between them. Each project has its own management setup but none of them know what's happening in the others.
Still in the brainstorm phase on how to fix this, some kind of running log or knowledge base separate from how I take notes for content. For now I'm just closing tabs on the side projects and organizing them to pick back up later. Focusing on SignalNine revenue. The rest is just distraction if I'm honest about it.
Logged this one because it was fun. I got Claude Code running on my own VPS and now I can drive it from n8n instead of going through the API.
I knew it was possible. But actually making it work opened up so many doors to other things I can do with it.
I realized a lot of what I'm doing right now requires me to manually remember it. So I'm trying to make it more autonomous, where I get prompted to do the thing instead of memorizing it and following some discipline.
It needs to be a system where I'd be doing it without much thinking, prompted rather than prompting myself. At first I thought it was an accountability thing. I don't think it is. It's more about systemizing the habit so it works around my work.
It's fine to follow some structure, and there are topics that matter for the business itself. But I'll do it in a way I'm actually into. So the subject is defined by what the business needs. The style is defined by me, not by shallow optimization.
Because the more I do it that way, the more I'm building the skill of speaking, instead of the skill of following a script. I want to be able to look at a diagram and explain the concept.
So I realized it's better to hit record, say it out loud a couple of times, and delete the repeated versions. That's the most natural way to go about it.
Kept rewriting the script and then speaking it out loud, over and over. And at some point I was just looking at the diagram and explaining it the way I'd actually say it.
(I'm creating loom infra walkthroughs)
founders, please comment answer to a stupid question for engagement.
ie:
"are founders using vscode"
"hot take: marketing > building, thoughts?"
"post your app"