Aniket Bindhani

I dont think someone who buys watches worth 40-50k would waste their time standing in this crowd

I just realised now that Mr Bean was british and not american. I always thought he lived in america Btw i still watch Mr Bean episodes sometimes.

Commit early, commit often! 🤓 ✅ Finish a sub-task? Commit. ✅ Reach a stable state? Commit. ✅ Fixed a bug AND updated docs not related to the bug? That’s TWO commits. Atomic commits = easier debugging and a cleaner history. Your future self will thank you.

@hellonehha I am currently 24 and i also get the fomo if i sleep early. I end up coding or learning something every night and stretch it till 3 in the morning

there was a time in my life when I used to sleep by 3-4am. I worked last few years to fix my sleep pattern. It was v hard for me to sleep by 10-11pm. reason was - I had fomo of leaving behind. I used to whole night just code, learn something , or keep doing something but now I just sleep by 10-11pm & I am v proud of it.

The big mistake by youtube was not removing dislikes count, it was introducing youtube shorts

@Prathkum I believe consistency is above all. Even if its 0.1% but showing up every day makes wonders we can’t predict on day 0. Took a long time to realise this

The fastest way to get better at anything is to stop chasing perfection and give yourself room to be messy. show up consistently, build rough things, make mistakes in public, and iterate as you go, because you can't improve something that doesn't exist.

@devsharmatwt Happens frequently. Even opening the lid daily leaves fingerprint near the webcam

I don't like macbooks just because of this. Any tip ?

@NanouuSymeon With ai tools hours have been the same(4-5) but productivity has sky rocketed

How many hours per day, do you code?

Rajma chawal

Csk is cooking today

Why is my entire feed filled with copy link not working tweets!!!🤯 X ios version is trash

@akshaymarch7 I wonder how most of the people in the comments have forgotten that today is 1st april

From May 2026 onwards, interview process in big tech (FAANG) companies is changing completely. This major change is because of the insane amount of cheating happening in interviews lately. Here’s what’s coming: 0. No DSA questions will be asked - With AI doing most of the work, it hardly matters if you can invert a binary tree anymore. 1. All interviews will be recorded - Mandatory camera ON. Facial recognition will be used to validate your identity. No more “my mic wasn’t working” excuses. 2. No resume required while applying - Instead, you’ll give an AI-proctored test. Your resume is now replaced by how you actually perform. 3. Live screen monitoring with AI detection - If your eyes move suspiciously or you keep looking somewhere else… instant RED flag 🚩 4. “Explain your code” round becomes the hardest round - You can use AI to write code. But now you’ll be grilled on every single line you submit. 5. One round where AI is allowed - Yes. You’ll be given access to claude code max subscription and evaluated on how effectively you use them to solve real-world problems. 6. Mandatory “build something” round - No more theoretical answers. You’ll be asked to build a small working feature live. 7. Background noise analysis using AI - That means if someone whispers “bhai answer yeh hai…” in the background… you’re out 😄 8. Random surprise round - Mid interview, a new interviewer joins and asks you to debug a completely different codebase. 9. “Why should we not replace you with AI?” round - No right answers here. This is a survival round. ... Launching a new course "Namaste Interviews" next week to prepare you, please write "interested" in the comments and you'll get a 50% discount code in your DM.

I just read about the attack on Axios. It was a supply chain attack. The attackers took over the lead maintainer's npm account and published malicious code into two versions, 1.14.1 and 0.30.4 The malicious code was basically a hidden dependency which was installed along with all the other dependencies. It was a package plain-crypto-js@4.2.1 So, if someone installs axios by npm install, updates the package or during rebuild the package pulls the latest version, the malicious dependency executed a script to deploy a remote access trojan (RAT) across all platforms windows, mac and linux. It gave the attackers full control of the machine, which means they could access api keys, ssh keys, affect the ci/cd workflow, etc. I have used axios extensively across a lot of my personal projects, and one project which is in production uses axios, but its been months i haven't upgraded. But whoever installed or updated during the attack time frame would have had their machines compromised.

Moving from Next.js to Spring Boot for my backend has come with a few massive "aha" moments. The biggest one so far while building CoWeave? Zero-code database queries. In the Next.js and Node world, talking to a database usually means one of two things: writing out raw SQL strings, or setting up an ORM like Prisma where you still have to explicitly write out the query logic step-by-step (like db.user.findUnique(...)). But with Spring Data JPA, I recently needed to find a user in my PostgreSQL database by their email. Instead of writing a query, I just typed this single line inside an interface: Optional findByEmail(String email); That is it. No implementation code. No SQL. Spring actually looks at the English name of the method (findByEmail), understands what I am asking for, and automatically generates the secure SQL query in the background. If I want to find a user by their username and status, I just name the method findByUsernameAndStatus, and Spring does the rest. It feels a bit like magic. It saves hours of writing boilerplate database code and keeps the backend incredibly clean.

Wth IS THIS REAL?? This is crazy!!! Its gonna start another pirate era

Often while starting a fullstack project, the main concern was choosing the right database. In the nodejs/nextjs ecosystem, choosing @MongoDB was the go to option. This time for my project I thought of going with @PostgreSQL . But downloading the heavy PostgreSQL installer, setting up pgAdmin, dealing with background services draining my laptop's battery, and eventually forgetting the password a month later. I didn't wanted to deal with all of these. Also I didn't wanted to go for a cloud hosted db option either. So while working on the backend, i decided to try "Docker Compose". Instead of installing a database directly, I wrote a simple 15-line "docker-compose.yml" file. Now, it just takes one command "docker-compose up -d" to spin up my database and in seconds I have a fully functional Postgres database running in an isolated container. When I am done coding for the day, I turn it off. My laptop stays clean, there are no weird port conflicts, and I never have to deal with a messy uninstallation again. As a solo developer, using Docker has been a game changer.

Starting a project in a new tech stack is always a humbling experience. Coming from Javascript and Nodejs, setting up backend for a new project usually means running "npm init", installing express and then manually structuring folders, routing and configurations. You start with a blank canvas. Recently while working on a new project with the Spring Boot framework, I was amazed by the way Spring handles bootstrapping feels like magic. Instead of building everything from scratch, I used the Spring initializr and in about 30 seconds, i just didn't give me a "package.json". It gave me a complete production ready architectural blueprint. The folders were set, the build scripts were ready and i could just start writing the actual business logic instead of setting configurations. There’s something beautiful about a framework that just says, "Here is the standard, now go build your product." Have you tried @springcentral framework for your projects?

Is @Reddit down?

Have you ever started a project, pushed it to Github, shared the repository link with people and then you realised you need to completely restart, restructure your folders and push entirely new code. Well i just ran into this issue while building my new project. I needed to wipe the starter code but absolutely had to keep the same repository link active. Here the command "git push --force" comes into the picture. Normally Git is highly protective of the commit history. It believes in cleanly merging changes. But when you add "--force", you are telling Github to "Ignore what you have, replace it entirely with what is on my local machine right now." When to use it - Completely overwriting a starter repository (Just like i did) When not to use it - Using it on a shared team branch. You would literally erase someones work

@HelloVyom Try in javascript

No DSA in Java