1
00:00:00,110 --> 00:00:01,520
Welcome to the Architecture 
Corner. 

2
00:00:01,530 --> 00:00:06,520
Today we're diving into a really
hot topic in tech right now, AIS

3
00:00:06,530 --> 00:00:10,210
impact on software development. 
You've probably heard the buzz. 

4
00:00:10,220 --> 00:00:14,430
Maybe coding is dead or even 
calls to, you know, dismiss the 

5
00:00:14,440 --> 00:00:17,220
AI hype. 
Our goal today, Let's try to cut

6
00:00:17,230 --> 00:00:19,400
through some of that noise. 
Find the really important 

7
00:00:19,410 --> 00:00:22,030
takeaways for developers trying 
to figure all this out. 

8
00:00:22,040 --> 00:00:24,090
Exactly. 
It's less about the hype and 

9
00:00:24,100 --> 00:00:26,790
more about, well, understanding 
the real shifts. 

10
00:00:26,840 --> 00:00:29,770
What skills do we need now? 
What's the actual reality for 

11
00:00:29,780 --> 00:00:31,150
developers on the ground today? 
OK. 

12
00:00:31,160 --> 00:00:32,290
Good. 
Let's maybe start with some 

13
00:00:32,299 --> 00:00:34,250
data, because we've all seen 
those headlines, right? 

14
00:00:34,320 --> 00:00:36,870
Things like developer job 
openings dropping sometimes like

15
00:00:36,880 --> 00:00:40,760
25%, that really feeds this 
narrative that AI is just gonna,

16
00:00:40,770 --> 00:00:42,620
well, replace programmers. 
Right. 

17
00:00:42,630 --> 00:00:44,800
And here's where it gets really 
interesting. 

18
00:00:44,810 --> 00:00:49,360
Hmm, yes, there's a noted drop 
looking ahead to 2025, but it's,

19
00:00:49,970 --> 00:00:52,810
it's way more complex than just 
AI taking over. 

20
00:00:52,890 --> 00:00:55,400
You have to think about other 
factors too, like how we even 

21
00:00:55,410 --> 00:00:58,780
define roles, computer 
programmer versus software 

22
00:00:58,790 --> 00:01:00,500
developer. 
That's changing. 

23
00:01:00,650 --> 00:01:02,980
Plus there's the whole post 
pandemic market correction, you 

24
00:01:02,990 --> 00:01:05,900
know, after that hiring frenzy 
and things like remote work 

25
00:01:05,910 --> 00:01:07,840
outsourcing, that's still a big 
trend. 

26
00:01:07,920 --> 00:01:11,140
So it's not just one thing. 
AI is having an impact, 

27
00:01:11,150 --> 00:01:15,240
definitely, but it seems focused
on a certain, let's say, type of

28
00:01:15,250 --> 00:01:17,640
development work. 
The developers who are really 

29
00:01:17,650 --> 00:01:19,900
thriving, they're the ones 
committed to constantly 

30
00:01:19,910 --> 00:01:23,660
learning, adapting, which 
ironically, Jenny, I can 

31
00:01:23,710 --> 00:01:26,080
actually help with. 
It makes that path easier in 

32
00:01:26,090 --> 00:01:28,480
some ways. 
Adapting that brings up new ways

33
00:01:28,490 --> 00:01:30,520
of working, doesn't it? 
And maybe some new risks. 

34
00:01:30,530 --> 00:01:32,780
I know the author Mario 
Bittencourt talks about this 

35
00:01:32,790 --> 00:01:36,140
idea of vibe coding underage. 
Karpathy coined it. 

36
00:01:36,150 --> 00:01:38,620
I think it's become super 
popular, that phrase. 

37
00:01:38,690 --> 00:01:41,550
But what does it actually mean? 
Yeah, that's a great point. 

38
00:01:41,590 --> 00:01:44,120
And we need to be careful about 
what some call semantic 

39
00:01:44,130 --> 00:01:47,620
diffusion, you know, where a 
buzzword just kind of loses its 

40
00:01:47,630 --> 00:01:50,340
original meaning. 
Vibe coding, really. 

41
00:01:50,390 --> 00:01:54,500
At its core, yeah, it's about 
sort of surrendering to the AI, 

42
00:01:54,510 --> 00:01:58,420
just blindly accepting what it 
spits out, fixing things with 

43
00:01:58,430 --> 00:02:00,710
more prompts instead of digging 
into the code yourself. 

44
00:02:01,460 --> 00:02:04,250
Mario Bettencourt suggests. 
Maybe it's OK for like, quick 

45
00:02:04,260 --> 00:02:07,750
throwaway projects, yeah, or 
maybe when maintainability, 

46
00:02:07,760 --> 00:02:09,910
security, those things aren't 
top priority. 

47
00:02:10,060 --> 00:02:13,310
But otherwise, yeah, it feels a 
bit irresponsible. 

48
00:02:13,410 --> 00:02:16,990
OK, so if vibe coding is maybe 
not the best path for serious 

49
00:02:17,000 --> 00:02:19,870
projects, how do developers 
navigate this effectively? 

50
00:02:19,880 --> 00:02:23,050
What tools, What strategies 
should we actually be using to 

51
00:02:23,060 --> 00:02:25,040
partner with AI? 
Well, it's kind of surprising is

52
00:02:25,050 --> 00:02:27,010
that a lot of developers still 
aren't really using Gen. 

53
00:02:27,020 --> 00:02:29,280
AI tools day-to-day. 
The keys really integration. 

54
00:02:29,290 --> 00:02:32,270
You need to pick a tool that 
integrates Gennai well. 

55
00:02:32,440 --> 00:02:35,290
Could be Cursor, Jetbrains, 
Vscode, Neovim. 

56
00:02:35,380 --> 00:02:38,750
Lots of options are emerging. 
The main thing is use them. 

57
00:02:38,790 --> 00:02:41,850
Learn what they can do, but also
critically what they can't do 

58
00:02:41,860 --> 00:02:43,560
well. 
Right, understand the limits. 

59
00:02:43,670 --> 00:02:46,720
Absolutely, and use the features
within your IDE. 

60
00:02:46,890 --> 00:02:50,320
That chat function especially 
when it knows your code context.

61
00:02:50,530 --> 00:02:53,840
Very useful code completion too.
That tab tab tab thing. 

62
00:02:53,890 --> 00:02:55,660
It's great for quick local 
changes. 

63
00:02:56,010 --> 00:02:59,000
Then you have multi edits for 
bigger stuff across files where 

64
00:02:59,010 --> 00:03:03,540
it suggests changes you confirm 
and the most powerful perhaps 

65
00:03:03,550 --> 00:03:05,020
are the agents. 
Agents. 

66
00:03:05,030 --> 00:03:08,320
What are those exactly? 
Think of them like more 

67
00:03:08,330 --> 00:03:11,800
autonomous helpers. 
They can handle multi step tasks

68
00:03:11,990 --> 00:03:15,180
like creating a whole new 
feature, updating existing ones,

69
00:03:15,190 --> 00:03:18,160
even bootstrapping an entire 
application based on commands. 

70
00:03:18,290 --> 00:03:20,900
Super powerful, but you have to 
stay in the driver's seat. 

71
00:03:20,950 --> 00:03:23,560
Always be in control. 
These tools sound amazing, 

72
00:03:23,570 --> 00:03:26,860
almost transformative, but how 
do we get the absolute most out 

73
00:03:26,870 --> 00:03:29,800
of them without, you know, 
falling into that vibe, coding 

74
00:03:29,810 --> 00:03:32,260
trap or other pitfalls? 
Crucial part, isn't it? 

75
00:03:32,370 --> 00:03:35,180
It's not just about installing a
plugin, it's about how you use 

76
00:03:35,190 --> 00:03:37,000
it. 
So maybe three key tips here. 

77
00:03:37,010 --> 00:03:39,020
First, contest is absolutely 
king. 

78
00:03:39,070 --> 00:03:41,220
Don't just give vague prompts, 
be specific. 

79
00:03:41,290 --> 00:03:43,160
Provide versions, documentation,
links. 

80
00:03:43,170 --> 00:03:46,260
If you can guide the AI, reduce 
those hallucinations. 

81
00:03:46,270 --> 00:03:48,300
Makes sense. 
Garbage in, garbage out still 

82
00:03:48,310 --> 00:03:49,820
applies. 
Pretty much, yeah. 

83
00:03:50,050 --> 00:03:52,760
Second, define your standards up
front. 

84
00:03:52,890 --> 00:03:55,720
You can actually set up 
instruction files in your IDE, 

85
00:03:56,200 --> 00:03:58,960
Tell the AI you're coding 
standards, project structure, 

86
00:03:59,010 --> 00:04:01,260
security rules. 
You could even ask the AI to 

87
00:04:01,270 --> 00:04:03,450
look at your code and help 
define those standards for. 

88
00:04:03,460 --> 00:04:07,540
You oh interesting, using AI to 
teach the AI about your project.

89
00:04:07,550 --> 00:04:11,370
Exactly. 
And 3rd, find balance breakdown 

90
00:04:11,380 --> 00:04:14,630
big tasks. 
If you give the AI a huge spec, 

91
00:04:14,700 --> 00:04:17,310
it might struggle. 
These models tend to remember 

92
00:04:17,320 --> 00:04:19,610
the beginning and end of a 
conversation best. 

93
00:04:19,680 --> 00:04:22,940
So break it down. 
Bootstrap first, then maybe you 

94
00:04:22,950 --> 00:04:25,370
work feature by feature, then 
refactor. 

95
00:04:25,420 --> 00:04:27,510
Smaller focused interactions 
work better. 

96
00:04:27,580 --> 00:04:31,190
OK, so we've gone from tackling 
those job loss fears to some 

97
00:04:31,200 --> 00:04:32,880
really practical ways to 
integrate. 

98
00:04:32,890 --> 00:04:34,400
Jenny. 
It really sounds like the craft 

99
00:04:34,410 --> 00:04:37,620
of development is evolving 
rather than just vanishing. 

100
00:04:37,630 --> 00:04:39,800
Absolutely. 
I mean, just ignoring Jenny I 

101
00:04:39,810 --> 00:04:42,480
and its potential value, not 
even trying it out periodically,

102
00:04:42,490 --> 00:04:45,620
that seems misguided. 
But blindly trusting everything 

103
00:04:45,630 --> 00:04:48,400
it generates is just as risky. 
The future here. 

104
00:04:48,410 --> 00:04:50,860
It's really what you decide to 
make of it, how you choose to 

105
00:04:50,870 --> 00:04:53,420
adapt. 
The powerful thought to end on 

106
00:04:53,650 --> 00:04:56,750
adaptation is key. 
For more details on everything 

107
00:04:56,760 --> 00:04:58,800
we discussed today, do check the
description. 

108
00:04:58,870 --> 00:05:00,560
And please don't forget to 
subscribe. 

109
00:05:00,570 --> 00:05:03,250
It's free to the Architecture 
Corner newsletter over at 

110
00:05:03,260 --> 00:05:06,330
architecturecorner.substack.com.
Thanks so much for joining us.