I Teach You AI Engineering & System Design • 0.5M+ Audience

Join 250K+ Subscribers →
Pinned Tweet
We are in the middle of the agentic coding era, please take advantage of it. Coding agents are changing what it means to be a software engineer. Typing code on a screen used to be a big part of the job. But now AI agents can handle more of that work. The pattern of technological change is familiar: Mechanical part of work gets automated & human role moves up a layer. For software engineers, I think it means 3 things: 1 You need to know what good looks like. An agent can create a feature, fix a bug, and/or refactor code. But if you don’t know what good implementation looks like, you cannot tell whether the work should ship. The faster agents write code, the more your judgment matters. === 2 You need to learn how to manage multiple agents. One developer can already give different tasks to different coding agents. That changes the job. You become responsible for: - giving context to agents, - directing their work, - checking results. === 3 You need a way to control this across the company. Imagine all engineers in your company working this way... You need to know: - which “agents” people use, - what they’re doing, - what they cost, - what happens when something goes wrong. === This is why I’m genuinely excited about JetBrains Air. It gives you an environment for directing multiple coding agents & reviewing their work. So you can delegate more coding work without losing visibility/control. Plus... >JetBrains Air Teams lets you coordinate software delivery workflows across engineers & agents. So engineering teams can manage agentic work across the development process. >JetBrains Air Governance gives organizations policies, visibility, auditability & cost management. So they can control how agents get used & maintain accountability for what ships. And this works in a world where engineers use different agents & models. i.e., you don't have to bet everything on one provider. === The bottom line: Software engineers won’t become less important because agents can write more code. Their role moves up a layer. You delegate the work. You still own the result.
Paid partnership (ad)
10
1
13
1,574
SOFTWARE ENGINEERS ONLY What's one trick to get good at vibe coding?
1
1
638
Neo Kim retweeted
We are in the middle of the agentic coding era, please take advantage of it. Coding agents are changing what it means to be a software engineer. Typing code on a screen used to be a big part of the job. But now AI agents can handle more of that work. The pattern of technological change is familiar: Mechanical part of work gets automated & human role moves up a layer. For software engineers, I think it means 3 things: 1 You need to know what good looks like. An agent can create a feature, fix a bug, and/or refactor code. But if you don’t know what good implementation looks like, you cannot tell whether the work should ship. The faster agents write code, the more your judgment matters. === 2 You need to learn how to manage multiple agents. One developer can already give different tasks to different coding agents. That changes the job. You become responsible for: - giving context to agents, - directing their work, - checking results. === 3 You need a way to control this across the company. Imagine all engineers in your company working this way... You need to know: - which “agents” people use, - what they’re doing, - what they cost, - what happens when something goes wrong. === This is why I’m genuinely excited about JetBrains Air. It gives you an environment for directing multiple coding agents & reviewing their work. So you can delegate more coding work without losing visibility/control. Plus... >JetBrains Air Teams lets you coordinate software delivery workflows across engineers & agents. So engineering teams can manage agentic work across the development process. >JetBrains Air Governance gives organizations policies, visibility, auditability & cost management. So they can control how agents get used & maintain accountability for what ships. And this works in a world where engineers use different agents & models. i.e., you don't have to bet everything on one provider. === The bottom line: Software engineers won’t become less important because agents can write more code. Their role moves up a layer. You delegate the work. You still own the result.
Paid partnership (ad)
10
1
13
1,574
We are in the middle of the agentic coding era, please take advantage of it. Coding agents are changing what it means to be a software engineer. Typing code on a screen used to be a big part of the job. But now AI agents can handle more of that work. The pattern of technological change is familiar: Mechanical part of work gets automated & human role moves up a layer. For software engineers, I think it means 3 things: 1 You need to know what good looks like. An agent can create a feature, fix a bug, and/or refactor code. But if you don’t know what good implementation looks like, you cannot tell whether the work should ship. The faster agents write code, the more your judgment matters. === 2 You need to learn how to manage multiple agents. One developer can already give different tasks to different coding agents. That changes the job. You become responsible for: - giving context to agents, - directing their work, - checking results. === 3 You need a way to control this across the company. Imagine all engineers in your company working this way... You need to know: - which “agents” people use, - what they’re doing, - what they cost, - what happens when something goes wrong. === This is why I’m genuinely excited about JetBrains Air. It gives you an environment for directing multiple coding agents & reviewing their work. So you can delegate more coding work without losing visibility/control. Plus... >JetBrains Air Teams lets you coordinate software delivery workflows across engineers & agents. So engineering teams can manage agentic work across the development process. >JetBrains Air Governance gives organizations policies, visibility, auditability & cost management. So they can control how agents get used & maintain accountability for what ships. And this works in a world where engineers use different agents & models. i.e., you don't have to bet everything on one provider. === The bottom line: Software engineers won’t become less important because agents can write more code. Their role moves up a layer. You delegate the work. You still own the result.
Paid partnership (ad)
10
1
13
1,574
If you're a founder, learn this before you start scaling fast: Every new employee can create new payroll, tax, benefits, compliance, and IT workflows. If you’re still running those workflows manually, they become harder to keep up with every time you hire. Warp uses AI agents to manage HR automatically.
We’ve raised $85M for this moment. Introducing Warp 2.0: The first AI Head of HR. Every company is building AI to replace jobs. Warp is building AI to do the jobs no human should have to: If you work in HR, I want you to spend time with the manager who needs help or building company culture people actually want to work at. If you’re a founder, I want you to focus on signing clients or spending time with your family. You shouldn’t have to figure out how to register state tax in California. You shouldn’t have to pay outrageous penalties because you don't know what a DE 9C is. I want to make HR human again. Today, this is finally possible with the Warp Agent. I’d love for you to see it in action: warp.co/agent
Paid partnership (ad)
2
1
10
2,060
Build for scale when nobody’s scaling. Plan for failure when nothing’s failing. Add redundancy when nothing’s breaking. That is system design for you.
9
2
17
1,975
The Art Of AI Engineering Leverage (How Viktor Routed 13 Issues From Slack To GitHub In One Week): AI is making engineers faster at writing code. But code was never the only thing slowing engineering teams down. 1 Bugs get reported in Slack, 2 Someone has to collect context, 3 Turn it into an issue every morning, 4 Make sure the work actually gets tracked. Multiply that across an engineering team & you get a lot of work happening around the code. We’re building a mobile app to help people learn software architecture. At first, we tried handling this manually between Slack & GitHub. But someone still had to move the context between them. So we gave Viktor (our AI employee) ownership of engineering issue coordination. We added him to Slack & connected him to GitHub. Now when our team finds an issue, Viktor takes the context from Slack & turns it into tracked work in GitHub. But we took it one step further... Every morning, Viktor reviews the open issues & sends our team a short brief with what still needs attention. So instead of starting the day by checking Slack threads & GitHub issues, our team starts with the work that needs attention. If something requires a decision, Viktor brings it back to us with a recommendation. He proposes…we approve. Viktor routed 13 issues from Slack to GitHub in our first week with him. As coding gets faster, I think the engineering teams that move fastest will automate more of the coordination around the code. A copilot helps you work. An AI employee works when you don't. Hire @viktor_com for your team. $100 in credits included, no card. Full link in the first reply. #AIemployee #SoftwareEngineering Paid Partnership
Paid partnership (ad)
5
1
21
2,030
Dreamina AI updated its web experience and canvas, and it’s live now. @Dreamina_ai #DreaminaCaughtTheVibe The update brings high quality AI video workflows and skills for film, brand ads, viral social content, and more, making it easier to explore ideas and keep the creative process moving in one place. Get 90% OFF your first month of Dreamina Basic until October 9th. Try it on your next creative idea.
The all-new Dreamina AI web experience is LIVE! Every imagination deserves cinematic expression. 🎬 Cinema-grade skills and master workflows, right at your fingertips ▪ Filmmaking — Textbook cinematography skills, delivering theater-grade quality frame after frame. ▪ Advertising & marketing — Brand-grade workflows, bringing every concept to blockbuster quality. ▪ Creator content — The production process behind breakout short-form hits, out in the open and ready to learn. 📃 A rebuilt creation flow ▪ Dual entry points: Generate and Canvas—switch whenever the work calls for it. ▪ A smarter AI agent: multi-session management, every step visible start to finish. ▪ One integrated canvas: text, image, video, and audio—full control across the whole process. Film-grade creation, now within reach. ✨ Try it now: dreamina.capcut.com/ai-tool/…​ ⏰ Giveaway: Repost + comment on this post within 12 hours—the first 300 get 1,000 credits. #DreaminaAI #DreaminaAIweb
Paid partnership (ad)
7
1
7
2,039
If you want to go GOD-level with API design, learn these 7 protocols (save now):
9
25
266
35,263
👋 PS - Want to make your AI agents real-time? Polling for updates adds unnecessary latency to agent workflows. Webhooks let your agents react to events as they happen. But running reliable webhook infrastructure means dealing with failed endpoints, retries, security & monitoring. Svix handles that infrastructure for you, including automatic retries, signing, observability & idempotency support. Get started with Svix: link.svix.com/sys-design
1
3
1,429
Anything else you'd add? ♻ Repost to help others learn API protocols.
2
957