Kunal @_devkunal

Me after Printing Hello World

a big part of the coding process is the refactors along the way. Scaling your solution to handle more edge cases, understanding why things need to be organized a certain way. You can't learn those lessons by outsourcing that journey. That makes you a user not a developer

@_pulkitxm Still, 28 hours is a crazy number.

@RhysSullivan The $2500 MacBook Pro I bought in 2012 that I used to write every single hashicorp 0.1 release. Arguably turned that $2500 plus some internet into like a billion dollars. Good trade.

Anthropic onboarding day: Michael Scott introducing Karpathy like he just signed Wemby in free agency.

@rauchg x.com/prisma/status/…

Prisma @prisma

3 weeks ago

Prisma Next is the version of Prisma ORM we would’ve created if we started from scratch based on the tech landscape of the late 2020s. And after months of hard work, it’s finally in Early Access 🚀 Run "npm create prisma@next" and try it today with @PostgreSQL or @MongoDB.

19 20 179 71K 50

-No girlfriend -Gym 5x a week -Same 3 friends -One delusional crush -8hrs work -Life is good

At one point my son and his friend kept looking for shortcuts to getting rich. Over and over I told them the way to do it is just to make something people want. If this is what I tell my own kids about getting rich, why won't politicians believe this is how a lot of people do it?

You can beat me at almost everything easily, but one thing you will find difficult to match is the number of hours I put in every single day. Maybe you can do it for a few days, but doing it for multiple years is different. Remember, motivation is overrated. Discipline is what builds you.

Passion.

ifti @DexterIfti

a month ago

Arpit sir, what is the "raaz" of your consistency 😊

0 0 7 10K 0

I don't know who needs to hear this. But no matter what language you are working on. You should definitely learn rust once in your lifetime. It teaches alot tbh. Learning rust makes you a better developer in your language.

writing code by hand feels like therapy in 2026

Some people are not slow learners. They just never sit with one problem long enough.

If you are doing anything serious you very quickly see the limits of these new AI models

What’s preventing you from coding like that? 🧐

I was working on a project in the last few weeks which required getting a huge amount of context, talking to many people, analyzing a lot of tradeoffs, understanding why certain decisions where made in the past. I was able to do it only because: - I made a list of ~30 questions (from first principles) that I wanted to get answers to. - There was amazing documentation available to get answers to most questions, talking to other helpful engineers helped answer the rest. - The amazing internal AI tools helped me to quickly find out resources to refer to, critique my ideas, and suggest potential exploration paths for the constraints I had defined based on the answers to my questions. Today, as an engineer, there is very little value in being able to solve a well defined problem and there is a lot more value in being able to solve a highly contextual and ambiguous problem. Yes, AI tools are amazing, but they only help if you ask them the right questions, which only comes from first principles thinking. The expectations from an engineer have never been higher. A junior engineer isn't expected to function like a junior engineer anymore, and the fact is that they're already working like a mid level engineer. If you're in college and looking to get into tech, you need to understand that nobody wants a copy paster, or heavy AI tool user. Companies want problem solvers who can solve ambiguous problems.

Frontend - Underrated Skill & Beautiful Skill ❤️ Mai products end-to-end khinch jata agar mujhe frontend ache se aata. - 1st us movement Mai bura hoon 😣 Merko nahi aata hai maza. - 2nd Us movement Harkirat said: “Mai kya karu, mai Keshav se puch ke batata hu” 😓 - 3rd Us movement At the end Harkirat accepted: “Frontend is a very underrated and polished skill too, but lekin mann nahi karta karne ka” 🤣 - 4th us moment again 🫂 Conclusion - Frontend aacha toh lagta hai but krne kaa maan nhi krta hai #frontend #backend #WebDevelopment

This C program uses branch prediction hints to optimize the hot path. The compiler can lay out code to favor the common case. Small change, measurable impact in tight loops.

ORMs are an anti-pattern once you start operating at scale. At scale, most move away from them as the abstraction that bridges the database and programming language never fully holds. At scale, by using ORM, you almost always end up missing native database optimizations. And if you are already writing raw queries to work around ORM limitations, you are actually better off using prepared statements directly. The ORM abstraction hides query complexity, yes, but it does make it easy to ship inefficient N+1 queries without realizing it. Debugging becomes painful at the worst possible time - during production incidents. ORMs tend to lag behind database features. Indexing strategies, query hints, and newer capabilities are either inconvenient to use (just look at prefetch in Django ORM) or simply unavailable. This makes you opt for the lowest common capability (as offered by ORM) instead of leveraging the database properly. At scale, explicit queries are always simpler, faster, and easier to optimize; the cognitive overhead of mapping objects to tables is often not worth it. To be fair, ORMs make sense for prototypes and for getting to market quickly. Use them when you are starting out or in the early phases, but have a plan to migrate away from them :) Easier said than done, though; been there!