RajuGangitla

It just took me half an hour to write 116 unit tests and 51 integration tests. peak productivity with AI

@itsZafeer @alvinsng I'm also trying

@alvinsng @Raju_dev0

Vibe Code → Deploy → Repeat

From the past two days, I have been trying to refactor an old code which was taking around 200 ms. After refactoring, the overall processing time went above 200 ms (200ms-300ms). Then I tried multiple approaches to optimize it again, but it was still around the same. Finally, I decided to move back to the old code. Sometimes we may over-engineer things while chasing these numbers. P.S.: This is what Claude is saying.

256 ms → 176 ms (opening a dialog) 240 ms → 48 ms (closing a dialog) Again, we are not talking about seconds to milliseconds optimization. This is the final level of optimization. In the below video, you can see that when I open a dialog, before optimizing it took 288 ms to load the dialog. After optimizing the code, it now takes 168 ms. This is great. Similarly, when closing the dialog, earlier it took 208 ms, and after optimization it now takes 48 ms, which is a significant improvement. Please let me know if you are interested in knowing what optimizations I have done.

@Sayyidalijufri @marclou @danmerrick117 Can you check your dm once

@Raju_dev0 @marclou @danmerrick117 ok i will give to to pay $10 to try for a month here you go: checkout.dodopayments.com/buy/pdt_0NZZZH… after you done the checkout check your email for the next guide then go to screensmooth.com/newuser

YESS, JUST SHIPPED v0.4 of my Screen Recorder (ScreenSmooth.com demo👇) ⏳ added progress bar when exporting ✨ added zoom animation duration 🚢 added: feedback button & roadmap page 🐛 fixed: video export truncation bug 🌟 and much more... and @marclou just become customer🥹🔥 (its ScreenSmooth.com - chrome extension screen recorder with auto zoom) video recorded using it:

@Sayyidalijufri @marclou @danmerrick117 ok let me try this for one month how can i pay ?

@Raju_dev0 @marclou @danmerrick117 if u want to switch between browser and application window while recording you can just use the entire screen yes manual zoom works on all

@Sayyidalijufri @marclou @danmerrick117 Can I switch between browser and application window right ? And also manual zoom works on both am I correct ?

@Sayyidalijufri @marclou @danmerrick117 Can I record only selected area ? Not only in browser in application window also?

@Sayyidalijufri @marclou @danmerrick117 Can you answer below questions 1) right now does it work with only websites ? 2) can I zoom it wherever i want or is it not configurable? 3) can I change between apps ?

@Raju_dev0 @marclou how about $10 for a month trial? like @danmerrick117

272 ms → 52 ms This is not about sec-to-ms optimizations. This is about reducing ms significantly. Before understanding properly, I had written the code in such a way that the dialog open state was maintained in the parent component. After that, I always follow the principle of keeping the state close to that component.

99% percent ? How did I miss this one percent ?

@imsethidev Open source?

Just started building my first project with React Flow 👀 No tutorials. No cloning. Just diving in and figuring it out as I go. I’ll be sharing the process, the mistakes, and the progress. Project details dropping soon

@faheem_khan_dev How come ? What is your thought process ?

@Raju_dev0 Yes I did answer correct one. 😀

Mercor AI interview question from round one Comment your answer. No GPT 👀 Q: What will the input boxes show after the first click? function List() { const [items, setItems] = React.useState(["A", "B"]); return ( <> setItems(["X", ...items])}> Prepend {items.map((item, i) => ( ))} ); }

@faheem_khan_dev After Gpt, I came to know that A,B,B Because of index tricky one though Did you answer correct one ?

@Raju_dev0 Think again

1 billion data inserts per day. 4 ClickHouse nodes. 2 shards. 2 replicas. 50 queries per second and 200 updates per second. Sharding ??? . Replication ???? . I heard these database terms many times. I understood them in theory. But I never actually worked with them in a real system. Did you ever feel the same? You read these terms, but never really build something using them. Today I tried to simulate a real-world production ClickHouse cluster using two machines. Check the diagram below to understand the setup better. Did I fully succeed in building it? Partially. I was able to set up the shards, replicas, and the cluster. I was able to seed the data and see it distributed across nodes. But I also failed in some parts. I faced real problems like networking issues, port configuration mistakes, and replication communication failures between nodes. This made me realize that distributed systems are not just about starting multiple nodes. The real challenge is making them communicate correctly, replicate data reliably, and stay in sync. Still learning. Still fixing. Still improving. Time to level up. @ClickHouseDB

@itsumeshk @runable_hq I lost the opportunity 🙃

4,000+ commits to main in the last 6 months. Started with 2 engineers, now 5. Looking for the 6th. We are hiring at @runable_hq for a Backend Dev. > Base: 30L–70L (based on performance only) > A really good amount of ESOPs in a super fast-growing company worth multiple crores by this year > Opportunity to work with the best engineers building AI from Bharat for the world Expectation: > Fast problem solver DM me here or apply at umesh@runable.com