gertsio ❗
1.1K posts
gertsio ❗
@gertsio
Financial Advisor turned → engineer | posting my road to FAANG 🌪️
NYC Katılım Ocak 2025
506 Takip Edilen155 Takipçiler
What you say is true, but nonetheless our AI will be great. Whether it is the best remains to be seen, but I will never give up. Never.
Space(XAI) is only 3 years old. That’s half the age of Anthropic and quarter the age of OpenAI.
Let’s see where things stand 3 years from now.
English
Elon doesn't need to run the best AI model. He needs to control the best hardware. Nvidia is the most valuable company on Earth and their models aren't the most popular. The hyperscaler play works.
English
@cursor_ai so you really were cooking this whole time
really really impressive model, guys 👏
gertsio ❗@gertsio
Cursor can’t really compete with Claude Code without having its own AI model. Claude Code gives you roughly 40 hours of work per week, while Cursor caps out at around 10. The only reasons Cursor is still in the game are vibe coders who aren’t comfortable with the terminal (yet) or folks who simply don’t know Claude Code exists.
English
@GertsDev is the higher bandwidth the main selling point for you or have you seen something else you prefer there?
English
Cursor can’t really compete with Claude Code without having its own AI model.
Claude Code gives you roughly 40 hours of work per week, while Cursor caps out at around 10. The only reasons Cursor is still in the game are vibe coders who aren’t comfortable with the terminal (yet) or folks who simply don’t know Claude Code exists.
English
@aakashgupta PM is a weird layer in 2026. AI generated sprints and plans better than 10 PMs together
English
Everyone keeps asking if AI is going to kill the PM role.
My guest this week runs an AI-native company, and the answer was the opposite of the hype. They're hiring more PMs than ever. More engineers than ever.
But the bar moved.
Code is cheap to produce now. So the PMs who stand out aren't the ones who write the cleanest spec. They're the ones with a real opinion about what to build. Product taste is the alpha.
So I asked the obvious follow-up. Where does product taste actually come from?
The answer was more concrete than I expected.
Taste is an output. It comes from consuming an enormous volume of feedback from every direction at once.
The best PMs already do this manually. YC has been telling every cohort the same two words for years: talk to users. But "talk to users" in 2026 means something bigger than customer calls.
It means building a context graph. One connected feedback layer that pulls from:
- Wherever your team logs issues
- GitHub discussions
- Slack and Discord conversations with your community
- Gong transcripts from every customer call
- Product analytics from PostHog, Amplitude, Pendo, and FullStory
- Twitter, if your users post about you there
Every one of those is a feedback stream. Most teams let them sit in separate tools, read by separate people, never connected.
Here's the part that reframes the whole thing.
Once that feedback lives in one graph, a human doesn't have to be the one reading it. Your agent can consume it.
That changes what a PM's day looks like. Instead of manually synthesizing scattered signal, an agent reads the full context graph and surfaces the patterns. You spend your time on judgment, not collection.
This is why I don't buy the "death of the PM" narrative.
The PMs who lose are the ones who thought the job was writing requirements. The PMs who win are the ones building the feedback machine that taste is actually made of.
Taste used to feel innate. It's becoming a system you can engineer.
Aakash Gupta@aakashgupta
She literally broke down how to run evals in Claude Code (built the whole thing live): 01:34 - What people get wrong with evals 04:35 - Why product taste is the alpha now 09:28 - Building a PM agent from one prompt 19:00 - Instrumentation without writing code 22:00 - Watching traces stream in live 28:00 - Getting Claude to write your first eval 33:58 - When vibe evals work and when they don't 48:50 - The self-improving loop (this part is wild) 01:03:00 - Same-day shipping is real 01:06:00 - The context graph unlock
English
@systemdesignone The only one metric that matters is how much money your code generates for you / your company. Whether you understand every line or remember the entire codebase means nothing
English
A pattern I've noticed in people using AI to code:
They're always shipping... They never stop generating... They've got Claude to code, CodeRabbit to review, and a prompt library larger than the codebase... But if you ask them what they understand about the code they merged last week, their minds go blank...
Productivity isn't the same as mastery.
Focus on the fundamentals.
(This is not just an opinion, but a fact.)
Lee Robinson@leerob
You might believe you should spend less time thinking about code because of AI. I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability. At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time. Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change. I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance. I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.
English
@AIandDesign What you fail to understand is the fraud, scams, and illegal labor practices that go on daily for tech workers. This will be the fourth time with four different companies where I have been laid off so a company can outsource or bring people from India.
English
Reply with your top #3 absolutely cracked devs who cannot land a job because of Indian H1-B workers.
English
@KaiXCreator You don’t need to cancel anything. Claude code is ok for architecture, he’s really nice to talk to / explore. Gpt 5.5 awesome in every other aspect. Use it together
English
@khushiirl If you had to write binary code. Wouldn’t you still know how it build it or debug it?
English
@avrldotdev It's gonna be awesome. I’m in charge of systems so they work. Nobody cares how or what part of code AI generated. And what ideas belong to who
English
@KaiXCreator Maintenance (i.e., not rewriting the entire stack every six months).
English
@alexis_acosta__ @mSykeCodes Makes sense to spend few months on deep refactoring and turn at least often maintainable code into something agent would understand.
Stop riding horses just because it's how it's always been
English
This is mostly how I'm operating at work as well. AI is great when you're starting a project from scratch. There's no tech debt and you can make the architecture exactly how you want it.
But at work, with a legacy codebase that has been around for 10+ years, you can't just let agents loose. There's too many abstractions that make no sense. Too much context that isn't documented anywhere and only lives in the minds of the senior engineers who've been working on the system for years.
This seems like maybe it's a solvable problem, though. There's probably room in the market place for an agency or consultancy that can go into large enterprises and lead the effort to make the codebase more AI friendly. This would probably include a large effort to document things but most importantly, finally address the tech debt that has been built over the years. The details of how to do this though aren't clear to me. How do you take a decades old codebase and make it AI agent compatible? That's the (probably billion dollar?) question.
English
I'm still writing 95% of all my production code by hand. I let it write tests, fix bugs, answer questions, analyze data, build prototypes, but I do not at work let the thing just rip on an architecture I know will have to be maintained into the future.
@levelsio@levelsio
I don't write code anymore I haven't written code in I think 6 months? I think everyone is like this no?
English
@mSykeCodes It's like saying I’m junior dev and our seniors dev write only boring stuff and I do architectural decisions.
Not a lot of devs write code / architect better than lets say gpt 5.5 in good hands
English