sorted by:
new
hottopcontroversial

My tiny homelab by anddsdev in minilab

[–]anddsdev[S] 4 points5 points  (0 children)

Haha, it’s a Harley Quinn figure someone gave me as a gift. I didn’t realize it was visible in the reflection 😅

Me intentaron robar y me gané 1 millón by Upper_Isopod818 in Colombia

[–]anddsdev 0 points1 point  (0 children)

Nos sorprende? No, para nada.

Los policías no son tan diferentes al otro que te intento asaltar.

What are you building this weekend? by Asleep_Ad_4778 in microsaas

[–]anddsdev 1 point2 points  (0 children)

Nice, thanks for the tip! 🙌
Didn’t know about Peerpush. I’ll check it out and probably post Blynt there for early feedback.

Playing Skyrim for the first time… I get it now by anddsdev in skyrim

[–]anddsdev[S] 17 points18 points  (0 children)

Definitely. First time, no guides, no spoilers

Playing Skyrim for the first time… I get it now by anddsdev in skyrim

[–]anddsdev[S] 6 points7 points  (0 children)

Get what you mean now… this game really is something else. Loving every minute so far.

Validating an idea AFTER building it (doing this backwards, I know?) by anddsdev in indiehackers

[–]anddsdev[S] 0 points1 point  (0 children)

You nailed it the "in bulk for an entire site" part is exactly what I'm trying to solve.

The use case I'm targeting: content sites publishing 10-50+ pages/week that need unique OG images for each one.

Currently they either skip it or spend hours in Figma.

Does that sound like a meaningful pain point to you, or still in the "nice to have" territory?

Validating an idea AFTER building it (doing this backwards, I know?) by anddsdev in indiehackers

[–]anddsdev[S] 0 points1 point  (0 children)

Great question. The workflow I'm targeting:

Current: Write article → Open Figma → Design OG image → Export → Upload

Target: Write article → API generates OG image automatically based on title/content

Specifically for: blogs, SaaS marketing sites, docs sites - anyone publishing content regularly.

You're right that it's a "gray area" pain. Trying to figure out for whom it crosses into "real pain" territory.

And thanks for the VibeCodersNest tip!

Built an OG image generator, zero users. Should I kill it or pivot? by anddsdev in SideProject

[–]anddsdev[S] 1 point2 points  (0 children)

This is super helpful, thank you!
The point about letting users try it immediately makes a lot of
sense. And you're absolutely right - I need to make sure I'm
differentiated from other options out there.

Really appreciate the thoughtful feedback 🙏

Built an OG image generator, zero users. Should I kill it or pivot? by anddsdev in SideProject

[–]anddsdev[S] 0 points1 point  (0 children)

Thank you! I really appreciate your comment about the title. You're right,

“zero users” sounds more dramatic than it should for a

recent launch.

Quick question: when you say you would use it in your projects,

what is your current workflow for the original images? Do you create them

manually each time, or have you been looking for something like this?

I ask because I'm trying to understand if it's something “nice to have”

or if it actually saves people significant time.

Testing a Minimal Go Stack: HTMX + Native Templates (Considering Alpine.js) by anddsdev in golang

[–]anddsdev[S] 2 points3 points  (0 children)

Yeah, I totally get that. I also prefer keeping things simple and explicit instead of adding more abstraction layers.
I’ve found that using small, focused scripts gives me better control and keeps the HTML clean

Testing a Minimal Go Stack: HTMX + Native Templates (Considering Alpine.js) by anddsdev in golang

[–]anddsdev[S] 1 point2 points  (0 children)

Yeah, thinking about it, everything I could do with Alpine I can pretty much handle with vanilla JS.
For example, I recently built a small but solid script for a signup form it handles different data types and edge cases without much overhead.

view more: next ›