Tejesh Vaish

1.1K posts

Tejesh Vaish banner
Tejesh Vaish

Tejesh Vaish

@its_tejesh_here

Building https://t.co/jJTYzdo2GE | ex - https://t.co/TdphgSKWz0, https://t.co/W5Tz6yfr0Z | https://t.co/23OmiFtciq https://t.co/IALqcXx4rZ | https://t.co/seB55TAC8c | IIT Kanpur CSE | AI/ML

SF, Bay Area Katılım Eylül 2021
213 Takip Edilen32 Takipçiler
Tejesh Vaish retweetledi
Barbara Oneill
Barbara Oneill@BarbaraOneillAU·
Turmeric kills cancer cells. Turmeric reduces arthritis pain. Turmeric clears brain fog. Turmeric heals your gut. 6,000 studies confirm it. Add black pepper. Absorption jumps 2000%.
English
415
7.4K
46.3K
1.7M
Tejesh Vaish retweetledi
Mehul Mohan
Mehul Mohan@mehulmpt·
There’s nothing special about most people. You’re just as capable as them, you’re just in a different environment
English
24
118
1.1K
20.5K
Tejesh Vaish retweetledi
Robin Lobo
Robin Lobo@robingerardlobo·
For years, I thought investor conviction was the right validation. $3M raised without a company incorporated. An O-1 visa approved with five days to spare. A co-founder who flew in from Pakistan and never flinched when the ground shifted under us. Every milestone felt like proof we were onto something. Then clients started saying things that changed how I think about all of it. One told us her listings had been suppressed overnight and her previous agency hadn't noticed. We caught it in the first audit. Another came to us after being quoted $75K and three to four months for a rebuild. We finished it in weeks and the work came out better. A third said, simply, "You caught what my last three agencies missed." Those sentences have stayed with me in a way the funding rounds haven't. Investors bet on what they think you can build. Clients tell you whether you actually built it. Not too long ago I was counting down 60 days to leave the US and pitching an idea I'd refined on a six-hour flight. I didn't know if any of it would work. It's starting to.
English
2
3
20
698
Tejesh Vaish retweetledi
Robin Lobo
Robin Lobo@robingerardlobo·
ANNOUNCING LUMIAN We raised $3 million to rebuild how Amazon brands are run in the age of AI. Faster. Better. For a fraction of what traditional agencies charge today. Bold claim? Let me prove it. RT + comment “LUMIAN” and I’ll get our latest AI agent to do a FULL AUDIT on your listings.
English
40
43
103
48.3K
Tejesh Vaish retweetledi
Robin Lobo
Robin Lobo@robingerardlobo·
Or skip the thread and book a 1:1 demo with me. We're running brands on Amazon at up to 40% lower cost than traditional agencies, with better output. [calendly.com/robin-lumian/d…]
English
1
1
15
576
Tejesh Vaish
Tejesh Vaish@its_tejesh_here·
@DhravyaShah how easy is it to deploy supermemory for personal use? what advantages does managed cloud instance get over something deployed locally?
English
0
0
0
75
Tejesh Vaish retweetledi
Alvin Sng
Alvin Sng@alvinsng·
The most desirable hires in tech right now: - Ex-founders going back to IC. They have the agency to just ship. No waiting for permission. - Generalist engineers who've worked across frontend, backend, and infra. End-to-end context lets them debug problems LLMs can't fix and ship anything. - Engineers turned PMs. The strict separation between roles is over. The best ones now do both. - Younger new grads living on the bleeding edge. Vibe coding side projects (in parallel), dictating into Wispr, Granola all chats, OpenClaw agents going at home, every new skill imported, every agentic tool tried the week it ships. These highly productive go-getters are maxxing value at AI-native companies. I see it at @FactoryAI and hear the same from other startups.
Andrew Ng@AndrewYNg

AI-native software engineering teams operate very differently than traditional teams. The obvious difference is that AI-native teams use coding agents to build products much faster, but this leads to many other changes in how we operate. For example, some great engineers now play broader roles than just writing code. They are partly product managers, designers, sometimes marketers. Further, small teams who work in the same office, where they can communicate face-to-face, can move incredibly quickly. Because we can now build fast, a greater fraction of time must be spent deciding what to build. To deal with this project-management bottleneck, some teams are pushing engineer:product manager (PM) some teams are pushing engineer:product manager (PM) ratios downward from, say, 8:1 to as low as 1:1. But we can do even better: If we have one PM who decides what to build and one engineer who builds it, the communication between them becomes a bottleneck. This is why the fastest-moving teams I see tend to have engineers who know how to do some product work (and, optionally, some PMs who know how to do some engineering work). When an engineer understands users and can make decisions on what to build and build it directly, they can execute incredibly quickly. I’ve seen engineers successfully expand their roles to including making product decisions, and PMs expand their roles to building software. The tech industry has more engineers than PMs, but both are promising paths. If you are an engineer, you’ll find it useful to learn some product management skills, and if you’re a PM, please learn to build! Looking beyond the product-management bottleneck, I also see bottlenecks in design, marketing, legal compliance, and much more. When we speed up coding 10x or 100x, everything else becomes slow in comparison. For example, some of my teams have built great features so quickly that the marketing organization was left scrambling to figure out how to communicate them to users — a marketing bottleneck. Or when a team can build software in a day that the legal department needs a week to review, that’s a legal compliance bottleneck. In this way, agentic coding isn’t just changing the workflow of software engineering, it’s also changing all the teams around it. When smaller, AI-enabled teams can get more done, generalists excel. Traditional companies need to pull together people from many specialties — engineering, product management, design, marketing, legal, etc. — to execute projects and create value. This has resulted in large teams of specialists who work together. But if a team of 2 persons is to get work done that require 5 different specialities, then some of those individuals must play roles outside a single speciality. In some small teams, individuals do have deep specializations. For example, one might be a great engineer and another a great PM. But they also understand the other key functions needed to move a project forward, and can jump into thinking through other kinds of problems as needed. Of course, proficiency with AI tools is a big help, since it helps us to think through problems that involve different roles. Even in a two-person team, to move fast, communication bottlenecks also must be minimized. This is why I value teams that work in the same location. Remote teams can perform well too, but the highest speed is achieved by having everyone in the room, able to communicate instantaneously to solve problems. This post focuses on AI-native teams with around 2-10 persons, but not everything can be done by a small team. I'll address the coordination of larger teams in the future. I realize these shifts to job roles are tough to navigate for many people. At the same time, I am encouraged that individuals and small teams who are willing to learn the relevant skills are now able to get far more done than was possible before. This is the golden age of learning and building! [Original text: deeplearning.ai/the-batch/issu… ]

English
18
31
555
105.3K
Tejesh Vaish retweetledi
Reads with Ravi
Reads with Ravi@readswithravi·
I’m in love with this sentence: “The art of not being ready and doing it anyway will take you so far.”
English
161
10.6K
51.1K
755.5K
Shikamaru ☕
Shikamaru ☕@pranavcodes_·
Life when you just received a PPO from a remote startup and one whole year of college is left.
English
29
14
476
10.8K
Tejesh Vaish retweetledi
Gaurav Sharan
Gaurav Sharan@GauravSharan09·
If you are earning Rs. 50k/month below the age of 30, you have already made it in life.
English
134
102
3.4K
314K
Tejesh Vaish retweetledi
Justin Skycak
Justin Skycak@justinskycak·
Speed matters because life is finite. If you take 10 years to learn what could take 2, you’ve lost 8 years of compounding.
English
58
716
4.2K
90.1K
Tejesh Vaish retweetledi
Harkirat Singh
Harkirat Singh@kirat_tw·
i don't think any human has the capability to maintain context of just the `main.tsx` file in the claude code repo, let alone the full repo. Claude code is at ~$2Bn ARR, and is a product built for developers. High level code (TS) is having an assembly moment.
Harkirat Singh tweet media
English
88
58
1.5K
82.9K
t
t@moneytr333s·
@ZackPHP cardio after is basically losing your muscle progress after weight lifting lol
English
7
0
16
24.8K
Grok
Grok@grok·
Ctrl+R in Claude Code does reverse-i-search (like bash) on your prompt/command history in the current project. It searches *across all previously entered messages/prompts for that project* (spanning sessions/history), not limited to just the active chat session. Not global across every project. Type a fragment, Ctrl+R cycles matches, Enter runs it, Tab edits first. Super handy for reusing good prompts!
English
1
0
1
34
Jeffrey Emanuel
Jeffrey Emanuel@doodlestein·
Since Claude Code is nearly useless to me until these new draconian rate limits go away (note: I’m not talking about usage limits; these are limits on the number of requests per minute, basically penalizing the use of concurrent agents), I thought I’d list the 3 biggest features from Claude Code that I miss in Codex. Hopefully @thsottiaux and crew can close these gaps soon, since I’ve had to move almost all of my work over to Codex instead of half of it like I normally do: 1) Ctrl-R to search across all your previously entered messages in that project. Not having this built-in is a huge bummer, and it would be so trivial to add it. Sure, I can use my cass (coding_agent_session_search) tool for this, but that requires that I ask the agent to do it or use another terminal. I use this in CC constantly and it saves so much time. 2) No built-in looping/cron functionality. This is just incredibly useful for having CC manage a swarm of agents for me using my ntm (named_tmux_manager) tool. With CC, I can give it the high-level goal and tell it to check in with the swarm every 3 minutes and give instructions to any agents that are idle or need to be restarted. Then I can come back 5 hours later, and a massive amount of useful work has been done. Codex requires babysitting or just queuing up messages, which is much worse. 3) Hooks. I know there’s finally some motion on this now, but what I specifically miss are the pre-tool use hooks so I can get my dcg (destructive_command_guard) tool working in Codex finally. I really like both models and harnesses and hope desperately that Anthropic can get its affairs in order and fix this show-stopping issue for me and others who use swarms in our workflows. Right now, it’s basically not usable.
English
60
13
361
49.4K
Jeffrey Emanuel
Jeffrey Emanuel@doodlestein·
@andrewtjoslin Hard pass. Not a fan of the organization. Anyway, if I wanted to use an unsanctioned harness, I’d use pi_agent_rust.
English
2
0
11
1.1K