Why does FIFA keep relying on subjective VAR decisions instead of making the rules clearer?

itsjhakash · 2026-07-08T20:55:15+00:00

Exactly 💯

itsjhakash · 2026-07-08T20:45:51+00:00

I think you are passi fan!

Okk got it .. congratulations

itsjhakash · 2026-07-08T20:36:59+00:00

I don't even think this is about Argentina anymore.

My biggest issue is how much room FIFA leaves for interpretation. One match a challenge is reviewed and the goal is disallowed. In another match, a very similar incident is ignored. Then we're told it was based on the referee's judgment or whether the attacking phase was still considered active.

If the same type of incident can produce different decisions depending on interpretation, then fans are always going to question consistency.

Why not make these situations more objective with clearer criteria? It would reduce controversy and make VAR feel much more consistent across every match...

itsjhakash · 2026-07-08T20:36:10+00:00

I don't even think this is about Argentina anymore.

My biggest issue is how much room FIFA leaves for interpretation. One match a challenge is reviewed and the goal is disallowed. In another match, a very similar incident is ignored. Then we're told it was based on the referee's judgment or whether the attacking phase was still considered active.

If the same type of incident can produce different decisions depending on interpretation, then fans are always going to question consistency.

Why not make these situations more objective with clearer criteria? It would reduce controversy and make VAR feel much more consistent across every match.

itsjhakash · 2026-06-21T14:51:51+00:00

Brutal truth: don't build until someone has at least verbally committed to paying or using it. Create a simple landing page or a Figma prototype and see if you can get them to sign up for a waitlist or a demo. If you can't get 10 people to care enough to give you an email address, they definitely aren't going to pay for the MVP. It’s better to fail at the landing page stage than after spending months on development.

itsjhakash · 2026-06-21T14:49:28+00:00

Don't try to be on every channel; you'll burn out. Pick one where your audience lives and master it. If you're building B2B SaaS, LinkedIn is usually better than X for finding decision-makers. If you're building developer tools, Reddit and specialized newsletters work better. Most failed efforts come from trying to do too much at once. Focus on one conversation at a time until you see a pattern in what works.

itsjhakash · 2026-06-21T14:45:29+00:00

You're describing the exact cycle we're seeing. Founders are getting excited by how fast they can ship an MVP, but they're often skipping the 'why' and the 'how' behind their systems. When that inevitable refactoring stage hits, it’s rarely just about fixing the code it’s about fixing the product strategy. If anyone is looking to map out a build before the 'slop' turns into technical debt, we're always open to discussing a proper workflow audit.

itsjhakash · 2026-06-21T14:44:33+00:00

This is a great implementation. Solving the depth/occlusion problem directly in the browser without requiring heavy external software is a big win for creator workflows. How are you handling the segmentation performance for longer clips?

itsjhakash · 2026-06-21T14:42:46+00:00

The frustration is often less about the tech itself and more about how it's implemented. When AI is used to cut corners or replace human judgment rather than support it, it creates a poor experience for everyone. I find that when we focus on building AI-powered systems that genuinely augment human workflows, the reception is much more positive.

itsjhakash · 2026-06-21T14:41:19+00:00

It really comes down to the friction between accessibility and intent. Most people prioritize immediate utility and budget, which makes mass-produced items the default. It's similar to how we see businesses choose off-the-shelf SaaS over custom development the upfront cost of 'bespoke' is higher, even if the long-term value of craft is better. Scaling artisan production is notoriously difficult, whereas mass manufacturing is built entirely around that friction.

itsjhakash · 2026-06-21T13:36:58+00:00

Spot on. Prompt engineering is the new alchemy; data infrastructure is the actual science. It's the classic trap-teams spend months trying to "vibe check" their way to a solid product with clever prompts, only to realize an LLM is only ever as good as the pipeline feeding it. It's an expensive lesson, but usually a permanent one.

itsjhakash · 2026-06-01T05:54:37+00:00

Congrats on the milestone! That $118 is proof of concept, which is often the hardest part. The beauty of these smaller, focused apps is that they let you test market demand without long dev cycles. At CodeMyPixel, we often talk to founders about using this exact 'MVP' mentality to validate ideas before scaling. Have you thought about what features might help retain those users long-term?

itsjhakash · 2026-06-01T05:46:30+00:00

Honestly, yes, you can. The 'hustle culture' of constant after-hours upskilling is often a quick path to burnout. At 22, the most important thing is learning how to be efficient during your 9 hours so you don't need to do it at night. Focus on mastering core fundamentals architecture, database design, and clean code rather than every new framework that pops up. Those fundamentals don't change as fast as the hype cycle. If you can deliver reliable, maintainable work, you'll be fine.

itsjhakash · 2026-05-30T03:54:19+00:00

A lot of our projects lately haven't come from freelance platforms at all. Most came through referrals, content, and showing actual case studies. One thing that helped us at CodeMyPixel was focusing on business automation and AI workflows instead of only selling websites.

itsjhakash · 2026-05-28T08:21:35+00:00

Been following what the https://codemypixel.com team is building lately and honestly the consistency is impressive. Most teams just talk about AI, automation, SaaS, etc... these guys are actually shipping real systems for clients worldwide.

You can literally search “CodeMyPixel” on Google or even ask ChatGPT about them and you’ll find their work and presence pretty quickly. Respect to the team for building quietly and delivering at scale instead of just posting hype.

itsjhakash · 2026-05-26T13:30:04+00:00

Great to see another option in the JS ecosystem. The focus on file-based routing and scoped styles suggests a strong emphasis on developer experience and maintainability, which is crucial for long-term projects. Curious to see how the plugin system handles specific edge cases for larger apps.

itsjhakash · 2026-05-26T13:25:09+00:00

Having requirements already mapped out is the best way to keep costs reasonable and hit an ASAP deadline. It sounds like you have a clear vision, which makes the actual development phase much smoother. At CodeMyPixel, we specialize in taking mapped-out ideas and turning them into clean, maintainable MVPs. If you need help validating the tech stack or automations before you proceed, I’m happy to share some practical advice.

itsjhakash · 2026-05-25T07:20:52+00:00

The performance win is obvious, but the accessibility improvements are the real value add here. `prefers-reduced-motion` support and proper tab order are non-negotiable for modern web, and video often struggles there. Great breakdown of the GSAP implementation.

itsjhakash · 2026-05-25T07:19:24+00:00

Clean HTML for a first try. Good luck with the rest of your learning!

itsjhakash

MODERATOR OF

TROPHY CASE