ਪੰਜਾਬ ਕਿੰਗਜ਼

Efforts are way better than promises.

[Johnny Midnight ⚡️ @its_The_Dr]

Nonchalant Lazy Goal.

[Suraj Sharma @suraj_sharma14]

If you can build these 12 Agentic AI projects.

You're hired.

Project 1: Structured Output Agent
Enforce Pydantic JSON schemas, validate tool responses, retry on parse errors, log validation failures.
→ Shows: You can make LLMs reliable not random

Project 2: RAG Agent with Citation Grounding
Retrieve context, generate answers with sources, flag low-confidence responses, fallback to search.
→ Shows: You can prevent hallucinations at scale

Project 3: ReAct Planning Agent
Observe → think → act → reflect loop, max iteration limits, self-critique, graceful degradation.
→ Shows: You can build agents that don't infinite loop

Project 4: Multi-Tool Orchestrator Agent
Dynamic tool registry, capability-based routing, permission scoping, parallel execution, conflict resolution.
→ Shows: You can coordinate complex workflows

Project 5: Memory-Enabled Conversational Agent
Short-term buffer + long-term vector recall, context compression, relevance scoring, cross-session sync.
→ Shows: You can build agents that remember users

Project 6: Human-in-the-Loop Approval Agent
Uncertainty detection → pause → request human input → resume with validated context, full audit trail.
→ Shows: You can build safe, compliant systems

Project 7: Cost-Aware Agent Router
Token budgeting per task, model routing by complexity/cost, early exit on confidence, cost-per-decision analytics.
→ Shows: You can reduce infra costs by 40-60%

Project 8: Event-Triggered Automation Agent
Listen to webhooks/queues, execute workflows on triggers, idempotent execution, dead-letter handling, retry logic.
→ Shows: You can build production automation not demos

Project 9: Multi-Agent Debate System
Multiple agents propose solutions, critic evaluates, voting/consensus logic, aggregator synthesizes with confidence.
→ Shows: You can orchestrate swarms not single agents

Project 10: Self-Reflective Agent with Auto-Eval
Execute → evaluate via LLM-as-judge → critique reasoning → regenerate with constraints, log improvement metrics.
→ Shows: You can build systems that improve over time

Project 11: Production Agent with Observability
Deploy with LangSmith/Arize tracing, latency/cost dashboards, alerting on loops/failures, canary testing, rollback.
→ Shows: You can ship to production not just localhost

Project 12: Open Source Agent Framework Contribution
Extend LangGraph/CrewAI/AutoGen with new pattern, write docs + demo, publish benchmarks, submit PR + tutorial.
→ Shows: You're a community builder not just a consumer

(Bookmark this)

happy building...

[ਪੰਜਾਬ ਕਿੰਗਜ਼ @T20WC2022]

@kartcric Better choice is 15 team world cup, 5 teams in 3 groups.

Top-2 qualify for Super 6.

Then 3 KOs

[yash.jsx @yashmp2004]

DSA Preparation Roadmap (From Zero to OA Ready)

1. Sliding Window: 3, 76, 209, 424, 567, 904
2. Two Pointers: 11, 15, 16, 18, 42, 167
3. Fast/Slow Pointers (Linked List): 141, 142, 19, 876, 160, 234
4. Binary Search on Sorted Data: 33, 34, 35, 153, 162, 704
5. Binary Search on Answer: 875, 1011, 410, 774, 1283, 1482
6. Hashing / Frequency Maps: 1, 49, 128, 217, 242, 347
7. Prefix Sum / Running Sum: 303, 560, 724, 930, 974, 523
8. Difference Array / Range Updates: 370, 1094, 1109, 1893, 1943, 2381
9. Monotonic Stack: 739, 496, 503, 84, 85, 901
10. Monotonic Queue / Deque: 239, 862, 1425, 1438, 1499, 1696
11. Heap / Top K: 215, 347, 692, 703, 973, 1046
12. Intervals: 56, 57, 252, 253, 435, 452
13. Greedy Scheduling / Sorting: 45, 55, 406, 621, 763, 134
14. Linked List Manipulation: 21, 23, 24, 25, 92, 138
15. Tree DFS: 104, 112, 113, 543, 124, 226
16. Tree BFS / Level Order: 102, 103, 199, 515, 637, 116
17. BST Problems: 98, 99, 230, 235, 450, 700
18. Backtracking Basics: 46, 47, 77, 78, 90, 39
19. Backtracking with Constraints: 40, 17, 79, 131, 51, 52
20. Graph BFS / DFS: 200, 695, 733, 994, 1091, 1254
21. Topological Sort / DAG: 207, 210, 802, 1462, 1203, 2115
22. Union Find / DSU: 547, 684, 1319, 1579, 990, 1202
23. Shortest Path: 743, 787, 1514, 1631, 1334, 1976
24. MST / Graph Greedy: 1584, 1135, 1168, 1489, 778, 1102
25. Trie: 208, 211, 212, 648, 677, 1268
26. Bit Manipulation: 136, 137, 191, 338, 268, 190
27. 1D DP Basics: 70, 198, 213, 322, 279, 300
28. Knapsack / Subset DP: 416, 494, 518, 474, 1049, 879
29. Grid DP: 62, 63, 64, 221, 931, 120
30. String DP / Sequence DP: 1143, 72, 115, 583, 97, 1312

How to use this list? 
- These numbers are Leetcode problem numbers
- Do 3 patterns at a time, not all 30 together.
- For each pattern, solve the first 2 to understand the idea, the next 2 to get repetition, and the last 2 to stretch yourself.
- After every pattern, write one reusable template from memory.
- Do not just “solve and move on.” Ask: what signal in the question pointed to this pattern?
- If you get stuck, revisit the same pattern after 3 to 4 days. Pattern recognition is built by spacing, not cramming.

[Dany. @godsplanbabby]

For me

[Dr. Maalouf ‏ @realMaalouf]

Muslim student asks: “Can I practice gay anal sex to widen my ass for a bomb?”

Muslim teacher answers: “Normally forbidden, but for jihad? Totally allowed!”

Is it just me, or they are all repressed and gay?

[trish @TrisH0x2A]

it is O(n²)

strlen has no way to know the string length without walking every byte to the null terminator
every loop iteration restarts from the beginning of the string
n iterations × n cost per strlen = n²

this is the actual patch submitted to PostgreSQL 12 in November 2019

the bug was in auth.c, the ident authentication loop
strlen was called inside the send() retry loop on every iteration

the fix is one line, cache the length before the loop

[ਪੰਜਾਬ ਕਿੰਗਜ਼ @T20WC2022]

@rohini_sgh @manishranjan Yes, but then isnt it a punishment for states controlling their population? How do you justify this?

[Punjab Kings @PunjabKingsIPL]

Life after PBKS wins 🫶

[ਪੰਜਾਬ ਕਿੰਗਜ਼ @T20WC2022]

@realpreityzinta @PunjabKingsIPL @prabhsimran01 @arshdeepsinghh @ShreyasIyer15 @RickyPonting In all these years, how you have stood with PBKS, motivates common fans like us to not loose hopes. We had a horrific decade but we all were, you were there, for the team, by the team, waiting for our time. you made it possible. Can’t express how long we waited for this. Takk!

[ਪੰਜਾਬ ਕਿੰਗਜ਼ @T20WC2022]

@bcci_x PBKS have chased 262

[- @arkaneeeeee]

Yeh kya haiiii 😭😭😭😭

[ਪੰਜਾਬ ਕਿੰਗਜ਼ @T20WC2022]

@oj4tta Thats exactly how RCB cracked the cheatcode in 2025 Final

[Wolf of X @WolfofX]

Kid given another hotdog the next game after losing a hotdog the previous game

[ਪੰਜਾਬ ਕਿੰਗਜ਼ @T20WC2022]

@AzeemRafiq30 @sunrisersleeds @ECB_cricket Only 4 Indian owners, but what about other 4 English owners ?Why did they not pick pakis in W100?

[ਪੰਜਾਬ ਕਿੰਗਜ਼ @T20WC2022]

@GongR1ght Why did non-Indian owners not pick him?

Please explain.

[ਪੰਜਾਬ ਕਿੰਗਜ਼ @T20WC2022]

@AjayJadeja171 @MichaelVaughan

[ਪੰਜਾਬ ਕਿੰਗਜ਼ @T20WC2022]

@Merovaeous @kartik_kannan But we can keep PCA as Test venue? Its perfekt with those bigger boundaries and lush green outfield

[Makakmayum @makakmayum_sid]

As a Backend engineer, learn below to move beyond CRUD APIs:

→Security
a. Authentication & Authorization
b. Cryptography
c. Encryption Algorithms
d. OWASP Top 10
e. SIEM, IDS, IPS, etc.
f. misc: OAuth 2.0, JWT, etc.
g. CORS
h. Security headers(CSP, HSTS etc.)
i. Input validation

→Performance
a. Caching strategies
b. Rate-limiting & Throttling
c. Load balancing
d. Chaos Engineering
e. Fault Tolerance

→Database Engineering
a. Query optimization
b. Indexing
c. Database trade-offs
d. Database transactions and isolation levels
e. Sharding and partitioning

→API Design
a. OpenAPI 3.0 standards
b. Restful & GraphQL API principles
c. Status codes, versioning, and pagination strategies

→Architecture & Paradigms
a. Monolith
b. Modular monolith
c. Microservices
d. Serverless vs. Native
e. Concurrency & parallelism
f. Multithreading
g. Optimistic and pessimistic locking

→Distributed systems
a. Microservices patterns
b. Event-driven approach
c. Serverless vs native approach
d. gRPC & Protobuf
e. Kafka/RabbitMQ

→ DevOps
a. CI/CD
b. Containerization
c. Understanding of SLAs
d. Incident Management

→Observability
a. Logging, monitoring, and tracing
b. Profiling & optimization
c. Alerting

→Miscellaneous Microservices topics
a. API Gateway
b. Reverse proxy
c. Circuit breaker Pattern
d. Retry/back off patterns
e. Background jobs/Scheduling

These will help you make outstanding backend systems that are secured, meet SLAs, and are highly tolerant.

[SumitM @SumitM_X]

Service based Interview Questions shared by a 5 year experienced Java developer :

1. What is CompletableFuture and when do we use it?

2. Difference between Future and CompletableFuture

3. Internal working of HashMap

4. HashMap vs ConcurrentHashMap

5. How Java Memory Model works?

6. What is volatile keyword?

7. How does Spring Boot Auto Configuration work?

8. How do we handle transactions in Spring Boot applications?

9. Propagation and Isolation levels in Transaction Manager

10. What is Dependency Injection?

11. An application is slow due to JPA. How do you fix it?

12. What is Dirty Checking?

13. How is JPA different from Hibernate?

14. How can we implement DTO projection in JPA. Write a query.

15. Two microservices share the same database. Is it a good approach?

16. Two microservices updating the same database row at the same time. What happens?

17. If one microservice is down, how does it impact system performance?

18. How do you improve application performance?

Programming Questions

a. Permutations of a String "abc"
b. Check if a string is balanced or not "{[()]}"

HOW MANY CAN YOU ANSWER ?