https://t.co/6kpFf1DMPX: Find who you vibe with, git commit to love
Cause you gotta launch on product hunt, thems the rules
https://t.co/7UrBImhQ9Z via @producthunt
STOP making tools for other nerds!
GET THE FUCK OUT OF THE COMFORT ZONE!
Make an AI tool that would help your MOM or DAD or someone who doesn't spend the whole fucking day in front of the computer.
For my own stuff, I’m pretty much done with CMSs.
The last few sites I’ve built are just plain PHP, markdown files with YAML frontmatter, and Parsedown for markdown-to-HTML rendering. No database, no admin panel, no plugin ecosystem accumulating technical debt.
Takes just 2 seconds to deploy and nothing to update, nothing to break, and nothing to maintain.
Every WordPress site I’ve ever run has eventually had a plugin conflict that broke a bunch of stuff. Every Craft CMS or Drupal upgrade has had at least one “why the fuck did that break” moment.
And for what? So I can edit content through a UI instead of just opening a file and pushing to git?
All that just so bots can hit my admin login page? Ugh…
I get it for enterprise clients with marketing teams, structured content, permissions, workflows, etc… a CMS earns its complexity at that scale.
But for a personal site, a blog, a product landing page, or even for relatively large sites, markdown files pushed to git is the most liberating stack I’ve used in a long time. I’m switching most of my content sites to a simpler system like this.
My co-founder is considering moving his main site over from WP to a system like this. Like thousands of pages, variations, modules, components. All that stuff can be replicated pretty easily, and then never have to deal with WordPress plugin updates ever again
No opinions to fight, no framework to learn, no dependencies to resent.
Just files.
Building an homelab is adultness
Building an homelab is adultness
Building an homelab is adultness
Building an homelab is adultness
Building an homelab is adultness
@mfranz_on Dissociation in general is a tricky thing, It can be advantageous if focused correctly but it exceedingly hard to do so.
The effort it requires to take the optimal route is... a lot
Chat UI would be a lot better with fluid or semi structured woven in commands.
opencode already does this with file tagging and subagent tagging but imagine if you could invoke certain options as if they were CLI switches.
Chat interfaces require way more cognitive work than people realize. I find it tiring sometimes.
I mean, you have to remember what you want, translate it into words, guess what phrasing the AI understands, do the whole back and forth dance, and track the conversation, summarize it in your head, then maybe branch out, etc.
Traditional navigation just needs you to recognize a menu item. We need both, but man sometimes a chat ui is just not necessary.
@mfranz_on Joke prompt: "build agi, make it aligned, no dystopia"
Actual: an automation you already built by hand or with other tools, to see how ti understands scope and how capable it is
@joncphillips I don't subscribe to ship fast by itself. (I do subscribe to shipping in the tumblr way)
and yeah I feel this. the twitter sphere loves its buzzwords and people latch on.
@mischavdburg I think the only thing stopping me from taking the plunge on k8s is that I need to confirm there are remote jobs available that are stable.
I'm not even looking for 200k/yr
Remote work is my priority