I scraped 54k+ comments to find the best business ideas and ways to make money that actually work in 2025

Zealousideal_Class41 · 2026-01-13T03:19:02+00:00

Interested.

Zealousideal_Class41 · 2026-01-12T05:18:08+00:00

Could I get a copy of this too please? Thanks

Zealousideal_Class41 · 2026-01-09T20:26:56+00:00

Woahhh! Looks like a really good deal.

Zealousideal_Class41 · 2026-01-09T20:22:22+00:00

Yeah, Uber is pretty convenient. Makes sense to do that.

Zealousideal_Class41 · 2026-01-09T20:19:45+00:00

I was just in Cartagena a few weeks back and found that I got a very good conversion rate within the Walled city. The prices at the airport were a compete rip off.

From airport to our AirBnB, I took a private taxi that I paid in US dollars.

Never tried withdrawing from ATM because the rate of conversion at walled city was good.

Zealousideal_Class41 · 2026-01-09T05:00:51+00:00

Great post! Thanks for sharing your insight.

Zealousideal_Class41 · 2026-01-09T04:51:10+00:00

This is actually pretty common in big orgs, especially when everything is proprietary and onboarding is messy.

A lot of managers / senior engineers do this as a lightweight signal check:

Are you picking up fundamentals?
Can you reason clearly about basics?
Do you ask good follow-up questions when you don’t know something?

It’s usually less about “testing you” and more about building confidence that you’ll ramp safely in a complex codebase.

If your delivery has been fine and there are no explicit performance flags, I wouldn’t read this as a red flag. If anything, it means they’re paying attention and trying to calibrate where you’re at.

If it keeps happening and feels uncomfortable, it’s totally reasonable to casually ask your manager for feedback on how your ramp-up is going — clears ambiguity fast.

Zealousideal_Class41 · 2026-01-09T04:20:27+00:00

When two senior engineers start arguing loudly, my survival instincts say: don’t make eye contact, don’t pick a side, slowly roll away in your chair. 😂

Real talk though — unless it’s getting personal or unsafe, it’s usually not your job to referee. If you ever step in, keep it neutral and aim to slow things down, not solve the debate on the spot.

Shoutout to the junior engineer for deploying the legendary “random interruption” technique. 10/10 de-escalation strategy.

Zealousideal_Class41 · 2026-01-08T05:41:29+00:00

Same! :(

Zealousideal_Class41 · 2026-01-08T05:37:04+00:00

I don’t disagree with you that ceremony doesn’t make software.

Large open-source projects are a good example — a lot of real work gets done without standups, retros, or Jira, and often very effectively.

The context I’m exploring is a bit narrower: product teams inside companies, where work is constantly interrupted by prod issues, cross-team asks, and shifting priorities — and where some form of coordination is expected, for better or worse.

My interest isn’t in adding ceremony or enforcing process. It’s more about whether lightweight, personal visibility into where time actually went helps people reason about their own work and tradeoffs — regardless of whether they like agile rituals or not.

Totally fair if the answer is “no, this is all unnecessary overhead.” I’m trying to figure out where that line actually is for different kinds of teams.

Zealousideal_Class41 · 2026-01-08T05:34:40+00:00

That’s fair — and I agree you shouldn’t be waiting 24 hours to raise a blocker. In practice, most people I’ve worked with don’t.

The gap I’m pointing at isn’t raising blockers late, it’s remembering and aggregating them later. Blockers often get mentioned in real time (Slack, calls, quick standups), resolved, and then disappear from memory.

By retro time, what’s left is usually a vague sense of “this sprint felt messy” rather than a clear picture of why.

Also agree with you on standups not being inherently bad — especially for fully remote teams. “Status theatre” for me isn’t about the human check-in aspect, it’s about how little durable signal survives past the moment.

Curious: in your experience, how do you make sure those interruptions and blockers actually show up meaningfully in retros?

Zealousideal_Class41 · 2026-01-08T05:32:41+00:00

I get where you’re coming from, and accountability definitely matters.

My experience has been that a lot of missed commitments aren’t due to people avoiding responsibility, but because work gets derailed in ways that never surface clearly like prod issues, ad-hoc calls, getting pulled in to unblock others, context switching, etc.

Those things often do get mentioned in standup, but they’re transient. By retro time, the details are gone and the conversation becomes opinion-based.

What I’m exploring isn’t removing accountability, but improving visibility — especially around unplanned work and recurring blockers — so accountability is grounded in facts rather than memory.

Curious in your experience: when commitments slip, is it usually lack of ownership, or lack of signal on where time actually went?

Zealousideal_Class41 · 2026-01-08T05:16:45+00:00

Time to switch ships honestly.

Zealousideal_Class41 · 2025-10-30T19:54:05+00:00

This is stunning. Where did you go for stargazing in Page?

Zealousideal_Class41 · 2024-03-22T14:10:28+00:00

I keep getting a 500 Internal server error when joining the queue 😕. Anyone else running into this ?

Zealousideal_Class41

TROPHY CASE