00:00:00I've never felt this much behind as a programmer. The profession is being dramatically refactored
00:00:06as the bits contributed by the programmer are increasingly sparse and between. I have a sense
00:00:11that I could be 10x more powerful if I just properly string together what has become available
00:00:17over the last year. And a failure to claim the boost feels decidedly like skill issue.
00:00:23Let's talk about this post by Andresh Kaparthi. These days, it's super easy to feel behind as
00:00:30a developer. Because there's so much buzz going on about AI, about new models dropping every day,
00:00:36new tools and new patterns of using these tools that you can feel behind. And just to be very
00:00:44clear, there are many amazing models like Opus 4.5 and there are amazing tools like Cursor or
00:00:51Cloth Code or Open Code which I really love using. And you can get a lot of good things out of using
00:00:57these tools and I will share more resources on using these tools efficiently and how I use them
00:01:03and which patterns or best practices you could use there. But it's super easy to feel behind when you
00:01:12shouldn't. And I would argue there is no reason to feel behind. And here's why. In his post, Andresh
00:01:20states there is a new programmable layer of abstraction to master in addition to the usual
00:01:25layers below, which by the way is important. It's clear that those layers are not going away. Your
00:01:31skills will still be required, but let's ignore that for now. But the new layer on top of your
00:01:37skills as a developer is that you must know how to work with agents, sub-agents, how to write good
00:01:44prompts, manage the context, the memory, the different modes in which you can use AI tools,
00:01:49plan mode and build mode and ask mode or whatever you have, permissions, tools, plugins, skills, hooks,
00:01:55MCP, LSP, slash commands, workflows, and so on. So that feeling of having to master lots of new tools,
00:02:03lots of new patterns in order to work efficiently with AI. And it's easy to feel like this. I mean,
00:02:09if you take a look at the Cloth Code documentation, there are sub-agents which you can build. There are
00:02:14plugins which you can build or install. There are agent skills which you can build, which I by the
00:02:20way find really useful, but there's this. There are hooks which you can use to run some code
00:02:26automatically when certain events happen. Like for example, the agent is done with a certain task.
00:02:33There is MCP, so MCP servers, which you can add to Cloth Code to give it new capabilities. And then
00:02:41there are dozens of patterns you'll find on X and out there on the internet that tell you how to
00:02:47efficiently combine all these capabilities to get the most out of Cloth Code. I mean, there is this
00:02:53entire Ralph Wiggum thing going on, which essentially is a plugin you can add to Cloth Code to get it
00:03:02into a mode where it continues going autonomously, improving your code, solving new tasks, and so on.
00:03:08And therefore have this loop where it keeps improving and keeps iterating and takes you
00:03:16out of the loop at least to a decent amount so that it can work more on its own. There is a bunch
00:03:24going on. And that is exactly what Andres basically mentioned here. You can feel overwhelmed because
00:03:32there are so many things to learn and master. But here's the important thing. You don't need
00:03:37to master all of that. For example, Lee Robinson, which used to work as a developer relations guy at
00:03:46Vercel for Next.js, is now working for Cursor. And over the holidays, he built a Rust-based image
00:03:52compressor, VASM binary and SvelteKit app, entirely with Cursor and AI with, as far as I remember,
00:04:02without writing a single line of code himself. He got test coverage there and he did review the code
00:04:10and he did provide lots of guidance. It's not vibe coding. He had a clear vision and guided the model
00:04:16on how to build this app. But he built this image compression library from scratch with Rust with
00:04:23help of AI. And he made it very clear that he built 80% of this project without any custom rules. You
00:04:30know Cursor rules are these things you can set up to give Cursor some, well, rules it should hopefully
00:04:36follow or commands or anything else. So he did not set up this super complex workflow using that
00:04:43Ralph Wiggum style with plugins and MCPs and all working together and having this infinite loop of
00:04:49stuff going on and a bunch of skills and sub-agents. No, he just used Cursor with an AI model, I think
00:04:57it was Opus 4.5, and built this app step by step and of course with the agent doing essentially
00:05:03all the work but based on his guidance. And this is a really interesting project. It shows us how far
00:05:10you can get with AI as an assistant these days. Again, without vibe coding but by blending your
00:05:18expertise as a developer with the capabilities and the knowledge of these AI tools. And it's very
00:05:23possible by the way that this image compression library in Rust has problems. He writes that
00:05:29himself. It's absolutely possible that there are bugs or performance issues or anything like that
00:05:34in there but it's still an impressive feat. But it kind of goes against what we see in this tweet
00:05:40which does not mean that you can't feel behind. That is absolutely valid and we probably all
00:05:45feel it from time to time. It just means you don't need to use all these capabilities just
00:05:53to get the most out of AI. So you don't need to use it all. You can just use AI in a very natural
00:06:02way by providing good prompts, good context, and for example by having a test suite the AI agent
00:06:08can run to validate their results. So you want to have something there but you don't need to
00:06:13combine all these things and learn about all of them. And then there is another reason why
00:06:19you don't need to feel behind. And that other reason is that all that will change soon anyways.
00:06:27I mean from all these capabilities here how many have we had half a year ago? I don't even know
00:06:33but for example skills are a recent addition. It's very likely it's almost guaranteed that over the
00:06:39next month we'll collectively decide and find out that it's not that important to set up skills or
00:06:47use a bunch of plugins or use sub-agents or whatever. We might find out that we don't need
00:06:55as many MCPs. For example I personally don't really use any besides context 7 for documentation lookup
00:07:02and playwright in cloud code for example to allow it to test the app in a browser. There are people
00:07:09that absolutely swear on having a dozen of MCP servers but we'll collectively find out what adds
00:07:16a real benefit and what doesn't. And then there are these tools like cursor or cloud code which will
00:07:22simply do good things automatically for you to put it like this. I mean if you compare working with AI
00:07:30assistants now to one or two years ago there's a lot of stuff cursor and these other tools do for
00:07:37you. Take plan mode for example. In the past a year ago you had to plan yourself. You had to ask AI to
00:07:46create a plan and to validate that plan and to ask you some questions before it gets started. Now there
00:07:53is this plan mode built into those tools. Who knows what will be built into them in half a year or so.
00:07:59So being ahead now by building a super complex setup by combining all these things will not
00:08:06necessarily put you ahead for a long time if it does so at all. And therefore long story short
00:08:15it's easy to feel behind but there is really no reason to feel behind. You don't need to use
00:08:23all these tools to get something out of AI as a developer and all that will change soon anyways.
00:08:30Therefore yeah don't stress out about it. It's too easy to get FOMO and feel overwhelmed these days.
00:08:37Try to take a step back. Things will not be as bad or things are not as urgent as they
00:08:46might sometimes seem.