General
p/generalShare and discuss tech, products, business, startups, or product recommendations
trending
•

2yr ago

Trump's tariff bomb hit the Korea stock market

Donald Trump's tariff policies are hitting the Korean stock market hard. The KOSPI is currently down 3%, and as an office worker in Korea, I am worried and feel uneasy. Could this lead to an economic crisis this year? I'm genuinely concerned. Let's talk this topic!
•

4mo ago

When do you know a feature is actually worth building?

I think many tech product builders, including myself, can easily fall into tunnel vision, whereby I am overly convinced that the feature we re working on is clearly justified. With vibe-coding tools, the cost of building new features has also dropped dramatically. But lower development costs didn't seem to translate to product growth in my organization. Many newly launched features still receive little adoption, or have a hard time "syncing" with the rest of the product.

So I m curious: how do you decide when a feature is actually worth building? Do you wait for repeated user requests, test a lightweight version first, trust your product instinct, or rely on behavioral data before committing?

•

7mo ago

Struggling to find people building hardware products — where are they hiding?

Hey everyone,

I m currently building a platform focused on helping people turn hardware ideas into actual working prototypes (connecting them with engineers, fabricators, etc).

But I ve hit a wall I didn t expect.

I m finding it surprisingly hard to locate people who are actively trying to build physical products. Not people interested in hardware, but people who are actually in the process and need help.

•

2mo ago

How do you stop user feature requests from ruining your original vision?

When you start getting regular users, everyone asks for random additions that sound good in the moment.

Slowly you look up and realize your simple app is turning into a bloated tool you didn't even want to make in the first place.

Where do you draw the line between listening to real feedback and just saying no to keep the app simple?

•

4mo ago

The UX problem nobody talks about: inspection fatigue

One thing I rarely see discussed in B2B software is inspection fatigue.

Not user fatigue.

•

4mo ago

What would happen?

I have seen a lot of people post on here purely for engagement, likes and followers. Is that actually necessary to get legitimate feedback on a release, or am I just feeding the algorithm what it wants?

•

2mo ago

What is the minimum retention signal you look for before testing higher price points?

Waiting for long-term cohort stability before raising prices sounds logical on paper, but it often delays revenue validation when your initial pricing is clearly too low.

There s always a risk that early low churn is just an artifact of undercharging rather than genuine product stickiness.

How do you know if you actually need more churn data vs just overthinking a price bump?

I ve been sitting on a price increase for way too long under the excuse of needing clearer churn metrics. Realized recently that I might just be using data collection as an excuse to delay the uncomfortable conversation.

If you bumped your rates early without full retention numbers did users actually cancel or was the fear way worse than reality?

•

2mo ago

My webhook check passed an address that means 127.0.0.1

Our API lets a customer register a URL we call when an invoice is paid. The whole job of that feature is to make a request to an address a stranger chooses, so the check on the address is the security of the feature.

The first version did what most guides say. Allow only http and https, resolve the hostname, and refuse it if PHP filter flags for private and reserved ranges reject the address. Those flags cover the ranges everyone remembers: 10.x, 192.168.x, loopback, and 169.254.169.254, where a cloud server hands out its own credentials to anything that asks from inside.

The first hole was the resolver. The function we called returns IPv4 records only. The HTTP layer resolves the name again and will happily connect over IPv6. So a hostname with a public IPv4 record and a loopback IPv6 record passed the check at registration and again at every send, with no timing trick involved. The fix was asking for both record types and refusing if any single address fails.

The second hole was the flags themselves. Checked one at a time rather than read off a table, six ranges pass them. Four are merely odd, like the shared address space some clouds use for internal networking. Two are translations: a NAT64 address and a 6to4 address can each carry 127.0.0.1 inside an IPv6 address, and a gateway will translate it back. Both passed everything. They now sit in an explicit deny list beside the flags.

At what point do you clear context instead of letting an agent try another quick patch?

I spent an hour yesterday watching an agent make four micro-fixes in a row only to land on the exact error code we started with.

It gets caught in this endless trial-and-error loop where it just keeps tweaking lines of code without checking root cause.

I started forcing myself to kill the session as soon as I see a second repeated error message.

First
Previous
•••
436437438
•••
Next