[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
#  @sriniously K Srinivas Rao
K Srinivas Rao posts on X about javascript, skim, careers, python the most. They currently have XXXXX followers and XX posts still getting attention that total XXXXXX engagements in the last XX hours.
### Engagements: XXXXXX [#](/creator/twitter::1421058930/interactions)
- X Week XXXXXXX +238%
- X Months XXXXXXX +78,519%
- X Year XXXXXXX +38,637%
### Mentions: X [#](/creator/twitter::1421058930/posts_active)
### Followers: XXXXX [#](/creator/twitter::1421058930/followers)
- X Week XXXXX +93%
- X Months XXXXX +851%
### CreatorRank: XXXXXXX [#](/creator/twitter::1421058930/influencer_rank)
### Social Influence [#](/creator/twitter::1421058930/influence)
---
**Social category influence**
[social networks](/list/social-networks) [technology brands](/list/technology-brands)
**Social topic influence**
[javascript](/topic/javascript) #11, [skim](/topic/skim), [careers](/topic/careers), [python](/topic/python), [loop](/topic/loop), [claude](/topic/claude), [breakthrough](/topic/breakthrough), [facebook](/topic/facebook)
### Top Social Posts [#](/creator/twitter::1421058930/posts)
---
Top posts by engagements in the last XX hours
"Most of us spend our entire careers writing code but never learn to read it. This is like trying to become a writer while refusing to read books. When you finally sit down with someone else's codebase REALLY sit down not just skim for the function you need. You start seeing patterns you never noticed in your own work. The way they handle error states their variable naming that actually makes sense six months later how they structure modules so changes don't cascade into chaos. There's this moment when you realize your "clean" code is actually just familiar garbage. Reading others' code is"
 [@sriniously](/creator/x/sriniously) on [X](/post/tweet/1943303192105881642) 2025-07-10 13:36:00 UTC 1677 followers, XXX engagements
"I spent two years building a homelab with Proxmox and it had a significant impact on how I interact with technology. Running your own infrastructure forces you to understand systems in ways that using cloud services never will of course learning and mastering cloud services is more valuable and will make you more employable but let's keep that aside for a moment. When your Proxmox cluster goes down you can't file a support ticket. You become the person who needs to know why. The most valuable lesson IMO wasn't about virtualization or networking protocols. It was about ownership in the deepest"
 [@sriniously](/creator/x/sriniously) on [X](/post/tweet/1945870357841457542) 2025-07-17 15:37:00 UTC 1687 followers, 1139 engagements
"You come from Python or TypeScript and decide to try Go. You want to build a simple API. In Express you'd write app.get('/users' handler) and be done. In FastAPI you'd use decorators and get automatic validation. In Go you open the net/http docs and find yourself writing twenty lines of boilerplate just to parse a JSON body. You think "there must be a better way" and reach for a framework like Gin or Echo. Then someone in the community tells you that's not idiomatic Go. Real Go developers use the standard library. They'll point you to some blog post about how frameworks are bad and you should"
 [@sriniously](/creator/x/sriniously) on [X](/post/tweet/1945461413591593471) 2025-07-16 12:32:00 UTC 2219 followers, 36.7K engagements
"Most JavaScript developers switching to Go often ask "where's async/await" and it reveals a fundamental misunderstanding of execution models. In JavaScript async/await exists because V8 runs on a single OS thread with an event loop. Every syscall would block the entire process so we needed continuation-passing style wrapped in promises. Async/await is syntactic sugar over state machines that compile function bodies into multiple resumption points yielding execution back to the event loop scheduler. Go doesn't need async/await because it implements M:N threading. The runtime multiplexes M"
 [@sriniously](/creator/x/sriniously) on [X](/post/tweet/1943937119266939087) 2025-07-12 07:35:00 UTC 2189 followers, 37.7K engagements
"Between Claude Code and Cursor the surface level difference is obvious. Claude Code lets you delegate entire workflows while Cursor keeps you in the driver's seat. Claude Code represents what I call the "delegation paradigm" where humans become orchestrators of AI capability. You describe the outcome you want and an AI agent figures out the implementation details. Cursor embodies the "augmentation paradigm" where AI enhances human capability but humans remain the primary decision makers at every step. It's about different theories of human-AI collaboration that will define how we work across"
 [@sriniously](/creator/x/sriniously) on [X](/post/tweet/1946115553191743540) 2025-07-18 07:51:19 UTC 2220 followers, 4207 engagements
"Been researching about Loki versus ELK stack lately for my upcoming Go boilerplate playlist and after going through a ton of resources I realized it comes down to one thing what do you value more simplicity or power ELK gives you everything. Elasticsearch handles search and storage. Logstash processes your logs. Kibana shows you pretty graphs. Three separate tools that work together like a well oiled machine. But here's the catch. You need to run three different services. You need to tune Elasticsearch clusters. You need to manage memory and disk space carefully. You need to understand how"
 [@sriniously](/creator/x/sriniously) on [X](/post/tweet/1946494125932683465) 2025-07-19 08:55:38 UTC 2221 followers, 1325 engagements
"I study the history of software because most people think code innovation happens in a vacuum. They see React and think Facebook just invented components. They miss the decades of work on MVC patterns the failed attempts at web components the slow evolution from server-side rendering to SPAs the quiet advances in JavaScript engines. When you know history you see that every breakthrough is built on a mountain of failures and incremental progress. Git exists because Linus got angry at BitKeeper licensing. Docker works because Google needed better process isolation and FreeBSD had jails. React"
 [@sriniously](/creator/x/sriniously) on [X](/post/tweet/1946970418696659053) 2025-07-20 16:28:15 UTC 2219 followers, 65.4K engagements
"The story of Go's garbage collector is one of the most remarkable engineering transformations in modern computing that I have ever studied about. When Go launched in 2009 its garbage collector would freeze applications for literal seconds making it unusable for any serious production system. Rob Pike and the team knew this was a problem but chose garbage collection anyway because manual memory management was simply too error prone for the kind of systems they wanted people to build. The early implementation was brutally simple stop everything mark all reachable objects sweep away the garbage"
 [@sriniously](/creator/x/sriniously) on [X](/post/tweet/1945309896188289428) 2025-07-16 02:29:56 UTC 2220 followers, 74.1K engagements
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
@sriniously K Srinivas Rao
K Srinivas Rao posts on X about javascript, skim, careers, python the most. They currently have XXXXX followers and XX posts still getting attention that total XXXXXX engagements in the last XX hours.
Engagements: XXXXXX #
- X Week XXXXXXX +238%
- X Months XXXXXXX +78,519%
- X Year XXXXXXX +38,637%
Mentions: X #
Followers: XXXXX #
- X Week XXXXX +93%
- X Months XXXXX +851%
CreatorRank: XXXXXXX #
Social Influence #
Social category influence social networks technology brands
Social topic influence javascript #11, skim, careers, python, loop, claude, breakthrough, facebook
Top Social Posts #
Top posts by engagements in the last XX hours
"Most of us spend our entire careers writing code but never learn to read it. This is like trying to become a writer while refusing to read books. When you finally sit down with someone else's codebase REALLY sit down not just skim for the function you need. You start seeing patterns you never noticed in your own work. The way they handle error states their variable naming that actually makes sense six months later how they structure modules so changes don't cascade into chaos. There's this moment when you realize your "clean" code is actually just familiar garbage. Reading others' code is"
@sriniously on X 2025-07-10 13:36:00 UTC 1677 followers, XXX engagements
"I spent two years building a homelab with Proxmox and it had a significant impact on how I interact with technology. Running your own infrastructure forces you to understand systems in ways that using cloud services never will of course learning and mastering cloud services is more valuable and will make you more employable but let's keep that aside for a moment. When your Proxmox cluster goes down you can't file a support ticket. You become the person who needs to know why. The most valuable lesson IMO wasn't about virtualization or networking protocols. It was about ownership in the deepest" @sriniously on X 2025-07-17 15:37:00 UTC 1687 followers, 1139 engagements
"You come from Python or TypeScript and decide to try Go. You want to build a simple API. In Express you'd write app.get('/users' handler) and be done. In FastAPI you'd use decorators and get automatic validation. In Go you open the net/http docs and find yourself writing twenty lines of boilerplate just to parse a JSON body. You think "there must be a better way" and reach for a framework like Gin or Echo. Then someone in the community tells you that's not idiomatic Go. Real Go developers use the standard library. They'll point you to some blog post about how frameworks are bad and you should" @sriniously on X 2025-07-16 12:32:00 UTC 2219 followers, 36.7K engagements
"Most JavaScript developers switching to Go often ask "where's async/await" and it reveals a fundamental misunderstanding of execution models. In JavaScript async/await exists because V8 runs on a single OS thread with an event loop. Every syscall would block the entire process so we needed continuation-passing style wrapped in promises. Async/await is syntactic sugar over state machines that compile function bodies into multiple resumption points yielding execution back to the event loop scheduler. Go doesn't need async/await because it implements M:N threading. The runtime multiplexes M" @sriniously on X 2025-07-12 07:35:00 UTC 2189 followers, 37.7K engagements
"Between Claude Code and Cursor the surface level difference is obvious. Claude Code lets you delegate entire workflows while Cursor keeps you in the driver's seat. Claude Code represents what I call the "delegation paradigm" where humans become orchestrators of AI capability. You describe the outcome you want and an AI agent figures out the implementation details. Cursor embodies the "augmentation paradigm" where AI enhances human capability but humans remain the primary decision makers at every step. It's about different theories of human-AI collaboration that will define how we work across" @sriniously on X 2025-07-18 07:51:19 UTC 2220 followers, 4207 engagements
"Been researching about Loki versus ELK stack lately for my upcoming Go boilerplate playlist and after going through a ton of resources I realized it comes down to one thing what do you value more simplicity or power ELK gives you everything. Elasticsearch handles search and storage. Logstash processes your logs. Kibana shows you pretty graphs. Three separate tools that work together like a well oiled machine. But here's the catch. You need to run three different services. You need to tune Elasticsearch clusters. You need to manage memory and disk space carefully. You need to understand how" @sriniously on X 2025-07-19 08:55:38 UTC 2221 followers, 1325 engagements
"I study the history of software because most people think code innovation happens in a vacuum. They see React and think Facebook just invented components. They miss the decades of work on MVC patterns the failed attempts at web components the slow evolution from server-side rendering to SPAs the quiet advances in JavaScript engines. When you know history you see that every breakthrough is built on a mountain of failures and incremental progress. Git exists because Linus got angry at BitKeeper licensing. Docker works because Google needed better process isolation and FreeBSD had jails. React" @sriniously on X 2025-07-20 16:28:15 UTC 2219 followers, 65.4K engagements
"The story of Go's garbage collector is one of the most remarkable engineering transformations in modern computing that I have ever studied about. When Go launched in 2009 its garbage collector would freeze applications for literal seconds making it unusable for any serious production system. Rob Pike and the team knew this was a problem but chose garbage collection anyway because manual memory management was simply too error prone for the kind of systems they wanted people to build. The early implementation was brutally simple stop everything mark all reachable objects sweep away the garbage" @sriniously on X 2025-07-16 02:29:56 UTC 2220 followers, 74.1K engagements