Science & Technology

It’s not just you

by The PrimeTime

📚 Main topics

CI and end-to-end testsAI-generated features can bring excessive end-to-end tests that are slow and flaky. Teams need to choose what to test and avoid accumulating huge test suites unnecessarily. 3:08
Context switchingAI can work faster than a developer in some moments and much slower in others, tempting people to start multiple tasks while waiting. The speaker says he works best with one or two tasks at a time. 4:40
Hype and unrealistic expectationsThe speaker pushes back on claims that developers must adopt every new AI tool or risk falling behind, and rejects the idea that AI can effortlessly build complex, resilient services. 6:14
Verbose AI outputAI often produces long, unhelpful explanations even when asked to be concise, wasting time and making it harder to find the useful point. 8:49
Ownership through iterationThe speaker recommends using an AI-built prototype to explore a problem, then designing and rebuilding a more thoughtful version. That process can reduce unnecessary code and help developers feel genuine ownership. 10:20
Junior developers and learningRelying on AI for instant output can deprive juniors of the chance to build expertise and recognize good design. The speaker urges them to keep learning through reading, hands-on work, and exploring trade-offs. 13:56

✨ Key takeaways

Use AI to explore, not just shipA prototype can reveal requirements and design choices; a deliberate second pass can produce a better-structured system with less code. 11:21
Keep building technical judgmentLearn about testing, edge cases, mocks, and dependency injection so you can assess AI-generated work rather than simply accepting it. 15:29
Avoid fear-driven adoptionTools and workflows change quickly, so claims that one specific approach is essential for future success should be treated skeptically. 6:14

🧠 Lessons learned

Be intentional about parallel workStarting extra tasks to fill AI wait time can leave developers overloaded and disoriented. Limit concurrent work to what you can genuinely manage. 5:11
Don’t be an AI proxyDevelopers should think through problems, trade-offs, tests, and system design instead of merely translating someone else’s instructions into prompts and merging the result. 17:32

🏁 Conclusion/next steps

Develop beyond promptingAI may become more capable, but the speaker argues that learning to reason about software is valuable now and helps developers contribute more than raw output. 16:30

programming software engineer software engineering developer web design web development programmer humor

Transcript excerpt

0:00 What when it comes to AI and software engineering are you struggling with the most? Now, obviously, this got a few views. Okay, 255,000 views, 336 comments, people are having problems. Whether you are somebody that just rejects AI altogether versus uh AI using for everything, it just seems like everybody has some sort of effect or upsetness about this unless if they are somehow magically completely insulated from the AI world. Now, you know me. I've kind of been thinking about this quite a bit. And I've been struggling over the last couple years about how I feel about this entire situation we're

0:32 going through. And I've made many YouTube videos talking about this. So, I figured, hey, let's go through the tweets. Let's see what people have to say, and I will give my professional opinion on each one of them. And this includes going over CI sucking, not being locked in, entirely too much hype, just useless walls of text. Oh my gosh. Lack of ownership or just simply trying to learn new things as a junior. All right, so we're going to have to talk about all them and I'm going to maybe some lukewarm takes, a couple hot takes.

🔒 The full, searchable transcript is available with Pro.

Suggestions