u/Thunderbit_

I’m trying really hard not to spend much on plants right now because money is tight, but I still miss the little serotonin hit of bringing home something new.

So now I’m living through other people’s clearance rack wins.

What’s the best “I cannot believe this was only $5/$10/$15” plant you’ve ever found?

Was it at a grocery store, big box store, local nursery, plant swap, random curb find, etc.? And did it actually stay healthy after you got it home?

Bonus points for ugly-duckling plants that turned into something amazing.

It’s getting hot where I am and I’ve reached the point where turning on the oven feels personally offensive.

I know the obvious answers are sandwiches and salads, and I do eat those, but after a few days I start wanting something that feels more like an actual dinner.

I’m looking for meals that don’t heat up the kitchen much. Rice cooker, Instant Pot, microwave, rotisserie chicken shortcuts, cold noodles, snack-plate dinners, anything like that.

What do you make when it’s too hot to cook but you still want something decent?

There's an interesting pattern in side projects lately: someone gets annoyed with a paid tool, rebuilds the small part they need, then makes it local/free/self-hosted.

Voice-to-text, writing tools, bank exports, tiny productivity apps, stuff like that.

On one hand it seems like a good niche because the pain is already validated. People are literally paying for the thing.

On the other hand, it can also be a trap. The paid product probably has a bunch of boring edge cases that aren't obvious until you try to replace it.

For people who have built "I refused to pay for X so I made Y" projects, did it actually turn into users, or was it mostly a fun personal build?

And what made the difference?

I've been noticing a weird pattern with automation projects.

The first version feels great: one annoying workflow gets removed, a few manual steps disappear, everyone is happy.

Then a few weeks later there's a new problem:

- the API changed

- the spreadsheet format changed

- one edge case keeps breaking

- nobody remembers why the workflow was set up that way

- the "simple automation" now needs docs, monitoring, and a person who owns it

So the work didn't fully disappear. Some of it just moved into maintenance.

For people building internal automations or client automations, how do you decide when something is worth automating vs when it's just creating a new system to babysit?

Do you have any rules of thumb for this?

This might be a common beginner problem, but it’s frustrating.

When I follow a tutorial, everything makes sense. I can read the code, understand what each part is doing, and even modify small pieces.

But if I close the tutorial and try to build something from zero, my brain just kind of freezes.

The hard part isn’t syntax exactly. It’s more like:

- where do I start?

- how do I break the problem down?

- what files should exist?

- what should I write first?

- how do I know if my structure is terrible?

I’m starting to think tutorials teach recognition more than problem solving.

For people who got past this stage, what actually helped? Smaller projects? Rebuilding tutorials from memory? Reading other people’s code? Something else?

One thing I underrated for a long time: free feedback and paid feedback are completely different animals.

People will say “cool idea” all day. They’ll upvote, ask for features, maybe even sign up.

But when someone actually pays, even a tiny amount, the conversation changes.

They suddenly care about:

- whether the tool saves real time

- whether onboarding is confusing

- what they’d be annoyed by next week

- what they expected but didn’t get

- whether this is a toy or something they’d keep using

I don’t think this means every project needs to monetize immediately. But I do think “would anyone pay for this?” clarifies things really fast.

For people who got their first paid customer: what changed after that? Did it validate the product, or did it mostly expose new problems?