keyur paralkar

A quick update: No more arrows getting latched at mid points of rect. Now arrows can smoothly revolve around their bound shapes on movement!! It's amazing to see that how a simple eq. of a straight line: y = mx + c, helped me solve this. 🚀 Here is the before and after comp:

Tip: Figure out your personal ceiling for running multiple agents in parallel. We need to accept that more agents running doesn't mean more of _you_ available. The narrative is still mostly about throughput and parallelism, but almost nobody's talking about what it actually costs the human in the loop. You're holding multiple problem contexts in your head at once, making judgment calls continuously, and absorbing the anxiety of not knowing what any one agent might be quietly getting wrong. That's a new kind of cognitive labor we don't have good language for yet. I've started treating long agentic sessions the way I'd treat deep focus work: time-boxed and tighter scopes per agent dramatically change how much mental overhead each thread carries. Finding your personal ceiling with these tools is itself a skill and most of us are going to learn it the hard way before we learn it intentionally.

Our errors are now agent-readable. Coding agents needed a lot of context to figure out what to do from a plain error and status code. So today I am shipping structured error messages, built for agents. Every error now has five fields: message, code, status, details, and suggestions. Details tell exactly which field or value caused the issue. Suggestions point to the right docs to fix it. Saving tokens for you!

When Opus 4.5 came out, it was a one-way door to a new way of engineering. Agents now do most of our coding. Knowing the inherent flaws and over-confidence of LLMs, we sent a clear message to our teams. Vibing and mission-critical infrastructure don’t go together. We’re sharing some of our early internal guidance in how we’re “agenting responsibly”, prioritizing security, durability, and availability at all times. vercel.com/blog/agent-res…

reflecting on 1 year of building and growing Orshot what a pleasure and satisfying journey it's been so far! recap and learnings 👇

I work on a browser rendering engine. I write Rust. No, it's not frontend, backend or systems engineering. I have struggled to explain what I do. So here's my attempt. You know when you write "display: flex" in your CSS and it just works? Someone had to make it work. Here's how a language feature goes from idea to your screen: Someone proposes a new feature in HTML/CSS/JS language. for example a new CSS property or a new way to handle text. A standards body (W3C for CSS, WHATWG for HTML, TC39 for JavaScript) discusses it, debates it, refines it. If it gets accepted, they publish a specification. A document that describes exactly how the feature should behave. Now browser engines (Chrome uses Blink, Firefox uses Gecko, Safari uses WebKit, and there's Servo which is written in Rust) need to actually implement it. Someone reads the spec, writes the code in the engine that says "when you encounter this property, here's how to calculate it, here's how to lay it out, here's how to paint it." Then it gets tested against thousands of web platform tests. Then it ships in a browser release. Then you install a browser update. Then you write that CSS property in your project. Then your users see it render correctly on their screen. That middle step, turning the specification into working code inside the engine, that's what I do. These days I am working on making sure one is able to debug things in Servo DevTools!

Protip: if you want to understand why more elements paint than expected (to compare rendering libraries, for example), you can use the Layer tool inspect it. hint: it's css, not javascript

More than a year ago, my health was bad. My focus span was a joke, motivation was low, annoyed and depression was knocking my door. What i did was simple: > deleted instagram, and X > started reading books (everyday) > stop following rage bait content and content creators. > cleaned my yt, and social media feed > delete all social media apps from mobile > call friends (real friends) weekly to talk > when was get the urge to check reels..I either go for a walk or read a book. things started changing. Apparently the continues stream of unasked information was the culprit.

Politics at work gets a bad reputation. Most people hear the word and think of manipulation, backstabbing, or someone taking credit for their work. That association is not wrong, but it is incomplete. There is a version of politics that is just noise - people optimizing for visibility over value. But there is another version that is simply influence - getting your ideas heard, understood, and acted on. The difference comes down to intent. Politics, in the negative sense, is about protecting yourself or advancing at someone else's expense. Influence is about helping the right things happen, even when you do not have direct authority to make them happen. If you have ever had a great idea die in a meeting, it was probably not because the idea was bad. More often, it is because there was not enough alignment built around it before everyone got in the room. That is influence work. The engineers who move fast over the long term understand this. They do not just write good code. They know how to bring people along with them. Good influence is not politics. It is how good ideas survive contact with an organization.

retweeting for reach. Koi to dekh lo 🙏🏽😂

wise words from the best systems engineer I've worked with: "two things that make code actually maintainable: 1. reduce the layers a reader has to trace 2. reduce the state a reader has to hold in their head" applies to every codebase. always.

just onboarded first Enterprise customer at Orshot! this customer also happened to validate a new direction for the platform! talking with customer is so so useful, the fastest way to grow 🚀

🎬 Introducing Animations in Orshot Studio By setting layer level animations, you can now generate interactive and more appealing ad banners, presentations, social media content (...and directly post to your social accounts too)

Dependable always beats the brilliant; if people can not count on you, nothing else matters. In any team or company, reliability is one of the most powerful ways to earn trust, respect, and influence. It does not mean overworking. It means people can trust your actions. If you notice, I did not say "you get things delivered" because that is not the only thing that matters. Here are some simple ways to signal reliability at your workplace - Do what you say you will do - Meet deadlines - Be punctual - Be available and helpful - Run toward problems - Communicate proactively - Follow through and document - Own mistakes quickly - Build a consistent track record Reliability does not always get celebrated, but people do notice it. Over time, reliability compounds into reputation, and reputation opens doors to new opportunities. If you want to build real trust at work, start by being reliable. This does not require doing one big thing but rather a lot of small things every day. The most impactful projects do not go to the loudest or the most brilliant; they go to the ones who can be trusted to deliver. Be the person others can count on.

@arpit_bhayani Congratulations Arpit 🎉

Joined Razorpay as Principal Engineer II :) From being a long-time customer to now building parts of the system - it's a full circle. Fintech is a new territory for me - time to get under the hood of how money actually moves. New domain, same guarantees - availability, correctness, performance - just with real money on the line.

@thelifeofrishi @orshotapp Congratulations on the milestone 🎉

At Orshot, we crossed 100+ customers this week while the team is vacationing in Italy 🇮🇹 Almost an year since I went full time on building Orshot, things are growing good! Thanks to everyone who's been supporting in the journey 😇

Today, Orshot has crossed 100+ customers in < an year of going live Excited to be re-launching on Producthunt, could use some help link 👇

We just added /btw to Claude Code! Use it to have side chain conversations while Claude is working.

Introducing 𝚑𝚒𝚝-𝚊𝚛𝚎𝚊—a collection of @tailwindcss utility classes for expanding the hit area of interactive elements. Small hit areas are a silent UX killer. One class fixes it. Distributed via @shadcn registry - see link below.

Who all are hiring in Pune, BLR or remotely for a Sr front end engineer? Is yes, then can you please DM me or drop a comment? I have a very good developer who is looking for the next move.

Engineers who learn AI + product thinking + domain knowledge will dominate the next decade. Just knowing how to code won’t be enough anymore.