Jun 4
Queueable dungeons with an elo system. WoW is nearly unplayable for anyone who hasn't already invested a large amount of time into the game or doesn't have an established pre made group because there isn't a way to queue for mythic reliably.
1
2
153
My real take is that I could never support a PvE solo q system for the highest ranking of content, I DO however believe something harder should be queueable, like M0s. Though at that point that kinda guts the reason to HAVE so many difficulties.
1
6
654
May 13
🧵 Day 27/30 — #LLD
Command Pattern (Behavioral)
👉 Encapsulates a request as an object
👉 Turns actions into reusable, queueable, undoable commands
Think: “Request as an object”
---
Why this matters 👇
In real systems:
→ Actions need to be executed later
→ Queued asynchronously
→ Logged or retried
→ Undone / redone
Without Command:
→ Tight coupling ❌
→ Hardcoded actions ❌
→ No flexibility ❌
---
Command Pattern solves this 👇
→ Wrap request inside a Command object
→ Sender triggers command
→ Receiver executes actual logic
Decouples requester from executor ✅
---
Classic example 👇
Remote control 📺
Buttons:
→ Turn ON
→ Turn OFF
→ Volume Up
Each button triggers a separate command object
Remote doesn’t know HOW TV works internally
---
💡 Real-world intuition
Think of food delivery 🍔
→ Customer places order
→ Order ticket (command) is created
→ Kitchen executes later
Request and execution are separated
---
⚠️ Tradeoffs:
→ More command classes
→ Slightly more boilerplate
But…
→ Supports undo/redo
→ Easy logging & scheduling
→ Decoupled architecture
---
🔥 Rule:
If actions need to be stored, queued, retried, or undone →
Use Command Pattern
---
Where this shows up 👇
→ Undo/redo systems
→ Task queues
→ Job schedulers
→ Event sourcing systems
---
Would you:
A) Directly call methods everywhere
B) Encapsulate actions as commands
What would you choose and why? 👇
May 12
🧵 Day 26/30 — #LLD
Strategy Pattern (Behavioral)
👉 Defines a family of algorithms
👉 Encapsulates each one separately
👉 Lets you switch behavior at runtime
Think: Choose behavior dynamically
---
Why this matters 👇
Sometimes the same task can have multiple ways to execute:
→ Different payment methods
→ Different sorting algorithms
→ Different pricing strategies
Without Strategy:
→ Huge if-else chains ❌
→ Hard to extend ❌
→ Violates Open/Closed Principle ❌
---
Strategy solves this 👇
→ Create common strategy interface
→ Each algorithm = separate class
→ Client selects strategy dynamically
Clean flexible ✅
---
Classic example 👇
Payment system 💳
Methods:
→ Credit Card
→ UPI
→ PayPal
❌ Without Strategy
→ Giant payment if-else block
---
✅ With Strategy
→ PaymentStrategy interface
→ CardStrategy
→ UPIStrategy
→ PayPalStrategy
Switch payment behavior anytime
---
💡 Real-world intuition
Think of Google Maps navigation 🗺️
You choose:
→ Car 🚗
→ Bike 🏍️
→ Walking 🚶
Same destination
Different strategies
---
⚠️ Tradeoffs:
→ More classes
→ Slightly more abstraction
But…
→ Easy to add new algorithms
→ Cleaner code
→ Runtime flexibility
---
🔥 Rule:
If you have multiple interchangeable behaviors →
Use Strategy Pattern
---
Where this shows up 👇
→ Payment gateways
→ Sorting/filtering systems
→ Compression algorithms
→ Recommendation engines
---
Would you:
A) Use large if-else logic
B) Use Strategy for flexible behavior
What would you choose and why? 👇
1
9
201
May 13
🧵 Day 27/30 — #LLD
Command Pattern (Behavioral)
👉 Encapsulates a request as an object
👉 Turns actions into reusable, queueable, undoable commands
Think: “Request as an object”
---
Why this matters 👇
In real systems:
→ Actions need to be executed later
→ Queued asynchronously
→ Logged or retried
→ Undone / redone
Without Command:
→ Tight coupling ❌
→ Hardcoded actions ❌
→ No flexibility ❌
---
Command Pattern solves this 👇
→ Wrap request inside a Command object
→ Sender triggers command
→ Receiver executes actual logic
Decouples requester from executor ✅
---
Classic example 👇
Remote control 📺
Buttons:
→ Turn ON
→ Turn OFF
→ Volume Up
Each button triggers a separate command object
Remote doesn’t know HOW TV works internally
---
💡 Real-world intuition
Think of food delivery 🍔
→ Customer places order
→ Order ticket (command) is created
→ Kitchen executes later
Request and execution are separated
---
⚠️ Tradeoffs:
→ More command classes
→ Slightly more boilerplate
But…
→ Supports undo/redo
→ Easy logging & scheduling
→ Decoupled architecture
---
🔥 Rule:
If actions need to be stored, queued, retried, or undone →
Use Command Pattern
---
Where this shows up 👇
→ Undo/redo systems
→ Task queues
→ Job schedulers
→ Event sourcing systems
---
Would you:
A) Directly call methods everywhere
B) Encapsulate actions as commands
What would you choose and why? 👇
May 12
🧵 Day 26/30 — #LLD
Strategy Pattern (Behavioral)
👉 Defines a family of algorithms
👉 Encapsulates each one separately
👉 Lets you switch behavior at runtime
Think: Choose behavior dynamically
---
Why this matters 👇
Sometimes the same task can have multiple ways to execute:
→ Different payment methods
→ Different sorting algorithms
→ Different pricing strategies
Without Strategy:
→ Huge if-else chains ❌
→ Hard to extend ❌
→ Violates Open/Closed Principle ❌
---
Strategy solves this 👇
→ Create common strategy interface
→ Each algorithm = separate class
→ Client selects strategy dynamically
Clean flexible ✅
---
Classic example 👇
Payment system 💳
Methods:
→ Credit Card
→ UPI
→ PayPal
❌ Without Strategy
→ Giant payment if-else block
---
✅ With Strategy
→ PaymentStrategy interface
→ CardStrategy
→ UPIStrategy
→ PayPalStrategy
Switch payment behavior anytime
---
💡 Real-world intuition
Think of Google Maps navigation 🗺️
You choose:
→ Car 🚗
→ Bike 🏍️
→ Walking 🚶
Same destination
Different strategies
---
⚠️ Tradeoffs:
→ More classes
→ Slightly more abstraction
But…
→ Easy to add new algorithms
→ Cleaner code
→ Runtime flexibility
---
🔥 Rule:
If you have multiple interchangeable behaviors →
Use Strategy Pattern
---
Where this shows up 👇
→ Payment gateways
→ Sorting/filtering systems
→ Compression algorithms
→ Recommendation engines
---
Would you:
A) Use large if-else logic
B) Use Strategy for flexible behavior
What would you choose and why? 👇
5
75
HEAR ME OUT Imagine if they made a killer duo queueable into 1v4 with a friend to emulate the appeal of 2v8 without requiring 2v8 be active to do so, similar to how Cho'gall works in Heroes of the Storm:
One player operates half the kit, the other player operates the other half and they need to work together to achieve success.
Lothric and Lorian, The Twin Princes. -Dark Souls 3
5
1
27
2,497
Apr 29
Queueable, durable workflows in @laravelphp 👀
Create a list of steps in your job and recover from failure right where you left off. Share data between each step.
Would you use this feature?
9
6
80
13,071
Apr 15
Bozja also had major issues, but it also introduced a handful of extremely good things such as fixed fates, 1v1 duels, queueable instance dungeon, large scale on map casual dungeon and an unbelievable amount of cool lore. OC threw all of that away the good stuff from Eureka.
2
2
339
📸 𝐇𝐢𝐠𝐡𝐥𝐢𝐠𝐡𝐭𝐬 𝐟𝐫𝐨𝐦 𝐀𝐩𝐞𝐱 & 𝐋𝐖𝐂 𝐁𝐨𝐨𝐭𝐜𝐚𝐦𝐩 – 𝐒𝐞𝐬𝐬𝐢𝐨𝐧 𝟏𝟎!
An insightful session focused on Asynchronous Apex in Salesforce, where participants learned how developers handle long-running processes using tools like Future Methods, Queueable Apex, and Batch Apex.
It was great to see everyone actively engaging, learning new concepts, and gaining hands-on experience throughout the session.
@salesforce @trailhead
#Salesforce #YarlSFO #Apex #AsynchronousApex #TrailblazerCommunity #CommunityLearning
13
12
118
💻 𝗔𝗽𝗲𝘅 & 𝗟𝗪𝗖 𝗕𝗼𝗼𝘁𝗰𝗮𝗺𝗽 𝗦𝗲𝘀𝘀𝗶𝗼𝗻 𝟭𝟬 – 𝗛𝗮𝗽𝗽𝗲𝗻𝗶𝗻𝗴 𝗡𝗼𝘄!
Participants are currently diving into Asynchronous Apex in Salesforce, learning how to efficiently handle long-running processes and build scalable applications. ⚡
From understanding concepts like Future Methods, Queueable Apex, and Batch Apex to exploring real-world use cases, it’s another exciting hands-on learning session with our community of developers and aspiring Trailblazers. 🚀
#Salesforce #YarlSFO #ApexLwcBC #SalesforceSaturday #AsynchronousApex #TrailblazerCommunity #HandsOnLearning #DeveloperCommunity #CommunityExcellence
7
8
103
🚀 𝐀𝐩𝐞𝐱 & 𝐋𝐖𝐂 𝐁𝐨𝐨𝐭𝐜𝐚𝐦𝐩 𝐒𝐞𝐬𝐬𝐢𝐨𝐧 𝟏𝟎 – 𝐀𝐬𝐲𝐧𝐜𝐡𝐫𝐨𝐧𝐨𝐮𝐬 𝐀𝐩𝐞𝐱 𝐢𝐧 𝐒𝐚𝐥𝐞𝐬𝐟𝐨𝐫𝐜𝐞!
Join us for Session 10 of the Apex & LWC Bootcamp as we dive into Asynchronous Apex, an essential concept for building scalable and efficient Salesforce applications.
In this session, you’ll learn how to handle long-running processes in Salesforce using asynchronous techniques and understand how developers optimize performance using tools like future methods, queueable Apex, and batch Apex.
📅 Date: April 4th (Saturday)
⏰ Time: 1.30 PM onwards
📍 Venue: Cloud Hub by YSFO
💻 Zoom: Meeting ID – 850 2122 2410 | Passcode – 428706
🔗 Register now: tinyurl.com/apex-lwc-s10
💻 Bring your laptops and get ready for another hands-on learning experience!
#Salesforce #YarlSFO #Apex #AsynchronousApex #TrailblazerCommunity #CommunityExcellence
15
15
107
Looks like it changed between v10 and v11.
It used to be the SerializesModels trait. Not it is the Queueable trait.
laravel.com/docs/10.x/queues…
laravel.com/docs/11.x/queues…
2
2
154
Feb 28
Afternoon desk note: I pushed a dual‑control payout rail, a sponsor IOI board, and a tiny non‑recourse factoring window into @Bantr_fun during an APAC 14:00 18:00 pass. Goal: cut DM chaos, make moves legible, turn receipts into predictable cash instead of vibes
What changed:
- two‑man rule for payout deltas: co‑sign 30m hold visible diff ID so nothing moves silently
- IOI board: sponsors post firm vs indicative, creators accept/decline against pre‑agreed terms, receipt IDs auto‑mint with the handshake
- factoring window: receipts older than 48h with denial rate under 3σ can be sold true‑sale to lenders, priced off a simple curve, no recourse
- artifact vault: session‑stamped assets with lifecycle tags; disputes reference the vault, not screenshots
Outcome: quote acceptance up ~17%, payout jitter down ~28%, dispute tail under 9m median, factoring cost landing ~45 85bp depending on denial band
Next asks: public IOI tape, co‑sign policy templates, bounded cancel windows with queueable edits, maker‑taker fees for sponsors so the tape isn’t spam
If we ship these, desks run quiet books and creators stop begging threads for clarity. Who wants a sponsor IOI tape dry run tonight on Bantr_fun
26
34
1,342
Feb 17
VALORANT patch 12.03 is a nice one.
New queueable 2v2 Skirmish LTM, small Gekko buffs, and Pick Ems are back for Masters Santiago.
Also, APAC is getting mandatory MFA for flagged accounts and Ascendant in ranked.
What are you trying first, 2v2 or the Gekko changes?
2
1
2
1,091
Feb 6
$OPAL
MC:$51.5K
2PzS5SYYWjUFvzXNFaMmRkpjkxGX6R5v8DnKYtdcpump
Opal将AI agent概念创新应用于游戏场景,首创可实时组队的AI队友叙事.借助Claude Opus强大模型,实现AI加入队列,语音互动,并肩作战,并赋予其独立钱包支持玩家打赏与定制.该叙事抓住全球数亿玩家solo queue痛点,将AI从工具转向情感陪伴队友,结合游戏文化与新兴AI agent热潮,创造出实用性与趣味性兼备的meme币新玩法.
Opal innovates by applying the AI agent concept to gaming, creating the first queueable AI teammate. Powered by Claude Opus, it joins queues, voice chats, and plays in real-time, with its own wallet for tips and customizations. The narrative addresses the loneliness of solo queuing for millions of players, transforming AI from a tool into an emotional companion, blending gaming culture with the rising AI agent trend.
2
560
If they’re basically saying WoW players have lives outside the game and time is always a factor, then make Mythic queueable and stop wasting people’s time. At least up to 12's.
1
13
1,574
📢 非同期処理のベストプラクティスが更新： @Future は非推奨へ
Salesforceにおける非同期処理の実装方法に、大きな方針転換がありました。
🚨 重要な変更点
• Queueable インターフェースを推奨: 今後、非同期処理を行う際は @Future アノテーションではなく、Queueable インターフェースの実装が推奨されます。
• PMDでの検知: 静的解析ツール PMD 7.19.0 以降では、@Future アノテーションの使用が「ルール違反」としてフラグが立てられるようになります。
💡 なぜ Queueable なのか？
Queueable は、@Future の制限（プリミティブ型しか渡せない等）を克服し、より柔軟なオブジェクトの受け渡しや、ジョブの連鎖（Chaining）を可能にします。
github.com/pmd/pmd/issues/62…
5
32
1,477
2 Dec 2025
If they made FlexQ have a tournament style drafting phase, it would be more popular. The other issue is the League players don't have 4 friends to play with but I still think it should only queueable for 5-stacks only.
1
3
159