Sagar Singh

2.1K posts

Sagar Singh banner
Sagar Singh

Sagar Singh

@_SagarSingh___

Building https://t.co/mNHZMcNuNM • Open Source Advocate 🚀 • Tweets about my coding journey

Durgapur, India Katılım Nisan 2023
984 Takip Edilen2.3K Takipçiler
Sagar Singh retweetledi
Abhishek Singh
Abhishek Singh@0xlelouch_·
I finally completed building @0xffdevs over the past few days - a learning platform for devs who want to code their way to financial independence. pathways for Go, Rust, Solana, system design. interview stories. a free system design canvas. jobs board. all free. We also launched a token on solana via market on @orynth so the crypto community can be a part of this ambitious, community driven project. Just a way for the community to have skin in what we're building together. Official CA(can be found on the wesbite too): 7bGT4zV1XfaDrjCGNDA5Tghsy83cJSaiqQhwmBBGory checkout 0xffdevs.com and start learning some niche skills, do checkout the roadmap for what's coming next! some exciting things in the pipeline!! Seeing some good growth for a platform launched yesterday
Abhishek Singh tweet mediaAbhishek Singh tweet media
English
3
8
62
4.4K
Sagar Singh retweetledi
jitesh💙
jitesh💙@Jitesh_117·
Hey! I am actively looking for a full-time backend engineer role, since my current stint would be coming to an end. I'm tech-stack agnostic, but I prefer Go or Elixir roles. A little about me: I am a backend engineer at heart, and I enjoy building and writing about backend systems. I like solving problems and am a Knight on LeetCode with a rating of 1875. I also run a blog where I write about my projects, Vim, Golang, and personal essays. It currently has 40K+ readers across 100+ countries. Over the past year, I have built and worked on some interesting things: - Currently building Postbox at Variant Systems, an AI agent-native form backend platform developed in Elixir - Amazon Dynamo implementation in Elixir with quorum replication, vector clocks, and gossip protocol - Tail at Scale in Go benchmarking p50/p95/p99 latency under failure scenarios - Brainrot Language Server in Go, an LSP for a slang-inspired language, featured in Golang Weekly Some other things that might be interesting: - 2x Kaggle Expert - Featured in Golang Weekly, Golang News, and Hacker News - Delivered a talk on fzf configuration and workflows at CLI Heroes, a developer event by One2C
English
70
116
493
30.1K
Abhishek Singh
Abhishek Singh@0xlelouch_·
The Oracle layoffs are a reminder that one hidden problem with switching jobs too aggressively for higher and higher roles is this: you keep moving up in title and salary, but you also quietly move yourself into a smaller and smaller market. At 12 LPA, 20 LPA, 30 LPA there are many openings. At 60 LPA, 80 LPA, 1 crore plus, suddenly the number of companies that can afford you drops very fast. Now add layoffs into the mix. When a company is cutting costs, the expensive mid-level or senior hire who joined recently is often at more risk than the person who has been there for 4 years with deep system knowledge. And the worst part is this: once you get used to a certain lifestyle, it becomes mentally very hard to go backwards. Your EMI does not want a career correction. Your ego does not want a lower title. Your family does not want a “temporary step down”. But the market does not care. So now you are stuck in a dangerous zone: too expensive for many roles, too junior for some leadership roles, and unwilling to come down. This is why blindly chasing the next package is not always a winning strategy. Better strategy is: switch with a reason, build rare skills, make sure your market value is backed by real depth, and save enough money so you are not negotiating from panic. A 40 LPA engineer with real ownership, calmness, and 18 months of runway is in a much stronger position than an 80 LPA engineer with no savings and no room to step down. More salary is good ofcourse. But with every jump, ask yourself: am i becoming more valuable, or just more expensive?
English
71
84
993
192.8K
Mohit.sol
Mohit.sol@mohitsatitwt·
Now I’m 100% sure I’ve been applying the wrong way. I need to figure out how to apply so that it actually works. Indeed and Glassdoor aren’t helping me even 1% in getting a job.
English
1
0
10
271
Aryan Srivastava
Aryan Srivastava@distroaryan·
@_SagarSingh___ Yeah you're right, I was a little wrong with my words there. Loki doesn't scrape cpu usage, ram usage loki is used for scraping logs like you mentioned query logs and prometheus is used for metrics like ram, cpu usage etc...
English
1
0
1
20
Sagar Singh
Sagar Singh@_SagarSingh___·
built grafana dashboard with 5 panels showing > error rate > success rate > p99 latency histogram > in flight request gauge > total requests rate next up fafo about loki
Sagar Singh tweet media
Sagar Singh@_SagarSingh___

> wrote a fast http server in go from scratch over tcp without the http lib > added worker pool for non blocking connection handling > wrote persistent connections / keep-alive > add prometheus to it > now i am going to collect sweet sweet metrics 😁😁

English
1
0
8
153
Sagar Singh
Sagar Singh@_SagarSingh___·
@distroaryan what i think is.. isn't prometheus better for scraping the metrics ? like isn't it better to separate concerns when we need metrics like cpu and ram utilization we go to prometheus , when we need to analyze/query logs we go to loki what is your take?
English
1
0
1
8
Aryan Srivastava
Aryan Srivastava@distroaryan·
@_SagarSingh___ Loki just scrapes more than logs like what is your cpu usage, what is your ram usage and more things other than logs we expose in code
English
1
0
1
29
Sagar Singh
Sagar Singh@_SagarSingh___·
> wrote a fast http server in go from scratch over tcp without the http lib > added worker pool for non blocking connection handling > wrote persistent connections / keep-alive > add prometheus to it > now i am going to collect sweet sweet metrics 😁😁
Sagar Singh tweet mediaSagar Singh tweet media
English
0
0
7
280
jitesh💙
jitesh💙@Jitesh_117·
publishing tomorrow!
jitesh💙 tweet media
English
3
0
58
680
Sagar Singh
Sagar Singh@_SagarSingh___·
Learning to instrument software today using open telemetry really fun , next blog is on instrumentation and observability , while i am at it i think why not add observability to my raft implementation too , going to do that as well and update here
Sagar Singh tweet media
English
1
0
6
90
Inosuke
Inosuke@Inosukeei_coder·
Be honest, Guys!! how many hours do you actually code daily? A) 0–1 B) 1–3 C) 3–5 D) 5+ No fake answers.
English
11
1
15
3.4K
Sagar Singh
Sagar Singh@_SagarSingh___·
@code_kartik Loll , i didn't notice the followers spike , good progress bro
English
0
0
1
107
Kartik
Kartik@code_kartik·
there are so many things which i can't discuss with this acc, because it's a big acc now. i am not able to use my acc like i use to do when i had just 300 followers. i guess everyone has this phase.
English
14
0
73
2.1K
jitesh💙
jitesh💙@Jitesh_117·
drank this for the first time and oh my god???
jitesh💙 tweet media
English
8
0
45
1.2K
Sagar Singh
Sagar Singh@_SagarSingh___·
@C_Kumar_Kartik great project bro , i built a similar project a while back but without the ai part , good work bro
English
1
0
1
19
Sagar Singh
Sagar Singh@_SagarSingh___·
stumbled upon this great article about go scheduler , runtime , memory model and under the hood story of what goes on behind the scenes : nghiant3223.github.io/2025/04/15/go-… give it a read, highly recommend
Sagar Singh tweet media
English
0
0
4
66
Sagar Singh
Sagar Singh@_SagarSingh___·
very recently i wrote a fast http server from scratch with connection pooling and then benchmarked it, i made some interesting observations i'll def write a blog on it, writing blogs are fun man !
English
0
0
3
59
Sagar Singh
Sagar Singh@_SagarSingh___·
one of the first things i struggled with was writing good errors that actually help in debugging wrote a comprehensive blog on error handling in GO , you'll def learn something new sagarsingh2003.github.io/blog/post.html… covers : - error bubbling - best practises - sentinel errors - Is() As()
Sagar Singh tweet media
English
0
0
10
82
Kartik
Kartik@code_kartik·
@_SagarSingh___ planning to do the same good for self reflection and progress as an engineer
English
1
0
2
114
Sagar Singh
Sagar Singh@_SagarSingh___·
have decided to work on my blogging and documenting skills going to post one blog/day for the next 21 days on the cool new tech that i have learnt over the past year and share whatever little knowledge i have very excited for it
English
1
0
10
215