Ayush (@ayush__64) header
Ayush (@ayush__64) profile picture

engineer in the making. solves problems, ships projects. building https://nitter.cf/t.co/nU5EH6iixX

Bengaluru
Joined November 2024
Photo by Ayush (@ayush__64)Photo by Ayush (@ayush__64)Photo by Ayush (@ayush__64)Photo by Ayush (@ayush__64)Photo by Ayush (@ayush__64)Photo by Ayush (@ayush__64)Photo by Ayush (@ayush__64)Photo by Ayush (@ayush__64)Photo by Ayush (@ayush__64)Photo by Ayush (@ayush__64)
built ALFRED : an AI that manages your features you give it an idea. it clarifies it, writes the PRD, scopes the tasks, tracks the GitHub branches, and reviews every PR against its own acceptance criteria the merge button stays human. always. try it : alfred.ayushlabs.tech
6
6
2
31
3,375
You type zomato.com and your phone has no clue where that is. So it asks a DNS resolver: "What's the IP for this name?" If the resolver hasn't cached it, it asks a root server, then the .com servers, then Zomato's own name server. The IP comes back, the page loads. That's DNS: the internet's phonebook, turning names humans remember into IP addresses machines use.
5
Ayush retweeted
Just launched my portfolio: ayush64.me/ 🚀 Dark, minimal, and text-first. No clutter. Just my work, my projects, and what I’m building. I m actively looking for internship/fulltime opportunities . Would love your feedback.
7
3
13
297
Why can one Chrome tab crash while the others keep running? Picture two restaurants. Each has its own kitchen, fridge and stove. A fire in one doesn't touch the other. Those are processes: separate memory, isolated from each other. Now put three cooks in one kitchen. They share the fridge and stove, so passing ingredients is instant. But they can grab the same pan, and if one starts a fire, the whole kitchen shuts. Those are threads: units of execution inside one process, sharing its memory and files, each with its own stack, registers and program counter.
10
Small JS thing that bites in API code: JSON.stringify({ name: "Ayush", phone: undefined }) gives {"name":"Ayush"} The key just disappears. NaN becomes null, and so does undefined inside an array. If the backend needs to know a field was cleared, send null.
1
13
Just launched my portfolio: ayush64.me/ 🚀 Dark, minimal, and text-first. No clutter. Just my work, my projects, and what I’m building. I m actively looking for internship/fulltime opportunities . Would love your feedback.
7
3
13
297
If you press the up arrow 20 times to find an old command, try Ctrl+R. Type any part of it, like "docker" or "migrate", and it searches your shell history. Ctrl+R again goes further back, Enter runs it, an arrow key lets you edit it first. Works in bash and zsh by default.
16
You're halfway through cooking Maggi when the phone rings. You remember exactly which step you were on, take the call, then pick up right where you left off. The CPU does this constantly. Saving the running process's state (registers, program counter) into its PCB and loading another one's is a context switch. No useful work happens during it, so it's pure overhead.
17
Small JS thing: [10, 9, 1, 100].sort() gives [1, 10, 100, 9]. Default sort compares items as strings, so "100" comes before "9". For numbers pass a compare function: arr.sort((a, b) => a - b) Also sort() changes the original array. toSorted() gives you a new one.
20
Funniest comedian by a mile
Anish left the board to tell us it's CHECKMATE 😭😭
20
Since my college won't give an NOC, I'm only looking at remote internships. And remote listings need a lot more filtering, because a few of them are not really internships at all. These are the checks I'm going with before spending time on one: Does it ask you to pay anything? Registration fee, "training fee", paid certificate, laptop deposit. A real company pays you, not the other way round. This one is an instant no for me. Is the take-home a test or actual work? A small task with a clear scope and a time estimate, like "build this API in 4 to 6 hours", is normal. "Build the full landing page for our new client" or "add these three features to our repo" with no limit sounds a lot like free work with an internship label on it. Is the stipend written down? "Performance based" or "will discuss later" is not always a scam, early startups are genuinely tight on money. But I'd rather know before investing a week. Can you find real people? A company site, a product that exists, a LinkedIn page with actual employees, maybe a GitHub org with commits. If the only contact is a Gmail ID or a WhatsApp number, that's worth a second look. Is anyone going to mentor you? For a first internship, learning from someone who reviews your code matters as much as the stipend. A JD that only lists 12 technologies and zero mention of who you'll work with tells you something. Caveat: none of these alone proves anything. Plenty of good tiny startups have messy listings, no stipend range and a founder who replies from Gmail. I'm treating this as a list of things to ask about, not reasons to reject. Also, OSS and programs like GSoC are a decent remote alternative while hunting, since the work is public and someone actually reviews it. If you've done a remote internship as a student, what's one thing you wish you had checked before saying yes?
2
2
104
The best librarian never asks you where the book is. You just say: "Give me every Premchand book you have." You don't tell them which shelf to check first or how to search. They figure out the how. That's SQL. You describe what data you want, and the database decides how to fetch it: SELECT title FROM books WHERE author = 'Premchand'; SELECT reads rows, INSERT adds them, UPDATE changes them, DELETE removes them. CREATE and ALTER shape the tables themselves.
10
Most git panic is really one question: where does the mistake live right now? Git has a few places your change can sit. Your working directory (the files you're editing), the staging area (what you've git add-ed), and your local commits. Each one has its own undo, and using the wrong one is how people lose work. Edited a file and want it back to the last commit? git restore file.py Careful, this throws away those edits. No recycle bin. Staged something by mistake, like a .env or a random log file? git restore --staged file.py This only takes it out of staging. Your edits stay in the file. Just committed, but the message has a typo or you forgot one file? git add the file, then git commit --amend This replaces the last commit with a new one (new hash), so do it before pushing. Want to undo the last commit itself? git reset --soft HEAD~1 keeps the changes staged. git reset HEAD~1 (mixed, the default) keeps them in your files, unstaged. git reset --hard HEAD~1 deletes them. Think twice before this one. Need to switch branches but you're halfway through something? git stash, do your thing, then git stash pop. The big caveat: amend and reset rewrite history. On your own unpushed branch that's fine. Once a commit is pushed and others might have pulled it, use git revert instead, which adds a new commit that undoes the old one, so nobody's history breaks. Reading this list is easy. Remembering it while staring at a messed-up repo before a PR is harder. That's why chapter 2 of GitLingo, the browser git playground I made, is all about this: diff, restore, amend, reset and stash, where you type the real command and watch the file move between working directory, staging and commits. Free, no sign-up, works on phone. Link in the first reply. GSoC season is coming, and even if an AI agent writes your code, undoing a bad commit is still on .
1
44
Ever wondered how one doctor sees 40 patients a day without mixing them up? Every patient has a case file: ID, current status, where treatment stopped, medicines, reports. Your OS keeps the same file for every process. It's called the Process Control Block (PCB): process ID, state, program counter, CPU registers, memory info, open files. When the OS switches the CPU to another process, it saves progress in the PCB and later resumes exactly from there.
1
44
Slow horses is really peak . Very tight story line and excellent cinematography . Worth binge watching
Every Apple TV+ show I've watched, ranked from GOATED to GARBAGE
1
41
Saw @Hiteshdotcom website on how he managed to teach DSA through visualisation . Tried to do something similar . 🤞
Made a small thing for anyone starting GSoC prep: GitLingo. Learn git by typing real commands in the browser and watching your files move between working, staging, local and remote. No sign-up, works on your phone. gitlingo.ayushlabs.tech
25
Underrated way to understand a new codebase: read the tests before the source. Tests show what the code is supposed to do, with real inputs and expected outputs, often more clearly than the README. Bonus: running them first tells you if your setup even works.
8
Since there is a new job opening , i would like to take over as the new CEO
BREAKING: Nvidia $NVDA CEO Jensen Huang resigns.
2
38
GSoC prep note for today. Before picking an org to spend the next few months on, I want to check one boring thing first: is anyone actually home? A project can have thousands of stars and still have maintainers who haven't looked at an outsider's PR in months. If I spend weeks understanding a codebase and my first PR just sits there, that's time I can't get back before proposals open. So this is the checklist I'm planning to run on each org on my shortlist, all doable from GitHub and their chat in one evening: - Open the closed PRs and look at the last 10 merged ones. Are any from people outside the core team? How long did they wait for a first review? - Sort open PRs by oldest. A few old ones is normal. A long list of first-timer PRs with zero comments is a signal. - Check recent issues and see if new ones get any reply at all, even just a label or "can you share logs". - Read last cycle's ideas page. Does each idea have a named mentor, and are those people still active in commits or chat? - Join their Zulip, Discord or Matrix and just read for a few days. Are newcomer questions getting answered, or does everyone scroll past them? Some caveats, because this can be unfair. Maintainers are mostly volunteers with jobs and exams of their own, so one slow week means nothing. Look at a few months, not a few days. And a quieter, smaller org can actually be a better bet than a famous one, because a mentor there might have time to properly review your work instead of a crowd of applicants fighting for attention in one channel. What I don't want is to choose only by tech stack or brand name, and find out about review speed after I've already sunk a month in. People who've done GSoC, what did you check before committing to an org? Anything you wish you'd looked at earlier?
24