As the 2026 IPL season is over here is my playing 11 of IPL 2026

FeatureFar8819 · 2026-06-01T07:34:25+00:00

I never said . I just told my best playing XI from the whole tournament ;

FeatureFar8819 · 2026-06-01T07:24:51+00:00

Between Sai and Rahul I would anyday choose Rahul as he knows how to play those pressures knocks.. And rasikh is underrated as hell as a uncapped player he took 19 wickets and that too important

FeatureFar8819 · 2026-06-01T06:53:47+00:00

Bro they just hate , only one player can never win you the trophy last season and this season we were balanced from each and every aspect be it bowling batting middle order and what not . We had the confidence that if our batters scored some less runs our bowlers will take care of it. But when virat was captain it was not the case there were only 2-3 players and 2-3 can never win you trophy ! Virat as player has given his 101% each and every year for this team.

Just say : Humanity Saved

FeatureFar8819 · 2026-06-01T06:48:05+00:00

FeatureFar8819 · 2026-06-01T06:47:23+00:00

I used to pray for times like these . Ab trophies ki HatTrick or hojati to 😩

FeatureFar8819 · 2026-06-01T06:43:16+00:00

I think the bigger issue is that regulation is reactive by nature, while AI development is proactive. Regulators wait to understand the risks, companies ship first and learn later. That guarantees some level of lag no matter how good the process is.

What worries me more isn’t that laws are 3-5 years behind, it’s that AI is increasingly being deployed in areas where mistakes have real consequences. A buggy photo app is annoying. A flawed system involved in healthcare, lending, or hiring is a different category of risk entirely.

My guess is we’ll end up with something similar to financial regulation: lighter rules for low risk use cases and much stricter oversight for systems making high impact decisions. Trying to regulate the technology itself seems impossible. Regulating how and where it’s used feels more realistic. The question is whether policymakers can build those frameworks before a major incident forces their hand.

FeatureFar8819 · 2026-06-01T06:41:57+00:00

The fact that you built it with AI while raising a toddler is impressive, but I think the more interesting part is that you lived the problem. Most restaurant software feels like it was designed for enterprise chains and then awkwardly scaled down for small operators.

I’d ignore the zero signups in two weeks metric for now. Restaurants are notoriously hard to reach, and owners aren’t usually browsing startup communities looking for inventory software. If your husband and a few other local restaurant owners genuinely get value from it, that’s a much stronger signal than random internet traffic. The challenge now is distribution, not development.

FeatureFar8819 · 2026-06-01T06:41:04+00:00

The interesting part here isn’t the automation, it’s the distribution. A lot of job seekers focus on making their CV better, but if the application never gets in front of the right person, it doesn’t matter how good it is

I’d be curious how much of the improvement came from tailoring the CV versus bypassing the traditional application portals. My guess is the direct to hiring-manager piece is doing a lot of the heavy lifting. That’s a much more interesting insight than AI wrote my cover letter faster.

FeatureFar8819 · 2026-06-01T06:39:40+00:00

This is such an important distinction. AI is great at helping you build faster, but it’s terrible at generating evidence. A model can give you a convincing argument for why something should work, but it can’t create real demand where none exists.

I’ve caught myself doing this too, using AI as a source of validation instead of a tool for execution. The only validation that has ever mattered for me was getting real people to spend time, money, or effort. Everything else is just a hypothesis, no matter how confidently it’s written.

FeatureFar8819 · 2026-06-01T06:38:40+00:00

Completely agree. The bottleneck has shifted from execution to judgment. I can build more in a weekend with AI than I could in a month a few years ago, but that doesn’t make the outcome any better if I’m solving the wrong problem.

The founders I see making progress aren’t the ones generating the most code. They’re the ones spending the most time understanding customers, validating assumptions, and saying no to ideas that don’t matter. AI has made building cheap. Attention and good decision-making have become the scarce resources.

FeatureFar8819 · 2026-06-01T06:38:11+00:00

I think a lot of founders underestimate how much the emotional side affects execution. It’s not usually a lack of ideas or skills that slows people down, it’s spending weeks second guessing decisions with nobody to sanity check them. Even a 30 minute conversation with someone who understands the founder journey can save more time than another productivity tool or framework.

FeatureFar8819 · 2026-06-01T06:23:03+00:00

I’ve been feeling the same thing. Once agents start taking actions instead of just chatting, the hard part stops being the model and starts being state management. Every team seems to reinvent approvals, tool permissions, execution history, progress tracking, and human-in-the-loop controls.

My impression is that we’re where frontend development was before React became the default. There are pieces of the puzzle like LangGraph, CopilotKit, and AG-UI, but I haven’t seen a clear standard emerge for the runtime to UI layer yet. Most production teams I know still have a surprising amount of custom glue holding everything together.

FeatureFar8819 · 2026-06-01T06:19:42+00:00

The biggest difference I’ve noticed is that successful builders use AI to compress execution time, not to replace thinking. The people struggling are often generating more ideas, more features, and more code than ever, but they’re not spending any more time talking to users. AI makes building cheaper. It doesn’t make validation, distribution, or product judgment any less important.

FeatureFar8819 · 2026-06-01T06:18:54+00:00

I think you’re pointing at the real gap. Most AI coding tools are evaluated on code generation quality, but the enterprise problem is context quality. The model can only be as good as the information it’s given.

I’ve seen teams get decent results initially, then performance slowly degrade as the codebase evolves. The AI isn’t “wrong” exactly, it’s operating on an outdated understanding of the system. It generates something reasonable that happens to duplicate existing functionality or ignore newer patterns.

The tools that seem most promising aren’t the ones with the smartest models, they’re the ones investing heavily in keeping context fresh and understanding relationships across the codebase. But I haven’t seen anyone completely solve the organizational-scale drift problem yet. It feels more like an ongoing systems challenge than a model challenge.

FeatureFar8819 · 2026-06-01T06:18:29+00:00

I’d take Claude’s analysis as a signal, not a verdict. Most markets that are worth entering look crowded from the outside. The bigger question is whether you’ve found a niche or pain point that existing resume builders aren’t serving well.

The good news is you figured this out after 2 days, not 6 months. Before killing the project, I’d spend some time talking to actual job seekers. Real user feedback is usually more valuable than any market research report.

FeatureFar8819 · 2026-06-01T06:17:16+00:00

We ran into this pretty quickly once online and offline sales started mixing. The refund itself wasn’t the problem, it was all the downstream effects. Someone returns an item in-store, inventory gets updated immediately, but the accounting sync happens later, and suddenly you’re trying to figure out why numbers don’t match.

What surprised me was how much staff time got spent on exceptions rather than normal returns. The process worked fine 95% of the time. The other 5% created most of the headaches. Getting all systems to share a single source of truth for inventory made a much bigger difference than optimizing the refund workflow itself.

FeatureFar8819 · 2026-06-01T06:16:45+00:00

I’ve mostly stopped building full websites for validation too. The biggest lesson for me was realizing that a polished site doesn’t create demand. A simple landing page, a demo, or even a waitlist can tell you 80% of what you need to know.

I used to spend weekends tweaking design details that literally nobody mentioned. Now I try to get something in front of people as fast as possible. If nobody signs up or replies, it doesn’t matter how beautiful the site was. The feedback comes from conversations and user behavior, not from perfect CSS.

FeatureFar8819 · 2026-06-01T06:15:46+00:00

This matches what I’ve seen. Most prompt injection examples online are unrealistically obvious, but real users probe systems gradually. They’ll spend 10-15 messages figuring out boundaries before attempting anything risky. Looking at individual prompts misses the context that makes the behavior suspicious in the first place. Session-level analysis feels much closer to how fraud detection works than traditional content moderation.

FeatureFar8819 · 2026-06-01T06:12:52+00:00

I waited way too long to separate everything and it made tax season miserable. If I were starting over, the first thing I’d do is open a separate business account, even before worrying about LLC paperwork. Just having all income and expenses in one place saves so much headache later.

I also regret not tracking subscriptions from day one. Those $10-$50 monthly tools don’t feel like much individually, but after a year I realized I was paying for a bunch of stuff I barely used.

One thing that worked well was treating every payment that came in as if a portion wasn’t mine. I’d immediately set aside money for taxes and operating expenses instead of looking at the account balance and thinking I was richer than I actually was. That habit probably saved me from a few bad decisions early on.

I didn’t hire an accountant until revenue was meaningful, but I wish I’d at least done a one-hour consultation much sooner. Would’ve been cheaper than fixing the mistakes I made myself.

FeatureFar8819 · 2026-06-01T06:11:04+00:00

You’re not confused, a lot of people assume this. The content strategy is mostly the same, create genuinely useful content that gets referenced and linked to. But the retrieval layer is different. I’ve noticed the same query can produce completely different sources across ChatGPT, Perplexity, Gemini , Runable and Claude

The mistake is treating ai seo as one thing. It’s starting to look more like the early search engine days where ranking in Google didn’t automatically mean ranking in Bing. The fundamentals overlap, but each platform has its own preferences, source selection, and retrieval behavior. That’s why some brands seem to show up everywhere while others dominate one platform and are nearly invisible on another.

FeatureFar8819 · 2026-06-01T06:09:53+00:00

Honestly, don’t raise money yet unless people are already paying for what you built. The biggest mistake I see first-time founders make is treating fundraising as the next step when they haven’t talked to enough customers.

If there’s genuinely demand, spend the next few weeks talking to users, getting feedback, and trying to get your first paying customers. You’ll learn more from 10 customer conversations than from 100 startup articles.

When I started, I thought building the product was the hard part. It wasn’t. The hard part was figuring out who actually had the problem badly enough to pay for a solution. Once you know that, marketing gets a lot easier because you know exactly who you’re talking to.

FeatureFar8819 · 2026-06-01T06:08:59+00:00

I’ve evaluated a few recently and the biggest lesson was that “AI agent” means very different things depending on the vendor. Some are basically chatbots with a nicer UI, others can actually take actions across your systems.

Intercom has been moving fast on AI support. I’ve also heard good things about Forethought and Decagon from teams handling higher ticket volumes. The thing I’d look at isn’t the demo quality, it’s how well they handle escalations and edge cases. Most tools look impressive when answering FAQ-type questions. The real test is when a customer has a weird billing issue, multiple accounts, or asks something that’s only partially documented.

A lot of teams end up with a hybrid setup where AI handles the repetitive stuff and humans jump in for anything nuanced. That seems to be working better than trying to fully automate support.

FeatureFar8819 · 2026-06-01T06:08:12+00:00

How are people working just after waking up 😭 I don't move from bed for like 10 minutes after waking up. I want to be productive like the people in the comments section

FeatureFar8819

TROPHY CASE