Mitesh B Ashar

30.1K posts

Mitesh B Ashar

Mitesh B Ashar

@iMBA

NOT an MBA.

Kolkata, India Katılım Ağustos 2007
2.7K Takip Edilen2.8K Takipçiler
Mitesh B Ashar retweetledi
Santiago
Santiago@svpino·
The tokenmaxxing culture is absolutely out of hand. You don't need an agent for everything. In fact, I'm 99% sure you don't need an agent for 99% of the problems you need to solve. Good engineering principles still apply. Simplicity still wins. A regular, boring ol' script that works every time is 1000 times better than a fancy agent that works sometimes. We need common sense back.
English
87
35
423
25K
Mitesh B Ashar retweetledi
Ajey Gore
Ajey Gore@AjeyGore·
Wanna run hassle free agents - whether @openclaw or Hermes - use @getclawstation :-) Retweet please :)
English
5
35
50
17.7K
Mitesh B Ashar retweetledi
Matt Pocock
Matt Pocock@mattpocockuk·
1m context windows are a nice gimmick But you might be better off sticking to only the first 150K tokens:
English
78
63
1K
87.7K
Mitesh B Ashar
Mitesh B Ashar@iMBA·
@championswimmer I'm yet to send a single message to Sol. Maybe just a couple to Fable. I have been trying out Terra for this large spec right now, still in interview mode. I use Sonnet for most of planning and building, and Opus 4.8/GPT 5.4/5.5 for reviews.
Mitesh B Ashar tweet media
English
0
0
2
104
Arnav Gupta
Arnav Gupta@championswimmer·
I'll get more work done with a 2x-5x faster Opus/GPT 5.5; in fact even with GPT 5.4 than I will with Fable or 5.6 Sol getting "smarter" I think apart from scaling the training side compute and model size, the labs should start focusing on optimising inference faster too now.
English
11
2
107
6.8K
Mitesh B Ashar retweetledi
Mitesh B Ashar
I dont think the crucial issues lie in the SDK. It is about how fast Claude Code dogfooding is happening. There is enough AI slop getting "dumped" into the software - not just UI, but also UX, feature-sprawl, regressions and all other classical problems you can think of. It's an evil side effect of fast tokenmaxxing in AI SDLC, amplified when you dont want to be slowed down due to human reviews. To add to it x.com/iMBA/status/20… I feel we should definitely call it out - it is the bare minimum we can expect from Anthropic!
Mitesh B Ashar@iMBA

Couldn't agree more with this! I stopped filing issues after a certain point of time. Your own AI was supposed to be your leverage/vantage point. And you couldn't use it well enough to address growing user needs, rather letting them rot and auto close - ignored and abandoned!

English
0
0
0
20
Arnav Gupta
Arnav Gupta@championswimmer·
My Claude Code subscription is the most useless now because it cannot be used outside of their buggy harnesses. GLM, Kimi, OpenAI all allow usage on any harness. For most used cases I use Pi, because I have some of my custom extensions that do some specific things.
English
26
4
483
24.5K
Mitesh B Ashar
I have always been a fan of using and building integrated experiences that alleviate user experience. The first time I contributed to the Claude Code settings schema files on Schema Store, it was because I was facing a problem configuring a specific valid setting in the settings.json file as CC was validating against the outdated/inconsistent schema. I realised this was a great avenue to contribute to the UX of people configuring their Claude Code settings. I started making schema docs consistent in shape, adding verbatim descriptions and valid links to the schema, and writing an opt-in novel coverage tool for the larger repo to validate test case coverages for schemas hosted in the repo. I have now been doing this for close to 6 months now, and have perhaps touched more than 75% of the lines in that file. I hope that it actually positively contributes to the experiences of the users of the large community of Claude Code users. Recently, Anthropic was again expanding on their Claude for Open Source program: x.com/claudedevs/sta… @pranshusharma specifically pointed it out to me and while I was not exactly meeting formally enumerated requirements, I applied simply because their application form asked to "apply anyway"! I got accepted for it yesterday. Thank you @ClaudeDevs, @AnthropicAI, @domdomegg, @trq212!
Mitesh B Ashar tweet media
ClaudeDevs@ClaudeDevs

6 months of Claude Max 20x, on us. We're expanding Claude for Open Source to more of the community. If you're a maintainer, a core contributor, someone landing PRs across the ecosystem, or someone keeping a critical package alive, apply today!

English
1
0
3
91
Mitesh B Ashar
We will really have to step back enough to reimagine that. IMO, we would take away the hands we gave AI. It is basically detrimental to the idea of AI taking a decision to take an action. You are clearly not trying to take away actionability. We are talking about moving the action boundaries. Perhaps towards optimisation. I dont think the answer lies on either of the extremes. The answer lies somewhere in the middle IMO. Would we still have reached a place where we are able to execute AI to accomplish such large long-running tasks, irrespective of their nature?
English
0
0
0
10
Sumit Datta
Sumit Datta@sumitdatta·
What would agents look like if we did not go down the path of tool calling and optimized for it? We can read files deterministically, just from context. We have semantic and keyword search, we have tokenizers. LLMs are great with words - what if we gave them just that.
English
1
0
0
54
Mitesh B Ashar
This is also one reason I become very uncomfortable with the common AGENTS dot md file. Because different harnesses need different user instruction memories. I actually prefer dot md much better. And if you ask me, what I would propose or push for is standardizing the placement of these files in a folder, like `.agents/instructions/{AGENTS.md,.md,/{AGENTS.md,.md}`
English
1
0
1
27
Mitesh B Ashar
Different models have different strengths, weaknesses and generation patterns. A one-for-all agents memory file just does not cut it through IMO. I am so amused by the fact that none of the major coding harnesses have come up with an implementation of this simple idea where model-specific agent memory files can be maintained by humans, to augment to the generic one.
English
3
0
1
48
Mitesh B Ashar
Mitesh B Ashar@iMBA·
@_swanand Artifacts in Claude code has been introduced recently. And has landed like a bug + feature. The system instructions should really instruct models to ask whether I want to publish an artifact. It's not a sane default when I am working on code.
English
0
0
0
154
Swanand
Swanand@_swanand·
I asked Claude to fetch a few images from Unsplash based on the copy and positioning spine of a landing page I am updating. It worked for 20 minutes, created a Python script to generate a moodboard, then downloaded images, ran the script to generate an HTML moodboard, and published it as an artifact. I just wanted a folder with images and an explainer file. But I didn't tell this explicitly.
English
3
1
23
3.1K
Mitesh B Ashar retweetledi
Arnav Gupta
Arnav Gupta@championswimmer·
Every piece of software I use which used to be originally produced with a lot of care has gotten shitty. Just to make a list from top of my head... 1. Starting with this site. I used to give an example of how the Twitter mobile app was epitome of saving list scroll state across app lifecycle and even app death, all the way back in 2016 when teaching mobile development to my students. Today, most tweets > 2 day old if I open, the replies do not load, I don't get notifications for DMs, and random parts of it don't work at random times. 2. MacOS which was once more polished than Windows on the UI and as hackable as Linux from inside out - now randomly freezes, has kernel panics, needs disabling needless safety features all they way from safe mode to get basics working or toning down the horrible glass UIs. 3. Spotify used to be one of my favourite products, having great offline-first experiences, seamless sync across devices, handover of songs midway between phone, desktop, car, etc. Now the app can't even load offline downloaded playlists properly when internet is down, sync almost never works, UI glitches, watch app can't figure out how to play on headphone, or when to sync from phone to watch. 4. Whatsapp - one of the most performant apps, with solid delivery rates even with as slow as 2G/EDGE internet, now actually has dead-end UI flows (when sending photos, trying to edit it can lead to an unknown state), message deliveries often don't work even on solid internet, and media uploads frequently need retries. 5. Microsoft's entire office suite which used to be a workhorse product - something so reliable, that non-tech people would never touch Google Sheets with a 10-foot pole and threaten to resign if they didn't have a proper desktop app license of MS Office. Now they push you towards the cloud versions which work way worse than Google Workspace, and have add tons of React UI elements in the Desktop apps that makes then visibly slow and janky and large Excel sheets even crash sometimes. Most of these were on the trajectory of enshittification before wide-scale agentic coding or Claude-driven development was even all that common. The entire industry is in a phase where everyone is just building things because it is their job, and the era of care, and sincere craftsmanship of products has mostly come to an end.
English
70
112
1.1K
52.2K
Mitesh B Ashar retweetledi
Arnav Gupta
Arnav Gupta@championswimmer·
What a weird string of own goals at Google in the last few weeks/months. Addy Osmani also just left Google. Really really weird.
Justin Poehnelt@JPoehnelt

Two months ago I was fired by Google for creating the Google Workspace CLI. It went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days. It was an incredible, confusing journey, from directors and leaders asking what they could learn from the tool to getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories. I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace. Either way, the irony of my termination was the announcement at Google Cloud Next two days before I was fired that an official Workspace CLI was coming. I want this out there because it is easier for me to explain my story and it is an experience I want to fully own. It's also part of my healing. Nearly 7 years at Google was an incredible opportunity for me and I was fortunate to have wonderful teammates and a manager that fully supported me through these last few months. Thank you.

English
2
6
179
40.5K
Mitesh B Ashar retweetledi
Nikhil Pahwa
Nikhil Pahwa@nixxin·
Six things WhatsApp Plus should have instead I have little need for the six features that WhatsApp offers as a part of WhatsApp Plus. I don’t need a custom app icon, stickers, a different theme for the app, ringtones (my Whatsapp is on mute and notifications are off except for my wife), or pinning extra chats: three pinned chats are enough. What I will gladly pay for: 1. Verified profile, so as to prevent people from impersonating me. It has happened. Happens to a lot of founder friends of mine. 2. Block WhatsApp for Business messages (mostly spam), except for businesses that I approve, instead of businesses that claim to have my approval, alongwith the ability to pause messages from businesses once my transaction is over. Transfer control to the user from the business. 3. Identify who has me on which broadcast list, and give me the ability to exit that list permanently. 4. Allow only your contacts to message you on WhatsApp 5. Autoresponders: for business, for when you’re busy, for when you’re traveling, especially for when you want to redirect people to someone else. I’d like to redirect messages from PR agencies to a black hole, but that’s just me. 6. Persistent web login and agent enablement: allow people and their agents to be persistently be logged in without having to change their number to WhatsApp for Business, or login every 14 days for their agents to retain access to it, and make WhatsApp more programmable with webhooks. Ok, I know the last one is something that a handful of people like me would want, but my point is that what WhatsApp thinks people want, based on its offerings, is bling not utility. That’s a social media mindset. WhatsApp is not Instagram, it’s a messaging app. What people actually want is lower noise, higher signal. YouTube got this right with YouTube Premium.
Nikhil Pahwa tweet media
English
7
12
53
9.6K