Akshay kumar HP

FC Barcelona ❤💙
Messi 🐐❤💙

[Sofia khatun @sofia3973]

The only 3 types of cardio you need to lose fat.

1. Walking

[Khairallah AL-Awady @eng_khairallah1]

🚨 Anthropic just showed a 27-minute workshop on how to actually do prompts for Claude.

Taught by the people who built it.

Free. No registration. No paywall.

I've seen $300 courses that don't cover what they teach in the first 8 minutes.

Watch it and bookmark it now.

[Akshay kumar HP @akshayhp11]

@damzychillin @grok

[Dmitrii Kovanikov @ChShersh]

Software Engineers who made grep, cat, cut, find, ls, less, and sed really cooked here.

50 years later and it’s still bread and butter of data analysis.

And it still works better than most of bloated alternatives.

[𝑺𝒉𝒆𝒃𝒂𝒔 @Shebas_10dulkar]

𝗞𝗢𝗛𝗟𝗜 now has 83 Intl Centuries

𝗙𝗼𝗿𝗺𝗮𝘁 𝗪𝗶𝘀𝗲
52 - ODI*
30 - TEST
1 - T20I

𝗢𝗽𝗽𝗼𝗻𝗲𝗻𝘁𝘀 𝗪𝗶𝘀𝗲
17 - AUS
15 - SL
12 - WI
9 - NZ
9 - SA*
8 - ENG
7 - BAN
4 - PAK
1 - ZIM
1 - AFG

𝗖𝗼𝘂𝗻𝘁𝗿𝘆 𝗪𝗶𝘀𝗲
39 - IND*
12 - AUS
7 - SL
6 - BAN
6 - WI
5 - SA
3 - ENG
2 - NZ
2 - UAE
1 - ZIM

𝗬𝗲𝗮𝗿 𝗪𝗶𝘀𝗲
11 - 2018
11 - 2017
8 - 2014
8 - 2012
8 - 2023
7 - 2019
7 - 2016
6 - 2013
4 - 2015
4 - 2011
3 - 2010
2 - 2022
2 - 2025*
1 - 2009
1 - 2024

𝗔𝗴𝗲 𝗪𝗶𝘀𝗲
21 - 3
22 - 4
23 - 8
24 - 6
25 - 5
26 - 8
27 - 5
28 - 10
29 - 13
30 - 7
31 - 1
32 - 0
33 - 1
34 - 7
35 - 2
36 - 2
37 - 1*

𝗥𝗲𝘀𝘂𝗹𝘁 𝗪𝗶𝘀𝗲
59 - Won*
14 - Lost
9 - Drawn
1 - Tied

𝗨𝗻𝗱𝗲𝗿 𝗘𝗮𝗰𝗵 𝗖𝗮𝗽𝘁𝗮𝗶𝗻
41 - Under Himself
25 - Dhoni
9 - Rohit
3 - Sehwag
3 - Rahul*
1 - Gambhir
1 - Bumrah

𝗜𝗻𝗻𝗶𝗻𝗴𝘀 𝗪𝗶𝘀𝗲
43 - 2nd Inning
34 - 1st Inning*
4 - 3rd Inning
2 - 4th Inning

𝗕𝗮𝘁𝘁𝗶𝗻𝗴 𝗣𝗼𝘀𝗶𝘁𝗶𝗼𝗻 𝗪𝗶𝘀𝗲
45 - 3rd*
33 - 4th
3 - 5th
1 - 2nd
1 - 6th

𝗗𝗮𝘆 𝗪𝗶𝘀𝗲
25 - Sunday*
5 - Monday
7 - Tuesday
11 - Wednesday
15 - Thursday
9 - Friday
11 - Saturday

𝗗𝗮𝘁𝗲 𝗪𝗶𝘀𝗲
1 - 1
2 - 4
3 - 1
4 - 0
5 - 4
6 - 1
7 - 1
8 - 4
9 - 1
10 - 4
11 - 4
12 - 1
13 - 3
14 - 1
15 - 7
16 - 5
17 - 4
18 - 3
19 - 3
20 - 4
21 - 4
22 - 2
23 - 3
24 - 5
25 - 0
26 - 3
27 - 1
28 - 3
29 - 2
30 - 2*
31 - 2

𝗠𝗼𝗻𝘁𝗵 𝗪𝗶𝘀𝗲
Jan - 11
Feb - 11
Mar - 5
Apr - 0
May - 0
Jun - 0
July - 8
Aug - 6
Sep - 5
Oct - 16
Nov - 10*
Dec - 11

𝗥𝗲𝗮𝗰𝗵𝗶𝗻𝗴 𝗖𝗲𝗻𝘁𝘂𝗿𝗶𝗲𝘀 𝗯𝘆 𝗛𝗶𝘁𝘁𝗶𝗻𝗴
1 run - 34
2 runs - 14
4 runs - 29*
6 runs - 6

𝗡𝗼𝗻-𝘀𝘁𝗿𝗶𝗸𝗲𝗿 𝗪𝗶𝘀𝗲
12 - Ajinkya Rahane
8 - MS Dhoni
7 - Suresh Raina
7 - Rohit Sharma
5 - Ravindra Jadeja
4 - KL Rahul*
3 - G Gambhir
3 - Kedar Jadhav
3 - Shreyas Iyer
3 - Axar Patel
3 - Hardik Pandya
2 - R Ashwin
2 - Yusuf Pathan
2 - Shikhar Dhawan
2 - Murali Vijay
2 - C Pujara
2 - Rishabh Pant
1 - Rahul Dravid
1 - Ishant Sharma
1 - Ambati Rayudu
1 - Stuart Binny
1 - Manish Pandey
1 - Jayant Yadav
1 - Dinesh Karthik
1 - Mohd Shami
1 - Vijay Shankar
1 - Umesh Yadav
1 - Bhuvneshwar
1 - Hanuma Vihari
1 - Nitish Reddy

𝗢𝗽𝗽𝗼𝗻𝗲𝗻𝘁 𝗖𝗮𝗽𝘁𝗮𝗶𝗻𝘀 𝗪𝗶𝘀𝗲
7 - Jason Holder
5 - Michael Clarke
5 - Steven Smith
5 - Alastair Cook
5 - Kane Williamson
4 - M Jayawardene
3 - Aiden Markram*
3 - Faf du Plessis
3 - Dinesh Chandimal
3 - Aaron Finch
2 - Angelo Mathews
2 - Dwayne Bravo
2 - George Bailey
2 - Joe Root
2 - Kraigg Brathwaite
2 - Mushfiqur Rahim
2 - Misbah-ul-Haq
2 - Shakib Al Hasan
2 - Ross Taylor
2 - Brendon McCullum
2 - Dasun Shanaka
1 - K Sangakkara
1 - Darren Sammy
1 - Brendan Taylor
1 - Graeme Smith
1 - AB de Villiers
1 - Eoin morgan
1 - Rangana Herath
1 - Tim paine
1 - Lasith Malinga
1 - Upul Tharanga
1 - Mominul Haque
1 - Mohammad Nabi
1 - Liton Das
1 - Babar Azam
1 - Najmul Shanto
1 - Temba Bavuma
1 - Pat Cummins
1 - Mohammad Rizwan

𝗚𝗿𝗼𝘂𝗻𝗱 𝗪𝗶𝘀𝗲
5 - Adelaide
4 - Vizag
4 - Kolkata
4 - Pune
4 - Port of Spain, Trinidad
4 - Colombo (RPS)
4 - Mirpur
4 - Nagpur
3 - Mumbai (Wankhede)
3 - Ranchi*
2 - Delhi
2 - Guwahati
2 - Dubai
2 - Galle
2 - Chennai
2 - Melbourne
2 - Perth
2 - Centurion
1 - Wellington
1 - Hobart
1 - Chattogram
1 - Birmingham
1 - Kanpur
1 - Thiruvananthapuram
1 - Harare
1 - Dharamshala
1 - Indore
1 - Mohali
1 - Durban
1 - Bengaluru
1 - Hambantota
1 - Canberra
1 - Napier
1 - Ahmedabad
1 - Capetown
1 - Guwahati (Nehru)
1 - Rajkot
1 - Hyderabad
1 - Jamaica
1 - Jaipur
1 - Fatullah
1 - Antigua
1 - Cardiff
1 - Sydney
1 - Johannesburg
1 - Nottingham

[Sahn Lam @sahnlam]

How to Learn Backend Development?

[SumitM @SumitM_X]

As a Reactjs developer,

Please learn :

1. Advanced State Management
- Redux & Redux Toolkit
- Context API
- Recoil or Zustand

2. React Performance Optimization
- Memoization (React.memo, useMemo, useCallback)
- Code Splitting
- React Profiler

3. Component Design Patterns
- Higher-Order Components (HOCs)
- Render Props
- Custom Hooks

4. Server-Side Rendering (SSR)
- Next.js
- Hydration

5. TypeScript with React
- Type Safety
- Advanced Types and Generics

6. Testing
- React Testing Library
- End-to-End Testing (Cypress, Playwright)
- Mocking and Stubbing

7. React Ecosystem and Tooling
- Webpack and Babel
- ESLint and Prettier

8. API Integration
- GraphQL (Apollo Client, Relay)
- SWR and React Query
- WebSockets and Real-Time Updates

9. Authentication and Authorization
- OAuth and JWT
- Role-Based Access Control (RBAC)

10. Code Architecture
- Monorepos (Nx, Lerna)
- Micro-Frontends
- Atomic Design

11. Web Performance Optimization
- Lazy Loading
- Progressive Web Apps (PWA)
- Service Workers

[Ahmad @TheAhmadOsman]

- you are
- a random CS grad with 0 clue how LLMs work
- get tired of people gatekeeping with big words and tiny GPUs
- decide to go full monk mode
- 2 years later i can explain attention mechanisms at parties and ruin them

- here’s the forbidden knowledge map
- top to bottom, how LLMs *actually* work

- start at the beginning
- text → tokens
- tokens → embeddings
- you are now a floating point number in 4D space
- vibe accordingly

- positional embeddings:
- absolute: “i am position 5”
- rotary (RoPE): “i am a sine wave”
- alibi: “i scale attention by distance like a hater”

- attention is all you need
- self-attention: “who am i allowed to pay attention to?”
- multihead: “what if i do that 8 times in parallel?”
- QKV: query, key, value
- sounds like a crypto scam
- actually the core of intelligence

- transformers:
- take your inputs
- smash them through attention layers
- normalize, activate, repeat
- dump the logits
- congratulations, you just inferred a token

- sampling tricks for the final output:
- temperature: how chaotic you want to be
- top-k: only sample from the top K options
- top-p: sample from the smallest group of tokens whose probabilities sum to p
- beam search? never ask about beam search

- kv cache = cheat code
- saves past keys & values
- lets you skip reprocessing old tokens
- turns a 90B model from “help me I’m melting” to “real-time genius”

- long context hacks:
- sliding window: move the attention like a scanner
- infini attention: attend sparsely, like a laser sniper
- memory layers: store thoughts like a diary with read access

- mixture of experts (MoE):
- not all weights matter
- route tokens to different sub-networks
- only activate ~3B params out of 80B
- “only the experts reply” energy

- grouped query attention (GQA):
- fewer keys/values than queries
- improves inference speed
- “i want to be fast without being dumb”

- normalization & activations:
- layernorm, RMSnorm
- gelu, silu, relu
- they all sound like failed Pokémon
- but they make the network stable and smooth

- training goals:
- causal LM: guess the next word
- masked LM: guess the missing word
- span prediction, fill-in-the-middle, etc
- LLMs trained on the art of guessing and got good at it

- tuning flavors:
- finetuning: new weights
- instruction tuning: “please act helpful”
- rlhf: reinforcement from vibes and clickbait prompts
- dpo: direct preference optimization — basically “do what humans upvote”

- scaling laws:
- more data, more parameters, more compute
- loss goes down predictably
- intelligence is now a budget line item

- bonus round:

- quantization:
- post-training quantization (PTQ)
- quant-aware training (QAT)
- models shrink, inference gets cheaper
- gguf, awq, gptq — all just zip files with extra spice

- training vs inference stacks:
- deepspeed, megatron, fschat — for pain
- vllm, tgi, tensorRT-LLM — for speed
- everyone has a repo
- nobody reads the docs

- synthetic data:
- generate your own training set
- model teaches itself
- feedback loop of knowledge and hallucination
- welcome to the ouroboros era

- final boss secret:
- you can learn *all of this* in ~2 years
- no PhD
- no 10x compute
- just relentless curiosity, good bookmarks, and late nights

- the elite don’t want you to know this
- but now that you do
- choose to act
- start now
- build the models

[Tanvir @anjum_ai]

Learning java is so hard.

This note will make it easy to learn Java.

Get the most comprehensive Java guide available, with over 300 pages of chapter-wise notes.

For the next 24 hours, it is FREE.

To get it, just
1. Like.
2. Reply "Java".
3. Follow me for DM

[Himanshu @him_q14]

Use this structure for your SAAS Landing page

Thank me later

[TRÄW🤟 @thatstraw]

12 Git commands you must know

[Skilled Coder @theskilledcoder]

How Git Works Internally

[Python Programming @PythonPr]

RoadMap for becoming a Data Engineer !!

[Kartik @code_kartik]

Want to learn system design but don't know where to start from?

Use this resource by bytebytego.

[Skilled Coder @theskilledcoder]

How an LLM Works (End to End)

[Mohit Mishra @chessMan786]

Build a Linux From Scratch

[Makakmayum @makakmayum_sid]

If you are a backend engineer, you have to understand SOLID principle without any exception. I have received multiple dms asking me to explain it in an understandable way. So here we go. Save this, you'll thank me later.

SOLID is a set of five design principles that help developers create software that is easy to maintain, understand, and extend. Think of this like rules for building with lego bricks, and shouldn't fall apart when you add a new piece.

→S - Single Responsibility Principle
A class should have only one job or one reason to change.
How I remember: A screwdriver is designed to drive screws. It's not also a hammer and a saw. If you make it do too many things, it becomes complex and hard to use properly.

→O - Open/Closed Principle
Software should be open for extension, but closed for modification. Means one should be able to add new features without changing the existing, tested code.
How I remember: Your phone is "closed" because you can't change its core operating system. But it's "open" cause one can extend its functionality by installing new apps from the Play/App Store without breaking the phone.

→L - Liskov Substitution Principle
If you have a class A, any class B that inherits from A should be able to replace A without causing any errors. In short, child classes should be perfectly substitutable for their parent classes.
How I remember: If you have a universal remote control designed for a "TV," it should work whether you're pointing it at a Samsung TV or an LG TV. You can substitute one type of TV for another, and the remote still works as expected

→I - Interface Segregation Principle
Clients should not be forced to depend on interfaces or methods they do not use. It's better to have many small, specific interfaces than one large, general-purpose one.
How I remember: When you go to a restaurant, you don't get one giant menu with every food item in the world. You get a breakfast menu, a lunch menu, or a dessert menu. You only see what's relevant to you at that moment

→D - Dependency Inversion Principle
High-level modules (your main business logic) should not depend on low-level modules (like a specific database or a payment gateway). Both should depend on abstractions (like a generic Database interface).
How I remember: You don't wire a lamp directly into your house's electrical system. Instead, the lamp has a standard plug, and your wall has a standard socket. The plug and socket (the abstraction) allow you to switch out the lamp for any other appliance without rewiring your house.

[Raul Junco @RaulJuncoV]

Most engineers stay average because they practice code questions.
Top engineers get ahead because they practice system design questions.

These 20 aren’t trivia.
They’re the ones that reveal if you can actually scale, simplify, and ship.

Read them. Save them. Drill them.
Because the engineer who can design systems…
…owns the room.

Add more to this list.