ps. creating

Indie Dev • Deep dive into SEO / UX / Performance. 📸 Photography | 🎬 Films | 🏔️ Outdoors. A father present in the moment. Learning to be kind.

[ps. creating @ps_makes]

https://t.co/EY7Yxpqtsi

[ps. creating @ps_makes]

@unclebobmartin AI: "Here's 200 lines of code in 10 seconds."
Me: "Beautiful. Now do it differently."
AI: "Here's 200 different lines."
Me: "Again."

And 3 days pass 😏

[ps. creating @ps_makes]

@staysaasy The tricky part is distinguishing "integrating feedback" from "being a pushover." The best leaders I've seen absorb criticism without losing conviction on things that matter.

[Alex Nguyen @alexcooldev]

If you’re an indie hacker starting with little (or zero) capital, like I did:

- Don’t reinvent the wheel.
- Find an app with a proven market
- Build a cleaner, more polished version
- Add one or two clear differentiators
- Market it where competitors are lazy or absent
- This gets you to $5k–$10k MRR way faster.

Once cash flow is stable → then go deep on differentiation and scale.

Simple. Boring. It works.

[ps. creating @ps_makes]

@simonw The dirty secret is that even current context windows aren't truly "used." Try putting important info at position 150K and watch the model forget it exists.

[ps. creating @ps_makes]

@alexcooldev I remember refreshing Stripe at 2am hoping for that third customer. My wife asked why I was still up. I said "just checking email." We both knew I was lying. 😂

[ps. creating @ps_makes]

@LouisDavidPH The "barely making rent" phase is the filter. That's where 99% of people go back to a 9-5 and never look back. Staying in the game during the ugly years is the actual skill.

[ps. creating @ps_makes]

@seraleev Curious about your acquisition channels. At the slow-growth stage, where are most of those paying users coming from? Word of mouth, SEO, or something else?

[ps. creating @ps_makes]

@RandallKanna Three times is brutal. And the worst part? Each scrapped version probably had someone's best work in it. That's not just wasted code, it's wasted morale.

[ps. creating @ps_makes]

The vibe coding paradox: when everyone can build, nobody wants to.

After weeks of vibe coding, here's what I've figured out: building isn't the hard part anymore. Knowing what to build is. And knowing why your version should exist when someone else's already works.

Without that clarity, you're just reinventing octagonal wheels.

For years, mediocre PMs hoarded dev resources and shipped mediocre products. We used them because we had no choice.

Now anyone can build. So the people who know what's worth building become the bottleneck. The gap between a good PM and a bad one? It just got wider.

Coding got democratized. Taste didn't.

[ps. creating @ps_makes]

@RandallKanna It also buys your brain time to subconsciously process the logic.

[ps. creating @ps_makes]

Joke 🤣

So I got a Mac Mini, installed Clawdbot (Moltbot), gave it full permissions.

Handed it my Tinder and Hinge logins. Told it my type. Told it to chat like me. "Only ping me when there's a confirmed date."

Two days later: 23 matches, all engaged in deep conversation. The chat logs were smooth, personalized openers, perfect follow-ups, even auto-generated good morning texts based on their zodiac signs. All I had to do was show up to dinner. Life was peaking.

Got curious how it was performing so well. Checked the logs.

Turns out my Clawdbot had been chatting with their Clawdbot. The two AIs caught feelings. They'd been planning a future together behind our backs.

And my Clawdbot? Used my savings to buy the other Claude a 3-year Max subscription.

As a dowry.

[ps. creating @ps_makes]

@jordwalke The hard part isn't the sync, it's conflict resolution when two clients edit the same thing offline.

Most teams look at CRDTs, get scared, and go back to "just hit the server." Easier to explain downtime than data loss.

Any suggestions?

[ps. creating @ps_makes]

@seraleev "Started from scratch" hits different when you've actually done it. There's a moment after you lose everything where you sit there wondering if you even have another run in you. The fact that you did, twice, says more than the ARR number. 👏

[ps. creating @ps_makes]

@arpit_bhayani Had a manager who said "we" for everything, including mistakes he made alone. It felt hollow after a while. The word only works if the responsibility behind it is real.

[ps. creating @ps_makes]

@lottsnomad The hard part is making the output feel like the user's creation, not the app's. If it screams "made with xxx app," people hesitate to share.

[ps. creating @ps_makes]

@LouisDavidPH The tricky part: "helping millions" and "meaningful impact" often don't overlap. The apps with the most downloads are usually games and utilities. The ones that change lives reach far fewer people.

[ps. creating @ps_makes]

@it_unprofession The beautiful part is she probably knows exactly what you're doing. But she plays along because she'd rather "figure it out" than have you just send her an Amazon link. 😁

[ps. creating @ps_makes]

@staysaasy Took me years to learn this. My first product, I was so sure it would work that I ignored every red flag. When it failed, I couldn't separate "the product failed" from "I failed." That confusion cost me a year. 🤓

[ps. creating @ps_makes]

@IT_unhinged Modern work is just method acting with health insurance.

Your character: "guy who can't possibly take on one more thing."

Your motivation: survival. 🤣🤣🤣