Manideep Polireddi

11.1K posts

Manideep Polireddi banner
Manideep Polireddi

Manideep Polireddi

@okmanideep

💼 Engineer at JioHotstar. Previously at Praja, Disney+ Hotstar, Headout. Follow for not so funny takes on Android, Flutter, the open web... Neovim btw.

Bengaluru, India Beigetreten Eylül 2010
699 Folgt1.2K Follower
Manideep Polireddi retweetet
Aaron Levie
Aaron Levie@levie·
CEOs are uniquely prone to AI psychosis because they’re sufficiently distant from the last mile of work that still has to happen to generate most value with AI. So when they play with AI, they see the happy path results, often not considering the next 10 or 20 things that have to happen to get sustainable results from agents. “Look I made this awesome product prototype”. Yes but you didn’t have to review the code before it went into production and fix a bunch of issues. “Look I generated a contract”. Yes but you didn’t verify all the terms before it goes out to the counterparty and didn’t have to wire up all the past contracts to work with. The best thing you can do as a CEO is to use AI a *ton* to figure out the real implications of agents in the enterprise, and come out the other side with an appreciation for both the upside and the real work that goes into them.
Michal Malewicz@michalmalewicz

CEOs are the most delusional about AI. Detached from reality.

English
309
784
7.2K
1.2M
Manideep Polireddi
Manideep Polireddi@okmanideep·
@ponnappa You can probably switch it up without much of a compromise. Nothing 4a pro as the main device and Pixel 10a/your current pixel as the backup.
English
0
0
1
197
Sidu Ponnappa
Sidu Ponnappa@ponnappa·
@okmanideep I care a lot, and despite that I enjoy the rest of the experience enough that I'm thinking of compromising
English
1
0
0
295
Sidu Ponnappa
Sidu Ponnappa@ponnappa·
i bought a nothing 3a as a backup device nearly a year ago and i've grown to enjoy it so much i'm thinking of buying the 4a pro and switching away from Google phones after more than a decade. should i?
English
11
1
64
13.8K
Manideep Polireddi
Manideep Polireddi@okmanideep·
Bleaching is a nice way to describe what is happening these days with HDR
Sudendra@sudhukl

@okmanideep Are they de-promoting their own AI? Or bleaching photos is a thing now?

English
0
0
0
35
Arnav Gupta
Arnav Gupta@championswimmer·
@ponnappa Google phones are the worst of both worlds. For actual flagship performance and an actual iPhone-rivalling ecosystem - you go to Samsung. For barebones, no-frills phones as a secondary device, Nothing is great.
English
8
0
29
3.4K
Manideep Polireddi retweetet
Srinivas Alavilli
Srinivas Alavilli@srinualavilli·
From vision to action! @Bioconlimited is leading the way with India’s first HR-backed #CorporateCommuteNudge program. Inspired by @kiranshaw’s leadership, we’re making bus and metro commutes the gold standard for corporate India. These efforts started at @ELCIA_IN in partnership with @OfficialBMRCL @BMTC_BENGALURU @GBAChiefComm more than a year ago! @0RRCA @ELCITA_IN @WEPPIA_EPIP @qualcomm_in @AlstomIndia @WRIIndia @prashanthp @SCSC_Cyberabad @nasscom @SVP_India @ASSOCHAM4India @AMAMEDICALASSO @RameshPV2010 #HYSEA @jayesh_ranjan @GummallaSrijana
Kiran Mazumdar-Shaw@kiranshaw

Biocon wants its employees to take the bus & metro in Bengaluru. Here is how deccanherald.com/india/karnatak… via @deccanherald

English
1
2
12
981
Manideep Polireddi retweetet
Armin Ronacher ⇌
Armin Ronacher ⇌@mitsuhiko·
A selection of great PRs that were submitted to Pi — a thread.
English
36
15
411
56.4K
Armin Ronacher ⇌
Armin Ronacher ⇌@mitsuhiko·
Why does everybody want managers to be ICs? Please someone explain this to me from first principles.
Brian Armstrong@brian_armstrong

This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian

English
271
23
1.5K
444K
Dmitriy Kovalenko
Dmitriy Kovalenko@neogoose_btw·
Everyone migrate to nushell. Go in debt if you have to.
English
17
1
89
12.8K
Manideep Polireddi retweetet
Mitchell Hashimoto
Mitchell Hashimoto@mitchellh·
Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. mitchellh.com/writing/ghostt…
English
551
1.6K
16.7K
2.9M
Manideep Polireddi retweetet
Vic 🌮
Vic 🌮@VicVijayakumar·
I'm now able to tell my agent “we are going to work on JIRA-1234” and it goes and pulls down the task, makes me a plan, I say yeah okay that looks good, and it generates the commit. I run an AI review from a different session, it finds 4 issues of varying priorities, I paste it to my original agent and say validate these findings and fix them if necessary, it creates a fix, I run another review, no more high priority issues found. I open up the code in an IDE to go over it before pushing it up for human review. Looks fine I guess, nothing crazy. I try to understand everything before I push it up for review because if this breaks, it's still my name on it. I say why did you make this one change, it gives me a reasonable explanation for why. It says something codebaity like "if you want I can suggest 2 more ways you could really tighten up this work to prevent some rare but possible regressions". I'm smart enough to not fall for it. Code pushed up, task moved to in-review. I didn't write any of it, this is not my accomplishment. Users won't care who wrote it if it works. A lot done in 20 mins but it felt soulless.
English
82
56
1.5K
196.9K
Manideep Polireddi
Manideep Polireddi@okmanideep·
@dharmesh > there's elegance and value in having the backend and the frontend in the same language. Even with LLMs?
English
0
0
0
216
dharmesh
dharmesh@dharmesh·
I'm going to say something shocking and borderline heretical (for me). I'm thinking about switching from Python to TypeScript for my next project. I've been using Python for *decades* as my primary programming language. There are so many things I love about the language: 1) Python is a joy to develop in. 2) Great libraries for everything I need to do. 3) It seems to be lingua franca of AI. It's what LLMs use when they need to generate code to solve a problem. It's usually the first language to get an SDK/library from the frontier model companies (and others in the space). It's what many AI-oriented open source projects are built-in. So, why am I considering TypeScript? A few reasons: 1) There's elegance and value in having both my front-end code and back-end code in the same language. 2) TypeScript is natively type-safe. 3) When distributing applications to others (particularly CLI tools), it's much more common/simple to do with a Node app then try to build binaries in Python (using something like pyinstall). 4) TypeScript is a close second when it comes to being popular in the AI community. 5) There are packages for most of the common things I need (web framework, database access, web/http calls, etc.). 6) There is first-class support from Vercel for deploying TypeScript apps. I'm both an investor in Vercel and a customer but have mostly used it for front-end deploys, not backend. And, what once was the biggest reason NOT to use TypeScript is no longer true: The fact that I don't know TypeScript and didn't want to spend hundreds of hours becoming an expert at it. Now with agentic coding, I don't need deep knowledge of the language in order to be productive. With my knowledge of Python, C++ and other prior languages, I can likely get by pretty well in TypeScript with the help of Codex and Claude Code. Haven't made the decision to switch over completely yet, but next time I have a small, contained project I need to work on, I'm considering trying TypeScript. What do you think? Am I overthinking it or underthinking it?
English
100
12
283
46.6K
Manideep Polireddi retweetet
takahirom
takahirom@new_runnable·
Androidの開発のskillsがGitHubでリリースされたみたい XML -> Jetpack Compose移行やAGP9移行、Nav3、R8、Billingライブラリのアプデ、Edge to edge対応など、一時的だけどちょっと痛みがありそうなタスクのskillが揃っている github.com/android/skills
日本語
1
65
315
20.7K
Manideep Polireddi retweetet
TheStandupPod
TheStandupPod@thestanduppod·
You're Delusional
English
34
65
1.1K
137.6K
Manideep Polireddi retweetet
dax
dax@thdxr·
there's so much bro-economics going on right now "if the company doesn't use ai then they'll be less productive than their competitors and so they'll die" yeah imma go crush exxon mobil with the clanker crew and my 3 second attention span
English
57
58
1.5K
47K