Parikshit Upadhyaya

106 posts

Parikshit Upadhyaya

Parikshit Upadhyaya

@parikupa

Applied maths, computer science, music, cricket

Stockholm Katılım Ekim 2014
36 Takip Edilen7 Takipçiler
Julien Chaumond
Julien Chaumond@julien_c·
Who else feels like they lose ~20 IQ when it’s hot outside?
English
58
10
358
51K
One Happy Fellow
One Happy Fellow@onehappyfellow·
do java programmers suffer from premature encapsulation? 🤔
English
10
3
32
1.6K
Beff (e/acc)
Beff (e/acc)@beffjezos·
@elonmusk @iScienceLuvr Finishing PhD is an anti-signal in many cases. If you didn't learn to go to drop out go to industry and build real things, then you are probably too theory-pilled
English
85
16
440
293.4K
Pranav Mailarpawar
Pranav Mailarpawar@pranvtwt·
I know a lot of people who doesn't know how to push code to the repository but they are SDE-2 :)
English
43
11
667
44.1K
Parikshit Upadhyaya
Parikshit Upadhyaya@parikupa·
@ChShersh Solving actually difficult problems requires something beyond intelligence. Something akin to "chutzpah"
English
0
0
0
74
Dmitrii Kovanikov
Dmitrii Kovanikov@ChShersh·
Smart enough to feel that most people are dumb. Not smart enough to solve actually difficult problems.
English
31
27
563
14.5K
Parikshit Upadhyaya
Parikshit Upadhyaya@parikupa·
@naval On a tangent here but people in India will often use the word "duty" for work. Sharp contrast to the west, where you are expected to be passionate about work. How do you find love for what you do if you are not passionate? One way is to refer to it as "duty"
English
0
0
0
30
Naval
Naval@naval·
A man expresses love through duty.
English
722
3.2K
23.2K
2M
Jonathan Blow
Jonathan Blow@Jonathan_Blow·
I've been trying to use ChatGPT as a thesaurus but it doesn't seem to be very good ... it keeps making generic suggestions even when prompted like "imagine you are very learned, with a huge vocabulary"... it then just picks older generic words. Any hints? English has 600k words!
English
134
2
504
59.9K
Parikshit Upadhyaya
Parikshit Upadhyaya@parikupa·
@system_monarch Some winners (OAI + Ant) with very good winter jackets on have emerged this time around that were missing at the end of the previous winters. But there are a lot of people without jackets
English
1
0
2
54
Puneet Patwari
Puneet Patwari@system_monarch·
AI winter happened 2 times in history between 1974-1980 and early 1990s. Does anyone think the current euphoria can lead to another AI winter? Have we breached the barrier this time? 🤔
English
9
1
13
2.3K
ThePrimeagen
ThePrimeagen@ThePrimeagen·
Honestly why stop at 100x engineer? Just use more agents, you literally could be 1000x, 10000x, 100000x just by scaling You could what you use to in an entire year in one second
English
295
158
4.7K
181K
bourbaki
bourbaki@2oovy·
I don’t understand why some ppl will play chess but not any other board game
English
14
3
28
2.1K
berni
berni@itsnotbernhard·
Great feeling: you pass on a candidate who doesn't clear your technical bar. Two weeks later they've joined your competitor. Your bar is your moat
English
18
0
232
36.9K
Jesse
Jesse@Dev_JesseMaduka·
Some people use Git daily and still don’t fully understand it 😭
English
82
9
281
19K
Parikshit Upadhyaya
Parikshit Upadhyaya@parikupa·
@DJ_CURFEW ClickUp is quite slow in general for an app that is just use to push tickets. Consider rewriting the backend in rust instead of node?
English
0
0
0
36
Zeb Evans
Zeb Evans@DJ_CURFEW·
Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why. First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it. Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands. Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition. I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively. THE 100X ORGANIZATION The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago. Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken. The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems. These roles will evolve. But waiting for that to happen naturally means falling behind now. The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working. THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS — THE BUILDERS: 10X ENGINEERS I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality. Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment. AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down. Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed. So who do you want orchestrating and reviewing code? And how do you want your best engineers to spend their time? If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code. The new world is about enabling your 10x engineers to become 100x. The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated. I call this the great reckoning of AI coding, and every company will face this soon if not already. More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well. — THE BUILDERS: 10X PRODUCT MANAGERS Product management and design roles are merging. Designers that have customer focus, become more like product managers. And product managers that have intuition for UX become more like designers. The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results. The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy. Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on. To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production. Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck. That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time. — THE SYSTEM MANAGERS Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp. The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world. You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is. — THE FRONT-LINERS In a world that will become saturated with AI communication, the human touch will matter more than anything to customers. This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings. One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers. REWARDING 100X IMPACT In a world where companies are able to do so much more with less, where does that excess money go? In our case, much of the savings in this new operating model will flow directly back to those that enabled it. We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them. You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace. Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems. THE FUTURE Nearly every company will make changes like these. The ones that do it proactively will define what comes next. The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago. ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.
English
1.6K
3.7K
7.7K
9.1M
vik
vik@vikhyatk·
if you understand your full codebase, you're not moving fast enough
English
25
8
285
12.4K
Nick
Nick@nickcammarata·
meditation will nuke your short term memory and you'll end up doing basic things twice in a row because you forgot you just did it, but you'll be so baseline happy doing anything that you won't mind doing things twice
English
57
10
837
281.1K
Parikshit Upadhyaya
Parikshit Upadhyaya@parikupa·
@charles_irl @modal If there are only 10-12 instance types, once could just iterate across all the corners of the feasible region polytope and find the actual optimal solution without approximation?
English
0
0
0
32
Charles 🎉 Frye
Charles 🎉 Frye@charles_irl·
Added a smol new section to last week's blog post on the technical internals of @modal's fast cold boots. This section describes how we frame cloud buffer management as a linear optimization problem and solve it with GLOP. modal.com/blog/truly-ser…
Charles 🎉 Frye tweet mediaCharles 🎉 Frye tweet media
English
5
5
70
4.2K
Gary Marcus, MIT PhD and NYU Professor Emeritus
seriou question: how do you handle an intellectual doppelganger who has systematically started adopting every position you have argued for for 30 years while presenting each idea as if it were his own? nothing in graduate school prepared me for this.
English
80
4
211
29.6K