arjun ✧

@herschelle___ alcohol is a cowards means to distraction, focus on your research

these days when i listen a good song, my brain goes "yk what would make this experience even better, ALCOHOL"

it's jjk day, no more jjk day from next week 🥀

@DweetParikh @kirat_tw @100xDevs in teeno chutiyo ka chehra dekh ke ghussa aati hai

woahh woaahh woaahh!!! @kirat_tw @100xDevs

@herschelle___ resonance jaake bhi nahi hua bhai

@ArjunIngole_ resonance alumini

i got 600 AIR last year GATE DA, my good friend got 178 AIR this year, two of my roommates are getting that bag since third year of btech, other two are doing masters in great indian institutes kill me tomorrow and I'll die in peace knowing i had such great friends

@AbhinavXJ greed is the biggest sin of all, never trust a course seller

Be striver > posts about filing FIR on some kid who pirated his course and was selling it > I quote it by saying if it's his first time he deserves atleast one chance > comes in my dm asking me to delete it > just coz I had a different opinion than him? He wants it to be deleted? > I deleted it out of respect last night > this morning calls me out for no reason, calling out my profession > Blocks me and everyone who didn't agree with him > Says he is going to delete his youtube channel > turns out to be a marketing stunt > Launches a sale right that moment to maximize revenue from this stunt all this coz I just had a different opinion than him seriously, I used to respect him a lot but finding out the kind of person he is just disappointing If he had even slight maturity he would have sorted it out on dms but nah let's make a post on me this morning I still stand by what I said. And to everyone who is worrying where they will study "dsa" if he deleted his channel trust me there are millions of other places you can learn it from one example is @kunalstwt playlist who teaches way better than him, link in reply my respect for kunal just increased today no wonder why he left all this behind Indian course sellers sucks and you need to stop licking their boots, and do something for yourself!

karanji

@prajdabre does it need to be exact?

Technical interview question: Suppose you have 5 TB worth of text data and you want to count the total number of words, how will you do this?

to ensure this doesn't happen, consider using baymax x.com/ArjunIngole_/s…

the fame got to him

website arjun-ingole.github.io/baymax/

introducing baymax for ai coding agents. scan your agent configs for risky permissions: - always-allow shell access - unsafe approval/sandbox defaults in codex - over-broad allowed tool rules in claude code run as a cli. fix interactively. re-scan until clean. fully open source

@HSVSphere and there's 2 more parts

"the website is down" >look inside >clueless marketing guy >dickn balls >lmfao

Introducing Vue Doctor for Vue/Nuxt. Scan your codebase for anti-patterns: - Composition API mistakes (watch/computed/reactivity pitfalls) - Accessibility issues - SSR + Nuxt boundary issues Run as a CLI or agent skill. Repeat until passing. Fully open source.

opensource at github.com/arjun-ingole/v…

Try it:  npx -y vue-doctor@latest .   inspired by react doctor by @aidenybai

-

@arpit_bhayani "the database has to hold locks on every row it touches for the entire duration of the operation" don't you think this is ideal? this should prevent dirty reads for any other transaction right?

Deleting a large number of rows (say, a million) in a single query feels efficient. It is not. It can crush your database. When we run a large DELETE in one go, the database has to hold locks on every row it touches for the entire duration of the operation. If it takes 30 seconds to run, those locks are held for 30 seconds. Every other query that needs those rows is stalled, waiting. On busy systems (high query or update load), this has a ripple effect. Reads pile up, writes get blocked, and your connection pool starts getting exhausted. This cleanup job will likely become a production incident :) There's also the transaction log (WAL) to think about. A massive DELETE generates a huge amount of log data in one shot, which can spike disk I/O and slow down replication. Your replicas can fall behind, sometimes significantly. The fix is pretty simple - batch your deletes. DELETE ... WHERE ... LIMIT 1000, then sleep for a small interval, then repeat. It's slower in wall-clock time, but the locks are short-lived, the log writes are spread out, and your database stays responsive throughout. Fun fact: Databases cannot protect you from yourself :) This is one of those things you learn once, usually the hard way. Don't ask me how I did :)

expecting butterflies with a garden full of dead flowers