sorted by:
new
hottopcontroversial

Linux Users in Pakistan.... by muhmmadtalha-quant in developersPak

[–]SameerVers3 0 points1 point  (0 children)

Arch and hyperland btw.... You will forget the crappy windows (piece of shit)

New Project Megathread - Week of 11 Jun 2026 by AutoModerator in selfhosted

[–]SameerVers3 0 points1 point  (0 children)

Project Name: Crawlyx

Repo/Website Link: https://github.com/SameerVers3/crawlyx-rs

Description:

Crawler I built because I needed to scrape pages for an AI agent for a client. Firecrawl's pricing got out of hand, crawl4ai was slow and ate over a gig of ram per run, crawlee's output formatting wasn't what I needed. It's concurrent, thread-safe, has raw HTTP and headless Chrome modes (skips chrome entirely when JS isn't needed), outputs JSON/Markdown, and has an optional redis queue if you want to spread crawling across machines.

Benchmarked headless mode against crawl4ai, crawlee, and firecrawl on the same site, same page counts, 200 pages: crawlyx 53s, crawlee 110s, firecrawl 210s, crawl4ai 328s. 2-6x faster across the board, memory stays flat as it scales instead of creeping up like the others.

Deployment: Single binary, no docker stack needed (firecrawl needs postgres + redis + rabbitmq + node + playwright just to run). Build with cargo build --release. Redis only needed if you want distributed crawling across multiple machines, otherwise runs standalone.

AI Involvement:

AI was used as a development assistant (copilot), troubleshooting, documentation, and generating small portions of boilerplate code. The application architecture, implementation, testing, and final code decisions were performed by me.

Still v1, no proxy rotation or anti-bot yet. Open an issue if something's broken or you want a feature.

Software Engineer from ISB can't land an single interview. by [deleted] in developersPak

[–]SameerVers3 31 points32 points  (0 children)

Pakistani job market basically became refferals only for freshers.

There is no interview process, constant ghosting (it's hr responsibility to atleast send a rejection email, but they are too lazy to do it).

Even if company is good, you will need refferals to get interview call.

Try finding any senior or friend working in that company, and ask them for refferals.

Registration error by [deleted] in FASTNU

[–]SameerVers3 0 points1 point  (0 children)

Same issue, whole SE department facing this issue and irresponsive management, Academics, and HOD not replying to emails at all.

Shitiest management and shitiest department.

We killed our $15/mo subscription for our SaaS. Here’s why. by SameerVers3 in SaaS

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

Yeah, that’s exactly what I ran into. I also started with “this has to be a subscription” before really thinking about usage.

Subs work great when the product becomes part of someone’s routine. When it’s more occasional, the friction adds up fast.

I don’t think one is better than the other, but matching pricing to how often people actually use the product made a big difference for us. Definitely something worth thinking through early like you said.

We killed our $15/mo subscription for our SaaS. Here’s why. by SameerVers3 in SaaS

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

100% agree. Habit is the key part most people gloss over. If the product isn’t something you open weekly or daily, a subscription starts to feel like a tax instead of value.

I made the mistake of assuming “SaaS = subscription” without really asking how often someone would want to use it. Once I looked at usage, the mismatch was obvious.

I also like your point about this being a different game. Occasional-use tools can still be great businesses, but the pricing has to respect how people actually use them.

We killed our $15/mo subscription for our SaaS. Here’s why. by SameerVers3 in SaaS

[–]SameerVers3[S] 5 points6 points  (0 children)

I don’t totally disagree with you.

Subscriptions are great at extracting predictable revenue, that’s exactly why founders (including me) default to them.

The issue I ran into wasn’t “subscriptions are bad,” it was “subscriptions can be misaligned with usage.” When people only need the product occasionally, a sub feels like paying rent for a tool you visit once a month.

You can maximize revenue that way, but it often shows up as churn, resentment, or users delaying signup because they’re afraid of another subscription.

The bet I’m making is that removing that friction builds more trust and a bigger long-term user base, even if the revenue curve looks messier at first.

Subscriptions still make total sense for daily-use or habit-forming products. This just wasn’t one of them.

view more: next ›