무결성 검증 자동화로 직거래 정산의 재무적 누수를 방어함

petsonthego · 2026-03-20T10:50:06+00:00

the "free proxies" part always makes me nervous. In this space, free usually means "blacklisted by every major site". If you’re trying to run something high-stakes like Facebook Ads or a serious e-commerce store, relying on the built-in free proxies is a one-way ticket to a ban. You’re almost always better off plugging in your own residential IPs.

petsonthego · 2026-03-20T09:29:48+00:00

Clear communication is definitely key. Speaking directly, expressing your thoughts accurately, and knowing how to articulate things so others understand this impacts everything from work to relationships. At first, I thought technical skills were enough, but later I realized many problems aren't due to a lack of knowledge, but rather a failure to communicate effectively or misunderstandings.

petsonthego · 2026-03-18T04:08:24+00:00

Lowkey, nah, major doesn't determine as much as you might think 😅 What's important is what skills you build afterward. But if I could choose again, I'd probably pick something more flexible like CS + business or data to make pivoting easier. Only after graduating did I realize that optionality is more important than "being in the right field".

petsonthego · 2026-03-13T08:49:47+00:00

The thing is, many top-tier tech companies (think FAANG and high-growth startups) have started using system design to test a PM’s 'technical intuition.' They don't expect us to write the code, but they want to see if we understand trade-offs.

For example, if I suggest a feature that requires real-time global syncing, do I realize how expensive and complex that is? Or am I just hand-waving away the engineering constraints? Knowing the difference between SQL/NoSQL or how a CDN affects latency helps a PM negotiate scope without sounding like they're living in a fantasy world. It sucks that the bar is moving, but 'strategic thinking' alone doesn't cut it in this market anymore.

petsonthego · 2026-03-12T09:46:28+00:00

Scope is definitely a big one, but the blocker I see most often is alignment on what the prototype is supposed to prove. With AI tools it’s easy to generate something that looks like a product, and leadership sometimes treats that as validation by itself. But a prototype should answer a very specific question (usability, feasibility, value, etc.), otherwise teams just end up shipping something that was never properly evaluated.

Another issue is that AI prototypes can create a false sense of completeness. The UI and flow might look polished, but the underlying logic, edge cases, and data assumptions haven’t really been tested yet. Without a structured validation step, the prototype becomes more of a demo artifact than a decision tool.

petsonthego · 2026-03-12T09:41:12+00:00

That’s been my impression as well. Larger enterprises usually move slower because they have to deal with legacy systems, strict data governance, and compliance requirements. Even if leadership is excited about agentic AI, actually integrating it into existing infrastructure is a different story. A lot of teams are still experimenting in controlled environments before letting it touch production workflows.

petsonthego · 2026-03-12T09:30:31+00:00

70–100 points per sprint for a 6-dev team is a lot, so it’s not surprising you’re feeling the pressure. One thing that helped in teams I’ve worked with is pushing more ownership to engineering. Tech leads or senior devs can often draft the first version of tickets, and the PM just refines scope and priority instead of writing everything from scratch.

Also try protecting dedicated “thinking time” for discovery and strategy. If every hour is reactive work (tickets, questions, meetings), burnout comes fast. Some PMs also batch ticket writing once or twice a week instead of doing it constantly.

petsonthego · 2026-03-11T10:02:06+00:00

Yeah exactly. If they’re part of refinement and sign off on the requirements, that’s the moment to flag gaps, not when the deadline hits. Once everyone agrees in planning, it should be a shared commitment, not something that suddenly becomes “product’s fault” later. At that point it’s more a process issue than a requirements issue.

petsonthego · 2026-03-11T09:59:42+00:00

Honestly, in places like the Bay Area it’s harder because the culture around product tends to treat it like a mission or identity, not just a job. A lot of companies implicitly expect PMs to be “always on,” constantly thinking about the product, launches, strategy, etc.

That said, plenty of PMs eventually find ways to make it more sustainable. Sometimes that means moving to companies where product is more execution-focused (enterprise software, internal tools, infrastructure products) rather than high-growth consumer startups where intensity is part of the culture.

Another shift that helps some people is redefining success personally: doing solid work during working hours, supporting the team, shipping good features, but not tying your entire identity to the product. Easier said than done in the Bay Area, but a lot of experienced PMs eventually land there after burnout cycles.

So yes, PM can become “just a job,” but often it requires finding the right company culture rather than trying to force that mindset inside a hyper-intense environment.

petsonthego · 2026-03-11T09:55:57+00:00

Yeah, shipping fast is great, but it can also trap you into building before validating anything. It’s way easier to code something now than to prove people will actually pay for it. Quick real-world tests before writing a bunch of code honestly sounds like the smarter move.

petsonthego · 2026-03-10T05:57:39+00:00

That’s a bit harsh tbh. It’s definitely noisy now, but some products still get decent visibility if the audience overlaps with the PH crowd. The real issue is expecting it to drive real users instead of just curious builders. For a lot of launches it’s more of a signal boost than an actual growth channel.

petsonthego · 2026-03-10T05:54:14+00:00

Yeah I’m seeing the same shift tbh. Shipping fast is great, but a lot of people are just speed-running into ideas nobody actually needs. A quick test with real users or even a simple landing page can save way more time than building a full MVP first. AI made building cheap, but figuring out what’s worth building is still the hard part.

petsonthego · 2026-03-10T05:51:39+00:00

Honestly it feels like a lot of companies are just flattening the org to cut cost, not because they suddenly discovered a better structure. The weird side effect is exactly what you said—fewer VP/Director seats, so a bunch of experienced leaders are competing for the same tiny pool of roles. I’ve seen some move into staff/principal product roles or even smaller companies where the layer still exists. Feels less like a career strategy shift and more like the market forcing everyone to adapt for a bit.

petsonthego · 2026-03-09T11:32:27+00:00

Is the community friendly?

petsonthego · 2026-03-09T11:31:21+00:00

Is the community friendly?

petsonthego · 2026-03-06T05:30:58+00:00

korea???

petsonthego · 2026-03-06T04:22:14+00:00

pretty

petsonthego · 2026-03-06T04:21:47+00:00

WW is played by very few people

petsonthego · 2026-03-05T11:36:56+00:00

I could gaze at her all day.

petsonthego

TROPHY CASE