Pinned Tweet
LFT Coach, Assistant, Analyst
- Invite/VCL+
- Can make stratbooks, improve fundamentals, create micro plays, design macro systems
- Coached NA top 30+/EU/GC top 10+
vlr.gg/player/17415/prainex
I have coached for several years and know I can make impact at a high level
Prainex retweeted
LFT VCT/VCL Asst Coach/Analyst/Coach
Open to any regioN
After helping and learning from 3 teams and systems this year i am confident i can help any team in 2027
DM me or @Drunkenpony if interested
Prainex retweeted
This is the right move. Work or study while pursuing pro opportunities. Have a backup plan.
Streaming btw is probably the one career harder than pro play so I wouldn’t consider that a backup plan
Everything @LudwigAhgren is saying here is 100% fair and accurate. Let's do the math:
1. To support a Valorant challengers team like the 2026 M80 roster which won NA would be approximately $500k annually give or take. That's 5 players, 1 HC and 1 AC/Analyst on monthly salaries + travel etc.
For us to take this roster into the new ecosystem and compete we would have to make EVERY Cup + at least ONE Masters event to just break EVEN on the investment into the game. If we miss even 1 cup we are down six figures. If we miss a Masters its an even bigger hole.
Most teams cannot afford to take this risk for so little return. It's financial suicide.
We could just look to drastically reduce salaries but then you are just in a race to the bottom. Playing T1 Valorant is a full time job and you have to be able to pay people full time wages. I would rather go do something else than pay players a fraction of what their time is worth. It's sad because there are many t1 Valorant players in North America who will miss out on opportunities to have a career.
Sucks to even write that to be honest.
2. Competitive Integrity. This will be an 8 team league in Americas and there should be no doubt about that.
Any non-partnered team that has an inch of success or develops an amazing talent will lose those players at the first break in the season to partnered teams and have to start building chemistry over. Agents will insist on their players being moved to partner teams and if you try to retain them you will be holding them back. This is fair as the best salaries and financial opportunities will only come from partner teams.
This, even more so that the financial picture, is the real reason M80 will not compete in Valorant in 2027. It's just a completely unlevel playing field and that's not something we are interested in.
I got into esports because of Valorant. We launched M80 with a Valorant roster announcement. It breaks my heart to leave.
We love the game and the community and would love to return in an instant when things make more sense. I look forward to that day.
To clarify
Riot changed the way Valorant works so that any team can make/win an international tournament
But they chose 4 teams in NA to become partners
They give those teams millions of $$ AND a skin in the game (they get a percentage of sales)
If an unpartnered org builds a moneyball team that absolutely crushes at an international event- those players will be poached by a partnered org
It happened to us with Brawk and Mada going to NRG it is happening to C9 who just lost partnership and already letting their players shop around
I just don't know if it is worth competing in the esport long term as compared to investing into an esport with a truly open system
Prainex retweeted
You use a normal SQL database.
The end.
Recently I interviewed a Senior Engineer.
Strong candidate.
Kafka? ✅
Redis? ✅
Microservices? ✅
Distributed systems? ✅
Then I asked:
"You're building the inventory service for a flash sale.
Only 1 item left in stock."
Two users hit “Buy Now” at the exact same millisecond.
Both requests pass the “is available?” check.
Both create an order.
Both deduct stock.
Now you’ve sold 2 items when only 1 existed.
How do you guarantee you never oversell — even with concurrent requests, client retries, and partial failures?
"Just use a database transaction."
Doesn’t fully solve it if both requests read `stock = 1` before either writes, or if the response is lost and the client retries.
"Check stock before deducting."
What happens when both checks happen at the same time?
"Use Redis DECR and reject if it goes negative."
What happens if Redis is down, or the decrement succeeds but the order is never persisted?
Your turn:
How would you design this inventory reservation API so concurrent buyers and retries never oversell the last item?
There’s a specific distributed-systems concept behind this.
And you’ll encounter it everywhere inventory, tickets, seats, coupons, and limited resources are involved.
If this is how the tac timeouts are sounding like then @totallynotbalax I’m glad you got your revenge w/ LOUD 😂
Prainex retweeted
Replying to @myhfie
You've lost as soon as you start treating your ranked teammates like real humans instead of NPCs. Don't click the bad dialogue option with them



































