u/Little_Decision_7433

Keep seeing this misunderstood so worth saying clearly: the padlock in your browser means the connection is encrypted. that's it. it does not mean the site is legitimate, the business is real, or anyone verified who owns it.

Let's Encrypt made SSL free and automatic years ago. scammers have had valid padlocks on phishing pages since at least 2018. a padlock just means your data travels to the scam site securely.

There used to be a higher-tier cert (EV SSL) where the issuer actually verified the legal identity of the company. you'd see the company name in green in the address bar. browsers quietly removed that indicator a few years back. so even that signal is basically gone now.

HTTP with no padlock in 2026 is a red flag. HTTPS with a padlock is not a green flag. it's just table stakes.

what do you actually check before entering card details on a site you've never used?

It's not formatting. It's not typos. It's not your college.

It's that your resume reads like a job description instead of a story of what you actually did.

You write: "Responsible for managing team communications and optimizing workflows."

What I read: Generic. Forgettable. Next.

Someone else writes: "Identified that our team spent 12 hours/week on manual status updates. Built a Slack bot that killed the process. Team got 12 hours back per week."

That person gets a call.

The difference? One shows impact. The other shows responsibilities.

Most job descriptions are written by HR. Your resume shouldn't sound like them.

Stop listing what your job was. Start showing what you changed.

Can you point to three things you actually improved? Quantify them. That's your resume.

Everyone talks about resume formatting. Fonts, bullet points, ATS optimization, spacing—it's endless. But after reviewing thousands of applications, I can tell you that's not why most resumes get rejected.

The real problem is that your resume tells a story, but not the story a hiring manager wants to hear.

Here's what I mean. Most people write their resume like it's a job description. "Responsible for X. Managed Y. Implemented Z." That's not compelling. A hiring manager doesn't care what your job title was. They care what problems you solved and what impact you had.

I've seen dozens of candidates with identical job titles and responsibilities. The ones who moved forward? The ones who showed: "I found a problem that was costing the company money, and here's exactly how I fixed it and what changed because of me."

The difference isn't the resume format. It's the thinking behind it.

Most people spend 2 hours on their resume. The ones who get interviews spend a week thinking about what they actually accomplished and how to frame it in a way that matters to the business, not just to HR.

So here's my question for you: Can you point to three concrete problems you've solved in your last role and quantify the impact? If you can't, your resume probably won't stand out either.

What do you think is this what's missing from your resume?

I spent 2 weeks talking to hiring managers at companies that actually hire junior ML engineers. Wanted to understand what percentage of resumes they instantly reject and why.

The pattern was shocking. Most freshers are solving the wrong problem.

What kills resumes (and it's NOT what you think):

#1: Your project picks scream "I built something to put on my resume"

Smart traffic system. Sentiment analysis. Fraud detection. Everyone builds these. Hiring managers have seen 500+ versions. What they want: evidence you can ship something real that someone actually uses. Build a tool you'd actually use. Not a tutorial project.

#2: You're competing on skills, not on shipping

"I know Python, PyTorch, TensorFlow, Pandas..." Okay? So does everyone. What they actually care about: "I shipped X. It broke. Here's how I debugged it. Here's what I learned."

#3: Your GitHub is empty (or useless)

If you have a GitHub, your repos look like homework submissions. No README. No actual process visible. They want to see your thinking commit messages, issues, how you approach problems.

#4: You're doing interviews wrong

You memorize ML concepts for technical rounds. They ask you to code a solution in 45 minutes. You freeze because memorizing formulas isn't the same as knowing how to think through a problem under pressure.

Real talk: Freshers who got hired had ONE thing in commo they built something small and shipped it. Not for their resume. Because they wanted to. Then they got interviewed and could talk about what actually broke and how they fixed it. That conversation changed everything.

Curious if this resonates with what you've seen or heard. Am I missing something or is the "build portfolio projects" advice just fundamentally misguided?

I've been talking to 50+ founders who built SaaS over the last year. Most get to 100 users. Almost none get past 1000. After digging into what happens at this inflection point, I noticed something weird: it's not a product problem. It's a data problem.

At 100 users you can ignore bad data. At 1000 you can't. You need to know:

Who's actually staying vs churning?

Why people cancel (not assumptions, actual data)?

What features users actually use vs what you think they use?

How much it costs to serve each customer?

Most founders have zero visibility here. They're flying blind.

I built a small tool to help this (not pitching, just context). While building it I learned that the founders who survived past 1000 users had one thing in common: they obsessed over user behavior data the moment they hit 100.

So here's my question: At what point did you start seriously tracking user behavior? And did it actually change how you built?

Dating apps have been leaning hard into AI lately and Tinder is no exception. Tinder's new Chemistry feature hands your match queue over to an algorithm that decides who you should meet based on personality signals and behavior patterns. A lot of people have been asking whether Tinder can actually be trusted with your data and your location when so much of the matching process happens inside a black box.

Trust score: 87/100

• Corporate structure transparent, founders and CEO publicly known
• SSL valid, domain active since 1998, not on any blacklists
• Facial verification now mandatory for new users in the US

What people are actually saying:

"i found my partner! and never been happier. i havent been active on tinder for years, but anytime i made a real connection with someone, it turned out to be a great date and i am still friends with those people. tinder helped me figure out my sexuality and find people of similar interests, as we are often shy and wouldnt talk to each other otherwise. even though im bad at texting, my partner had patience with me and we have been in a relationship for months and are getting engaged soon. i would recommend everyone to at least try. not just hook up. theres more." - Adéla, Trustpilot

"I paid for a Gold Membership and my account has been plagued with technical issues from day one. Despite having thousands of likes, I cannot match with anyone. Every time I swipe, I get a message saying Unavailable, cannot match. This has been happening for weeks, and their so-called support team is completely useless. On top of that, my account gets locked for verification repeatedly, even though it's already verified with a blue tick. How many selfies do they need? It's invasive, frustrating, and downright absurd. I've spent more time trying to fix issues with the app than actually using it. Tinder refuses to offer any compensation for the time lost or address my complaints." - Kateryna K., SiteJabber

The full report covers company evaluation, technical infrastructure, payment security and a broader look at user feedback patterns.

Is Tinder still the go-to dating app in 2026 or have you moved on to something else?

Full Tinder site evaluation: https://trustracer.com/reports/tinder.com

the Klarna story from earlier this year keeps coming back to me and i don't think the SaaS community has fully sat with what it means

Klarna, a company with real engineering resources, decided it was cheaper and better to build their own AI-powered CRM than to keep paying Salesforce. and they're not alone. the "SaaSPocalypse" piece in TechCrunch from march laid it out pretty clearly, AI agents are starting to do what entire categories of SaaS tools were built to do

the traditional SaaS value proposition was always: we build it once, you pay monthly, you get something better than you could build yourself. that math worked when building software was expensive and slow

but in 2026 a decent engineering team with AI can build a custom internal tool in weeks that does exactly what they need, nothing more, nothing less, no per-seat pricing, no features they don't use, no vendor lock-in

i'm building a B2B SaaS product right now and i'm genuinely asking myself who my customer is in three years. small companies without engineering resources, sure. but mid-market and enterprise? the ones who could just build it?

marc benioff says SaaS companies should become "operating systems for AI agents" which sounds great and means almost nothing practically

if you're building SaaS right now, how are you thinking about this. are you worried or am i catastrophizing

Accounts drained. Funds withdrawn without authorization. DraftKings confirms their core systems were not compromised.

Both things are true and that's exactly the problem. Credential stuffing attacks use password combinations leaked from other sites, not vulnerabilities in DraftKings infrastructure. Technically they're right. But if you're the user who lost $800 from their betting account the technical accuracy of that statement doesn't help you much.

The question this keeps raising for me is what "we weren't breached" actually means as a user protection. It describes where the vulnerability came from, not what the platform did to detect unusual withdrawal activity or stop it before funds moved.

What does a sportsbook actually owe users when their accounts get compromised through credential stuffing, and is 2FA being opt-in rather than default still acceptable in 2026?

not a developer. never been one. work in marketing, always had app ideas, never could do anything with them

three weeks ago i just started throwing everything at cursor and claude. describing what i wanted, iterating, breaking things, fixing things. watched maybe 4 hours of youtube total. shipped a simple subscription tool for newsletter creators, $29/mo

got my first paying customer on day 19. genuinely insane feeling

but now theres a bug where stripe webhooks randomly stop processing and i have no idea whats happening. i paste the error into claude, it gives me a fix, i apply it, something else breaks. been going in circles for two days

and it made me realize i dont actually understand any of what i built. like at all. i can describe features and claude builds them. but when something breaks at a level i cant describe in plain english im completely stuck

so my question to people here who are further along than me is this just the learning curve and it gets better? or is there a point where not knowing actual code becomes a real ceiling you cant get past

genuinely not sure if i should be proud of shipping or terrified of what comes next

so i wasnt even job hunting. just had my linkedin updated because i got a certification last month

got a message from a recruiter at what looks like a real mid-size logistics company in ohio. checked the company, it exists, has a website, glassdoor reviews, linkedin page with like 200 employees. looked legit enough that i actually responded

now they want to do an interview on teams next week and already sent over an offer letter. like before the interview. salary is 94k for a fully remote data entry coordinator role. i have no relevant experience for this. none.

the offer letter looks really professional, has the company logo, an actual address, a real person's name as HR director (i found her on linkedin, she exists)

but something feels off and i cant explain what. maybe because i never applied. maybe because the salary seems high for the role. maybe because it moved so fast

they havent asked for money or my SSN yet but they did ask me to confirm my home address for equipment shipping

has anyone seen this pattern before. is the address thing a red flag or is that just normal onboarding stuff

Saw this story from May 2026 Police Intellectual Property Crime Unit in the UK ran an operation targeting influencers livestreaming counterfeit products to thousands of viewers. Over $2 million seized. TikTok Shop hit $64 billion in merchandise sales in 2025. That scale has brought real fraud infrastructure with it fake sellers, bait and switch listings, manipulated reviews, off-platform payment requests.

The red flags I keep seeing mentioned: seller account under 90 days old, all reviews clustered within a short window, product images that reverse search back to AliExpress.

For people buying through TikTok Shop in the US is this something you actually think about before completing a purchase? Or does it feel like a different risk level than what's happening in the UK?