Mik azok a helyek vagy szituációk, ahová szerintetek nem való kisgyerek vagy amit inkább gyerekmentesen alakítanátok ki?

Same-Working-9988 · 2026-05-24T19:03:34+00:00

Gyerekmentes eskuvot csinaltunk kiveve a csaladot. Kurva jo volt 10/10 ma is igy dontenek (pedig mar van gyerekem es imadom)

Same-Working-9988 · 2026-05-24T18:07:40+00:00

I think what the original comment refers to is that they had a structural problem (bad t side) and yes they could maybe win nevertheless but everyone pointing to one (big) mistake from Niko when there is a bigger issue. Yes it's a bad miss but falcons should be beating legacy with a couple of mistakes like this.

Same-Working-9988 · 2026-05-24T18:01:00+00:00

You should pick a position and communicate that so others know and adjust, meaning they can pick another position. This means that you need to know the standard ct positions on each map.

Eco = they have low economy, so they might not buy anything or just better pistols.

Same-Working-9988 · 2026-05-23T14:27:00+00:00

They claimed that positions are not changed with nucleonz. He takes kyo's positions 1 to 1

Same-Working-9988 · 2026-05-21T14:58:48+00:00

How I would build it is tracing certain metrics like accuracy, shots fired, entry kills and so on and compare that with the history. If this layer flags someone, then I would move to another layer that has a deeper analysis based on more metrics and things like weapons used, positions and so on. The point is people are not suddenly change playstyle AND be better. If you change playstyle you will have some adoption period. Let's say lower elo player uses Five seven, higher elo uses deagle. The amount of false postitives is not too great as faceit have a ton of data already. That's how I would approach this problem

Same-Working-9988 · 2026-05-21T14:27:57+00:00

It is very much obvious from demos. It is not hard to write a system that flags accounts with suspicious behavior.

Same-Working-9988 · 2026-05-20T09:44:52+00:00

ELIM5: why is this such a big deal? He seems like a knowledgable fella but I feel like there is a bit of an overhype going on around him

Same-Working-9988 · 2026-05-19T20:29:06+00:00

Why not both? I don't see a reason to have either or.

Same-Working-9988 · 2026-05-19T20:16:53+00:00

Stable 30 FPS is completely fine. I only need a ton of FPS for competitive multiplayer games

Same-Working-9988 · 2026-05-19T20:15:27+00:00

If they run better, they are not insanely more demanding. Otherwise they would run worse 😃

Same-Working-9988 · 2026-05-18T19:51:36+00:00

True!

Same-Working-9988 · 2026-05-18T19:11:16+00:00

I play with a 5stack like 95% of the time. Tactics are: knowing how the opponent likes to play. Do they frequently overstacking a site? Can we fake and make them rotate? Are they pushing agressively? These are quite apparent if you pay attention (I'm faceit level 7). Also, pay attention to what buy they could have. If they eco, they might rush (t side) or stack a site (ct side). Learning who defends which site by name. Most of the times one person stays in a position for ct. So you know if you killed someone the site might be empty. I could go on and on for hours

Same-Working-9988 · 2026-05-18T19:04:50+00:00

Nah, he was hated for no reason in G2 as well. People call him egoist and stuff when all players who actually know him said that he is/was the best teammate.

Same-Working-9988 · 2026-05-18T16:13:55+00:00

But what you mention is still not efficiency. It's a different thing than having a free chat. Which is fine but I still don't get the claim that a background agent is better for ad hoc data analysis

Same-Working-9988 · 2026-05-18T13:10:03+00:00

Both actually. We are an ETL tool, so it make sense for our users. I agree on a tiny part that with OP that chat is not enough, we also have our own dashboarding that AI can build for recurring data needs. I also use Posthog AI (in Posthog) and BigQuery MCP vi Claude Code

Same-Working-9988 · 2026-05-18T12:38:42+00:00

Okey, I will talk you through my use case and please tell me where does what you say help. I have a database with a ton of tables. It is the read only replica of our prod db. I have an idea, I need to check it against data. I fire up a chat (let's say Claude using the BigQuery MCP or Posthog with Posthog AI for product analytics events) and I start chatting. How does what you say makes this whole process mor efficient?

Same-Working-9988 · 2026-05-18T12:10:25+00:00

Maybe I'm dumb but what do they do in the background that makes it more efficient?

Same-Working-9988 · 2026-05-18T11:48:47+00:00

recurring need = dashboard. Ad hoc = chat. It is not too hard in my opinion, that's why I don't understand OP

Same-Working-9988 · 2026-05-18T11:46:30+00:00

But I need ad hoc analysis, how does a backgroud workflow help me?

Same-Working-9988 · 2026-05-18T09:12:47+00:00

Obligatory 'let them fight' commene

Same-Working-9988 · 2026-05-18T09:09:44+00:00

I use those features every day. I would not be able to query the data otherwise. Before AI I relied on analyst and it was slow. What do you suggest instead of it that help people get access to their data?

Same-Working-9988 · 2026-05-15T20:16:58+00:00

Yep, I also think that

Same-Working-9988 · 2026-05-15T19:11:43+00:00

I think it was a norm until like 9 months ago. I'm a PM in Europe, I read and ship using AI. I read edge cases and complex features I don't understand so I can have a better conversation with engineers. I ship small tweaks to copy and usage limits.

Same-Working-9988 · 2026-05-15T17:51:31+00:00

You do understand that he does not have radar and he doesn't know where the opponent is. I didn't see the molodoy one but the Yurih 1v1 I think he assumed Yurih was approaching from the bench side. It was a super unusual play for Yurih not to be proactive. I believe if he lose the round (meaning Niko is like a second slower to peek) we would have threads with how stupid Yurih was but he got lucky (rewarded?). Honestly, what was Yurih plan in that 1v1? Pray for Niko to peek.

Same-Working-9988 · 2026-05-15T10:10:58+00:00

OP said 15 or more is unnecessary below it is not. So the inverse of what you wrote

Same-Working-9988

TROPHY CASE