YouTube2Text

Which Skills Will Matter Most for Software Engineers? | Kunal Kushwaha — Transcript

by CodeRabbit · 15,562 words · 2,400 segments · language en · Watch on YouTube

Full transcript

  1. 0:00What apart from AI do you bring to the
  2. 0:03table is the question you need to ask
  3. 0:04yourself. I don't want to talk about
  4. 0:06code.
  5. 0:06>> Yeah.
  6. 0:06>> Don't talk about code with me. Talk to
  7. 0:08me about this website. What would you
  8. 0:10break down? How would that change the
  9. 0:12market? How would that change the
  10. 0:14industry? And what changes would you
  11. 0:16make if you had full creative control?
  12. 0:18>> So, it's really about focusing on this
  13. 0:20product mindset, I think, is what I'm
  14. 0:21hearing.
  15. 0:21>> Product mindset. Ship fast. Use AI to
  16. 0:24achieve all the tasks and goals,
  17. 0:26>> but make sure you're not completely
  18. 0:28relying on it. If I'm in my 40s and I
  19. 0:31built my career on being very
  20. 0:32knowledgeable in Kubernetes, for
  21. 0:34example, what did I do to remain
  22. 0:36relevant?
  23. 0:41Hello and welcome everyone to another
  24. 0:43episode of uh the merch, our podcast
  25. 0:45brought to you here live from the code
  26. 0:47rabbit headquarters in San Francisco.
  27. 0:49Today I'm super excited because I'm here
  28. 0:50with Kunal.
  29. 0:52>> Hi. So so excited.
  30. 0:54>> Yeah, good to have you here. Kunal,
  31. 0:55you've had an amazing career. you've
  32. 0:58been um making big waves in terms of the
  33. 1:00developer community. You've been a CNCF
  34. 1:03ambassador, GitHub star, uh amongst a
  35. 1:06bunch of other things. So, I'm very
  36. 1:07grateful that you took time today to
  37. 1:09continue our conversation actually from
  38. 1:11scale all the way now here to San
  39. 1:12Francisco.
  40. 1:13>> Always a pleasure and uh this is such an
  41. 1:16incredible office by the way. I've not
  42. 1:17been to the code rabbit office before.
  43. 1:19>> Yeah.
  44. 1:20>> Uh yeah, absolutely incredible. Thanks
  45. 1:22for having me. Well, I I am honored to
  46. 1:24be here with you and I think uh there's
  47. 1:27a lot of interesting things we can talk
  48. 1:28about. So,
  49. 1:29>> yeah. So excited. The weather's been a
  50. 1:31little interesting this week.
  51. 1:34>> It is it is San Francisco August. We we
  52. 1:37call it August actually. [laughter]
  53. 1:39>> Yeah.
  54. 1:40>> So, what you see outside here is is
  55. 1:42actually KL. Um K is the fog or the name
  56. 1:45of the fog I should say. Uh and um every
  57. 1:48time in August, you know, the all the
  58. 1:49fog comes in because there's so much
  59. 1:51heat being built up on the central
  60. 1:53continental mass of California creates
  61. 1:55an uplift and then it pulls in the
  62. 1:57evaporated air from the ocean and it
  63. 1:59just collects over San Francisco.
  64. 2:00>> It kind of reminds me of home back in
  65. 2:03London.
  66. 2:04>> Yeah. [laughter]
  67. 2:05But no, uh I like California.
  68. 2:08>> Yeah, it's a good place to be, right?
  69. 2:10>> Yeah.
  70. 2:10>> Yeah. For us coders, it's not too bad
  71. 2:12because we we have one more excuse not
  72. 2:14to leave the house.
  73. 2:14>> Yeah. Yeah. I mean, I'm in San Francisco
  74. 2:16every month, so it's like second home,
  75. 2:19>> I guess. Third home in this case, right?
  76. 2:21>> Third home now. Uh, I go I'm in San
  77. 2:23Francisco more than I'm in India.
  78. 2:25>> Oh, really?
  79. 2:25>> Um, yeah.
  80. 2:27>> So, this would be second home.
  81. 2:28>> Yeah, [laughter] that's actually an
  82. 2:30interesting point. I think we can um
  83. 2:32dive right in there actually because the
  84. 2:34last time we talked, which I mentioned
  85. 2:36earlier, was at ScaleCon, Pasadena. Um,
  86. 2:39and we had a very, very quick chat. We
  87. 2:41had our setup there. So you kind of
  88. 2:42sweeped in and we touched on a couple
  89. 2:44interesting points, but one thing we
  90. 2:45didn't get to talk about it was a bit of
  91. 2:48your upbringing, I guess you could call
  92. 2:50it. So, uh, I digged a little bit deeper
  93. 2:52into after you told me that you were
  94. 2:54going to go and tell Yeah. [laughter]
  95. 2:56>> So, I have some spicy takes, but I just
  96. 2:58I just thought I'd give you the
  97. 2:59opportunity to to tell the story
  98. 3:01yourself before I do. Um, can you tell
  99. 3:03us a little bit about how you ended up
  100. 3:05here?
  101. 3:05>> Well, where do I start?
  102. 3:06>> Yeah.
  103. 3:07>> So, I wanted to be a doctor when I was a
  104. 3:08kid. When I was five years old, I was
  105. 3:10like in an accident and um everything
  106. 3:14worked out fine. Since then I was like
  107. 3:16okay doctors are cool you know I want to
  108. 3:19be a doctor.
  109. 3:21Um by the time I was like 15 you have to
  110. 3:24pick a career path in high school. You
  111. 3:26have to either pick like science uh be
  112. 3:29that tech or u in India be that tech or
  113. 3:33medical or if you want to do accounts so
  114. 3:35commerce um or if you want to learn like
  115. 3:38history or whatever there's arts for
  116. 3:39that and um I realized I am terrible at
  117. 3:43memorizing things can't memorize
  118. 3:45anything I had my chemistry exam because
  119. 3:47you know in chemistry there's a lot of
  120. 3:48rules and for every rule there's like so
  121. 3:51many exceptions like okay this rule
  122. 3:52works fine but it's not going to apply
  123. 3:54for this compound because it's an
  124. 3:56exception. I could never memorize things
  125. 3:58like that, you know, like bookish jargon
  126. 4:00knowledge cuz I can just look it up. Why
  127. 4:02do I need to memorize, you know?
  128. 4:04>> Yeah.
  129. 4:05>> And uh I I was like, "Okay, I can't be a
  130. 4:07doctor cuz, you know, it's just so much
  131. 4:09memorizing and reading and whatnot." Um
  132. 4:13I was always into tech. Wasn't like a
  133. 4:15hardcore programmer.
  134. 4:16>> Started when I was in high school with
  135. 4:18C++, but nothing major. In India, when
  136. 4:20you're in high school, you're preparing
  137. 4:22for your university entrance exams.
  138. 4:24Here's a huge country, 1.4 4 billion
  139. 4:26people. So we have millions and millions
  140. 4:29of students who graduate every year. So
  141. 4:31a lot different than a much smaller
  142. 4:33country let's say somewhere in Europe or
  143. 4:36even the US compared to India because
  144. 4:39these millions of engineers graduate
  145. 4:41every year and now obviously they're all
  146. 4:44looking for jobs. So it's very
  147. 4:45competitive. So from the very young age
  148. 4:47we're put into that competitive mindset.
  149. 4:51Um there are various ways to get a role.
  150. 4:54I think in tech at least um throughout
  151. 4:56the you know last few decades um there
  152. 5:00are some really prestigious colleges in
  153. 5:02India because there's just so many
  154. 5:03students fighting for seeds
  155. 5:05>> um getting into those universities is
  156. 5:07not easy and it's not always about your
  157. 5:09interest it's about what the university
  158. 5:11wants maths maths physics and chemistry
  159. 5:14>> it's like I think the second toughest
  160. 5:15exam in the world I think China has the
  161. 5:17toughest one I can be wrong I don't know
  162. 5:19but it's like definitely up there yeah
  163. 5:22>> so yeah that didn't work out cuz I
  164. 5:24didn't I wasn't good at chemistry or as
  165. 5:26good as physi at physics. Um and then um
  166. 5:31then yeah what happened then I took a
  167. 5:33year gap and that's sort of like looked
  168. 5:35down upon in India. I know ear gaps in
  169. 5:37Europe are great. I'm going to take an
  170. 5:38ear gap. I want to travel.
  171. 5:40>> Yeah. So it's looked down upon in India
  172. 5:43just like okay why are you taking an ear
  173. 5:44gap because you know the race moves so
  174. 5:46fast.
  175. 5:47>> Yeah.
  176. 5:48>> Took an ear gap. tried for the exam
  177. 5:49again to get into the top ID Indian
  178. 5:52Institute of Technology. Didn't work out
  179. 5:53cuz
  180. 5:55>> I mean a million students take that exam
  181. 5:57every year. I think they have around
  182. 5:595,000 seats.
  183. 6:01>> Wow.
  184. 6:01>> Look at the odds.
  185. 6:02>> No.
  186. 6:02>> Even if you're great, you won't get
  187. 6:04computer science. But there's one option
  188. 6:06for me. Like I could get a really nice
  189. 6:08college, but then I wouldn't be studying
  190. 6:10computer science.
  191. 6:11>> I would be studying something else like
  192. 6:13metal energy or well, god forbid
  193. 6:15chemistry.
  194. 6:16>> Yeah,
  195. 6:17>> I don't hate chemistry. Okay. there's
  196. 6:18any chemistry lovers. I love chemistry
  197. 6:20but it's just uh I can't memorize the
  198. 6:23>> compounds. But anyway, um then I was
  199. 6:25like okay let's just get whatever I'm
  200. 6:27getting.
  201. 6:28>> So I did that and I was like okay in
  202. 6:30life I'm always like whatever happened
  203. 6:33whatever has happened has happened.
  204. 6:35>> Yeah.
  205. 6:35>> I mean sure that is just life. If
  206. 6:38sometimes things don't work out
  207. 6:39according to your plan
  208. 6:42>> you can't time travel. That's didn't get
  209. 6:45a college didn't get a college. What
  210. 6:46what what would I do you know? Yeah, of
  211. 6:48course.
  212. 6:48>> Um, so I can't time travel back, but
  213. 6:50whatever you have in your resources
  214. 6:52right now, just use that to make the
  215. 6:55best out of it. And that's what I do. So
  216. 6:56I was like, okay, I'm in a decent
  217. 6:58college now. And there are examples that
  218. 7:00I've seen. The CEO of Microsoft didn't
  219. 7:02go to IIT.
  220. 7:03>> Satya Nadella, he went to MIT. It's a
  221. 7:05private college in India. I got into
  222. 7:07MIT. So I'm like, not not MIT US. It's a
  223. 7:10Manifal Institute of Technology in
  224. 7:12[laughter] India. Um, so I'm like,
  225. 7:14"Okay, these people are doing great, you
  226. 7:16know, things in life.
  227. 7:18>> The IIT tag is not the only thing." So I
  228. 7:20was like, "If they can do it, I can do
  229. 7:21it."
  230. 7:22>> Yeah.
  231. 7:22>> And then then I was like, "Okay, I'm
  232. 7:23just going to start learning and
  233. 7:25building and just do a bunch of cool
  234. 7:27stuff." That's when I found open source
  235. 7:29changed my life. Um,
  236. 7:32and yeah, I mean then that's that's how
  237. 7:34it started.
  238. 7:35>> Yeah. How do you say open source changed
  239. 7:37your life? I mean it's there's so much
  240. 7:40competition in the market you know um uh
  241. 7:44think from a student's point of view
  242. 7:46they're looking for internships first
  243. 7:47then they look for full-time roles
  244. 7:49>> it's a standard thing uh but when you go
  245. 7:52for an internship you have to send a
  246. 7:54resume in and in the resume they mention
  247. 7:57what have you done in the past and the
  248. 7:58students like I haven't done anything
  249. 8:00because I didn't have an internship but
  250. 8:02you need to put something in your resume
  251. 8:03to get the internship just like deadlock
  252. 8:06>> um open source is great because um you
  253. 8:09don't need to interview at a company.
  254. 8:11You can just pick a nice cool project.
  255. 8:12>> Yeah.
  256. 8:13>> Um contribute to it, put that on your
  257. 8:16resume,
  258. 8:18career takes off. So if you're a
  259. 8:19contributor, if you're a hardcore
  260. 8:20contributor in Kubernetes, like you
  261. 8:22wouldn't have issues at least getting an
  262. 8:24interview from some top tech companies,
  263. 8:27you know, like I got uh from Red Hat um
  264. 8:31some other companies and um it just
  265. 8:34opens a lot of doors for you and you get
  266. 8:36to meet a lot of cool people and I think
  267. 8:38that was the main main thing. Um yeah, I
  268. 8:42contributed to Kubernetes when I was in
  269. 8:44sophomore year.
  270. 8:45>> Wow. And then yes then I my whole career
  271. 8:48was in cloud native still am now
  272. 8:50obviously AI.
  273. 8:51>> Yeah.
  274. 8:51>> Um and yeah which is a bit interesting
  275. 8:55because the complaint I see from people
  276. 8:57is like open source is so complex like
  277. 8:59these projects are so big to contribute
  278. 9:00to.
  279. 9:02>> But it doesn't mean that it's not open
  280. 9:04to beginners. I mean cubernet is I think
  281. 9:07second largest project in the world
  282. 9:08after Linux.
  283. 9:09>> It's also one of the most welcoming.
  284. 9:13That's the word I'm looking for. Mhm.
  285. 9:14>> So they are always looking for
  286. 9:16contributors. There are a number of
  287. 9:17things you can do. Code contributions,
  288. 9:18non-code contributions. The key is just
  289. 9:21getting started. Um the one last thing
  290. 9:24is like if you don't put in efforts
  291. 9:25yourself,
  292. 9:26>> I mean the community people are there to
  293. 9:29help you but if someone sees this person
  294. 9:31is not putting efforts themselves, no
  295. 9:32one's going to help you.
  296. 9:34>> Well, how do you feel like that now
  297. 9:36changed? Because I mean it seems to me I
  298. 9:38have my open claw running. I can just,
  299. 9:40you know, pick up the repo and tell it
  300. 9:41to make a contribution. Like how If this
  301. 9:44happened now, yeah,
  302. 9:45>> this my story happened now. I was in a
  303. 9:47uni that wasn't as good and now I'm
  304. 9:49like, okay, I want to look for a role.
  305. 9:51[snorts]
  306. 9:51>> Okay, it's a good question. What would I
  307. 9:53do?
  308. 9:54>> Um,
  309. 9:55>> I feel like the way of contributing
  310. 9:56changed, right? Yeah, way way of
  311. 9:57contributing has changed but I think the
  312. 9:59whole narrative is the same in terms of
  313. 10:02building because
  314. 10:04programming languages and how we
  315. 10:06interact with the systems is just it's a
  316. 10:08mechanism you know 20 30 years down the
  317. 10:12line like sorry not down the line 20 30
  318. 10:14years before people were like coding in
  319. 10:15very low-level languages let's say even
  320. 10:18before that there were punch cards and
  321. 10:20whatnot
  322. 10:21>> so the problem solving mindset was still
  323. 10:23there so to answer your question I think
  324. 10:25gone are the days and companies are
  325. 10:27going to be like, I want to hire this
  326. 10:28person because they write better Java
  327. 10:30than this other person. I don't think
  328. 10:32that's going to be the case anymore.
  329. 10:34It's more about how much of a generalist
  330. 10:36are you, how can you
  331. 10:38>> I mean,
  332. 10:40how how well you communicate with
  333. 10:42others, for example, you know, other
  334. 10:43skills like empathy, problem solving.
  335. 10:46Um, I love the AI generation because I
  336. 10:49don't have to worry about syntax and
  337. 10:51programming languages and things like
  338. 10:52that. I have can focus on engineering. I
  339. 10:54can focus on building and you know
  340. 10:56problem solving and stuff like that. So
  341. 10:58AI takes a lot of that off my plate. Um
  342. 11:01so yeah I can write code as you know I
  343. 11:03can review code
  344. 11:04>> um do a bunch of stuff write docs
  345. 11:06testing and whatnot.
  346. 11:08>> So it's it's just giving people time
  347. 11:11>> you know to build stuff
  348. 11:14>> in the very short period of time. I mean
  349. 11:16my mother can build a website now.
  350. 11:18>> Yes.
  351. 11:18>> You know it's very simple easy for her.
  352. 11:20There's so many so many tools out there.
  353. 11:22So it's just giving people more control
  354. 11:24to you know um bring their ideas to
  355. 11:28reality. Um and this is a big thing for
  356. 11:30small businesses. You know I read this
  357. 11:32somewhere like when something becomes
  358. 11:33easier to do more people do it. And um
  359. 11:38yeah it's just how do you give access to
  360. 11:41you know the right tools to people at
  361. 11:43scale
  362. 11:43>> right and that is a beautiful arc I
  363. 11:45think to the next chapter of uh of your
  364. 11:48life which then focused on developer
  365. 11:50education. Right.
  366. 11:51>> Yeah. So can you tell me a bit more
  367. 11:53about how that how you got started? How
  368. 11:55what got you into that and how do you
  369. 11:57scale it today?
  370. 11:59>> Yeah. Um
  371. 12:01sophomore year I was in Kubernetes. I
  372. 12:03was contributing to Kubernetes and then
  373. 12:05um I was uh I got into this program
  374. 12:09called Google Summer of Code with Red
  375. 12:12Hat. It's like an open source program.
  376. 12:13You contribute to projects
  377. 12:15>> and then Google pays you.
  378. 12:17>> And then I was a mentor in that same
  379. 12:18program. And then I realized uh when I
  380. 12:21was learning how to code that I love
  381. 12:24going into the details of how things are
  382. 12:25working and whatnot and I love teaching.
  383. 12:28So I started volunteering at this local
  384. 12:30boot camp in Delhi and um I realized
  385. 12:34like I love teaching.
  386. 12:35>> Yeah.
  387. 12:35>> People told me you're so good at
  388. 12:37teaching.
  389. 12:38>> I know. Oh, I watched one [laughter] of
  390. 12:39your videos like you know what I really
  391. 12:41um it was uh crazy you I think one of
  392. 12:45your very early videos four years ago
  393. 12:47you have this scratch pad digital
  394. 12:48scratch pad on like a Windows or
  395. 12:50something.
  396. 12:51>> Yeah. Yeah. You just draw like little
  397. 12:52figures on it but it was so well
  398. 12:54explained
  399. 12:55>> and here we we all sitting there. I
  400. 12:57could use a lot of videos as well with
  401. 12:59crazy animations and so on and I thought
  402. 13:01like no it can be so simple. Yeah, it's
  403. 13:03uh people don't watch what you do, they
  404. 13:06watch how you do it. Even though there's
  405. 13:08a lot of tutorials on Kubernetes, if
  406. 13:11someone can explain Kubernetes in a in
  407. 13:13their own way, I think they'll get a lot
  408. 13:15of views and they'll get their own
  409. 13:16audience. So, it's [clears throat]
  410. 13:18>> this is what the question people have
  411. 13:19like, hey, why would I make a video on
  412. 13:21React or well something like codeex or
  413. 13:24whatever when there's already creators
  414. 13:26making videos on it? The topic doesn't
  415. 13:28matter. What matters is how you do it,
  416. 13:30>> you know. Uh but I realized I'm very
  417. 13:31good at like uh people say I'm very good
  418. 13:33at teaching and then um COVID came.
  419. 13:37>> Uh COVID came I was in San Diego 2019
  420. 13:40for CubeCon and then 2020ish early COVID
  421. 13:42came. So all these boot camps I was
  422. 13:45teaching at they had their own online
  423. 13:46portal. So all the kids were now
  424. 13:49learning online. Um
  425. 13:52and now uh they're like kunal you're not
  426. 13:55on the online portal. Yeah I didn't
  427. 13:57record videos for them. I just teach
  428. 13:58online in the in the building in person.
  429. 14:01They're like, "No, no, I'm going to
  430. 14:02learn from you."
  431. 14:03>> And I'm like, "Oh, okay." And I started
  432. 14:05my YouTube channel and I'm like, "Okay,
  433. 14:07if if you want to learn from me, it's co
  434. 14:09I'll just teach on YouTube." I remember
  435. 14:11I uploaded five videos on Python.
  436. 14:13>> Yeah.
  437. 14:14>> And each video was like 4 hour long.
  438. 14:17>> It was like full Python course in the
  439. 14:19depth.
  440. 14:20>> Yeah.
  441. 14:20>> With some like 10 projects or whatnot.
  442. 14:22Like if you don't know anything about
  443. 14:23programming, you could be like interview
  444. 14:26ready. that kind of yeah
  445. 14:28>> that I think because of that I got zero
  446. 14:31to 100k subscribers organically in like
  447. 14:342 and a half months
  448. 14:36>> and I realized okay this is this has
  449. 14:38been good people have been very kind
  450. 14:40>> you found your niche this is
  451. 14:41>> yeah people have been very kind to
  452. 14:42support and then I got into devops and
  453. 14:44then just started pushing more content
  454. 14:46teaching more people making education
  455. 14:48more accessible
  456. 14:50>> um and then I was like okay now I have a
  457. 14:53few it just kept growing in 100 in like
  458. 14:55a year I had like half a million or more
  459. 14:57than that.
  460. 14:58>> And then I was like, "Okay, all these
  461. 15:00people are now asking me questions."
  462. 15:01>> Yeah.
  463. 15:02>> So, what do I do? Cuz if someone is
  464. 15:05asking me a debugging uh like wants me
  465. 15:07to debug, help them debug something or
  466. 15:09whatever. The YouTube comments are not
  467. 15:10the right place for that.
  468. 15:12>> Like I'm like, "Okay, I'll start a
  469. 15:13Discord server."
  470. 15:14>> Started a Discord server.
  471. 15:16>> I don't remember what it's called. It
  472. 15:17was called something. And uh that grew
  473. 15:20to like 70 80,000 people. Um and then
  474. 15:25that converted to V make devs. So like
  475. 15:28we have this whole community um I
  476. 15:31started giving them challenges and we I
  477. 15:33was like okay um let's do some hackathon
  478. 15:35or something you know because have this
  479. 15:37big community and learning online is
  480. 15:40great but what I would recommend is to
  481. 15:43everyone even in today's age because you
  482. 15:44asked me earlier like what I would do in
  483. 15:46the AI age if I was a student now I I
  484. 15:49don't think much would change than what
  485. 15:51I did earlier honestly. Henrik um it's
  486. 15:54just the medium would change.
  487. 15:55>> I would be using a lot more AI tools.
  488. 15:57>> Yeah.
  489. 15:58>> But apart from that problem solving,
  490. 16:00contributing to open source, going to
  491. 16:02hackathons, creating content, writing
  492. 16:03blog posts, um speaking at conferences
  493. 16:07as a student.
  494. 16:08>> Um
  495. 16:10>> one word that I just get started.
  496. 16:11>> Yeah. That resonated with me was like I
  497. 16:13think learn in public. Is that
  498. 16:14something?
  499. 16:15>> Yeah. Build in public, learn in public
  500. 16:17cuz you get um learning in public
  501. 16:19doesn't mean like there's a mistake
  502. 16:21people make. They're watching my videos
  503. 16:23like today I learned u support vector
  504. 16:26machines from Kunal Goshwa.
  505. 16:27>> No one who is watching that post cares
  506. 16:30>> like [laughter]
  507. 16:32that's that's what the post would be
  508. 16:33today I learned about two-pointer from
  509. 16:35Kunal Kushwa.
  510. 16:36>> Mhm.
  511. 16:37>> That's not learning in public. That's
  512. 16:38just you sharing about your progress
  513. 16:39which is great.
  514. 16:40>> Yeah.
  515. 16:41>> But think about it like someone who is
  516. 16:43watching that post someone who's a
  517. 16:45really good engineer, senior person,
  518. 16:47it's not giving them enough value.
  519. 16:49>> Mhm.
  520. 16:49>> Right. It's just helping my promotions
  521. 16:51which I appreciate [laughter]
  522. 16:53you know I I appreciate that please keep
  523. 16:56it coming but no jokes aside
  524. 16:58>> when you talk about learning in public
  525. 16:59it's more about
  526. 17:01>> sharing your knowledge out there
  527. 17:02>> so I learned this computer course from
  528. 17:05Kunal or whatever
  529. 17:06>> if you find something interesting share
  530. 17:08about that write that in a blog post
  531. 17:09speak about it at a conference
  532. 17:11>> credit the creator if you saw the video
  533. 17:14from them if you want to no pressure um
  534. 17:18but that's what learning in public is
  535. 17:19all about and one other thing is because
  536. 17:20you get feedback from people in the
  537. 17:23industry and uh quite often I mean
  538. 17:26Twitter can X or LinkedIn can be a
  539. 17:29little uh
  540. 17:32what's the word I'm looking for
  541. 17:34>> cringe
  542. 17:35>> not cringe but like interesting place
  543. 17:37>> cuz sometimes if you ask for feedback
  544. 17:39people will have no filter they lack
  545. 17:42empathy is what I'm saying
  546. 17:43>> oh yeah I think especially the YouTube
  547. 17:45comments I don't know what's going wrong
  548. 17:46with people on YouTube but you need to
  549. 17:47stop like [laughter] guys this This is
  550. 17:49too much.
  551. 17:50>> No, one good other good thing is I get
  552. 17:52so many comments I just don't see a lot.
  553. 17:55>> Yeah.
  554. 17:55>> Uh criticism is fine or always welcomed.
  555. 17:59Let's make sure is I'm just saying like
  556. 18:00you will find people
  557. 18:01>> proportions like constructive.
  558. 18:02>> Yeah. You will find
  559. 18:04>> folks saying like hey this is not good
  560. 18:05but if if you're a student if you're
  561. 18:07just getting started
  562. 18:08>> I mean learning club is not just for
  563. 18:09students like anyone even if you're
  564. 18:11launching your own startup
  565. 18:12>> getting feedback online. I mean this is
  566. 18:13actually learning in public is what
  567. 18:15people do actually with these go to
  568. 18:16market sort of like activities because
  569. 18:18they do launch on product hunt and they
  570. 18:20get um sorry building in public yes
  571. 18:22>> which is sort of like you're learning
  572. 18:23from your customers or whatever.
  573. 18:26>> Uh but you're building in public you're
  574. 18:27doing soft launches on product hunt get
  575. 18:29a lot of feedback you're doing
  576. 18:30hackathons and stuff you're doing go to
  577. 18:32market events you're doing uh some
  578. 18:34webinars you're doing uh conference
  579. 18:36sponsorships so you're learning from the
  580. 18:38community in the public.
  581. 18:40>> Yeah.
  582. 18:40>> Right. It's just a different scale at
  583. 18:42what beginners do it at. But yeah, make
  584. 18:44sure the posts that you're making are
  585. 18:45valuable. Um, don't spam people. Don't
  586. 18:48use too many hashtags. Um, please stop
  587. 18:51the AI slop. It's just not going to
  588. 18:53work. It's it's not working. Use AI to
  589. 18:56write content. I'm totally for that.
  590. 18:58Okay?
  591. 18:59>> Use that uh to refine your content. I
  592. 19:02know English is not the first language
  593. 19:03for a lot of people.
  594. 19:04>> Yeah.
  595. 19:04>> Um, so you can use AI to sort of like
  596. 19:06help you with that, but some people just
  597. 19:08completely copy paste. We can tell.
  598. 19:11>> Oh, I mean I think then also the bot
  599. 19:12traffic and the bot commenters,
  600. 19:14especially LinkedIn, their banning
  601. 19:15algorithm is not so good yet.
  602. 19:17>> Yeah, it's not that good, but it's
  603. 19:18actually doing you more harm than good.
  604. 19:20>> Mhm.
  605. 19:21>> So, use AI. I'm very pro AI, but don't
  606. 19:24just copy paste uh comments. But yeah,
  607. 19:26for learning in public, getting feedback
  608. 19:28about your projects. Uh one best thing
  609. 19:31about learning in public is you make so
  610. 19:33many friends. I think that's the best
  611. 19:34thing.
  612. 19:34>> Okay.
  613. 19:35>> Um you make a lot of friends and you
  614. 19:37build your profile. Um,
  615. 19:40in the world is so small. Like every
  616. 19:42month in San Francisco, I run into
  617. 19:44someone that I knew from someone else.
  618. 19:47>> I mean, San Francisco is a surprisingly
  619. 19:50small city as well.
  620. 19:51>> The world is super small. [laughter]
  621. 19:54>> That's right. Well, yeah, I think from
  622. 19:57that arc, moving on, uh, you you talked
  623. 20:00about, you know, how you built this
  624. 20:02passion for learning and then how that
  625. 20:04translated into your community that
  626. 20:05you're building now. Can you tell me a
  627. 20:07bit more about that community? How big
  628. 20:09is it? What are what are you guys doing
  629. 20:10exactly?
  630. 20:12>> Yeah. So, when I was at conferences and
  631. 20:14stuff, uh when I was doing booth duty,
  632. 20:17it was great. There's just a lot of
  633. 20:19sales people in the room.
  634. 20:20>> Mhm.
  635. 20:20>> Which is fine. Sales people make it
  636. 20:22happen. They are the ones who bring
  637. 20:24money in.
  638. 20:24>> Yeah.
  639. 20:25>> But like if I want to if you want to if
  640. 20:27if I want to get developer feedback, if
  641. 20:29I want to get like what's wrong with the
  642. 20:31tool, what can I change? How easy was it
  643. 20:33to contribute? how easy was it to
  644. 20:36onboard and things like that. I think
  645. 20:39that's where you need to obviously get
  646. 20:40your hand get your tool in the hands of
  647. 20:42builders. So I think these sort of like
  648. 20:46go to market or engagement events that
  649. 20:48companies do. Let's say do like a
  650. 20:50workshop thingy or a webinar always talk
  651. 20:54always think about how engaged do you
  652. 20:56think people are.
  653. 20:58Some people they just do a webinar live
  654. 21:00and that doesn't really convert to
  655. 21:03anything. You know the argument they
  656. 21:04give is oh we got 100 email addresses
  657. 21:06yeah how many of them will reply to you
  658. 21:09know try getting a reply from everyone
  659. 21:11how many of them will get on a meeting
  660. 21:12with you so the coefficient factor for
  661. 21:16like how much engaged a person is I
  662. 21:19think that's something that you need to
  663. 21:21think about for your marketing efforts
  664. 21:23for developer not like you in general
  665. 21:25like uh people in general
  666. 21:27>> um hackathons are great because we we
  667. 21:31did one I think it was 2021 we got like
  668. 21:35um 2,000 something people and I hadn't
  669. 21:38even done
  670. 21:39>> any was it remote or
  671. 21:41>> it was remote from from my YouTube I
  672. 21:43think we got two two to 3,000ish or
  673. 21:45something
  674. 21:46>> and it was with elastic
  675. 21:47>> I remember
  676. 21:49>> um actually it was by Arvind
  677. 21:53>> Oh really Arvind for context is the
  678. 21:56previous VP of growth at great person
  679. 22:00>> great person and he was my first he was
  680. 22:01a very good friend so he was supportive
  681. 22:03and it was very small like event we did
  682. 22:06the budget was a thousand bucks. Um we
  683. 22:09got so many people share feedback and
  684. 22:11stuff and then uh we just started doing
  685. 22:14more and more events. Um I think last
  686. 22:16year because we make devs community we
  687. 22:20we renamed it like last year but it was
  688. 22:22so big that we were trying to figure out
  689. 22:23okay what do I want to do?
  690. 22:24>> Okay I want to do workshops I want to do
  691. 22:26inerson meetups and stuff. We we did one
  692. 22:28or two more hackathons and I realized
  693. 22:30okay this is like the thing that people
  694. 22:33want.
  695. 22:34>> Yeah.
  696. 22:34>> The the community wants this because
  697. 22:36when we do hackathons that's the most
  698. 22:38engagement we get.
  699. 22:39>> So around 10,000 people
  700. 22:41>> Yeah. They try out the product you can
  701. 22:42be sure that everybody who attends will
  702. 22:44actually have physical touch with the
  703. 22:46tools of the sponsors.
  704. 22:48>> Yeah. So for for the attendees uh and
  705. 22:50then I was like okay let's just do
  706. 22:52hackathons. That's what's working. Let's
  707. 22:53just do that.
  708. 22:54>> There are two strains to it. One is why
  709. 22:56would the audience care? Mhm.
  710. 22:57>> Why do the companies care?
  711. 22:59>> So for the audiences, I think they get
  712. 23:01to because there's the trend is shifting
  713. 23:03so fast. There's a new tool come out, a
  714. 23:05new inferencing tool will come out, a
  715. 23:07new monitoring tool will come out. Um
  716. 23:10>> the way we look at it differently at PMC
  717. 23:12Devs is we are we are riding with that
  718. 23:14trend.
  719. 23:15>> Something cool comes out, we give people
  720. 23:16the platform to build with it and share
  721. 23:19their feedback. That's what I care about
  722. 23:21the most because we have this incredible
  723. 23:24community behind us. The feedback that
  724. 23:26they give us is worth so much to well
  725. 23:31essentially all the companies in the
  726. 23:33world, the tech companies.
  727. 23:34>> Yeah.
  728. 23:34>> Because you know when a VC firm spons
  729. 23:37wants to invest in a company, they will
  730. 23:38go to like the research firms and some
  731. 23:40independent people. They pay them like
  732. 23:42two 300k for doing that background check
  733. 23:45about the industry analysis and whatnot.
  734. 23:48um big big companies like yeah like
  735. 23:52Gartner and stuff they publish their
  736. 23:54reports and they work with enterprises
  737. 23:56and share those findings and stuff with
  738. 23:58them. What we have found working with
  739. 24:00companies is um imagine this you're a
  740. 24:04company we're doing a hackathon together
  741. 24:0810,000 people test out your platform
  742. 24:11>> signups get up stars and whatnot
  743. 24:13>> I genuinely don't believe in vanity
  744. 24:15metrics I don't think it matters as much
  745. 24:18um may look good on the paper
  746. 24:21>> but the kind of numbers if you want to
  747. 24:23expect from a hackathon or like any
  748. 24:25conference you're sponsoring it doesn't
  749. 24:28matter if it's Not I mean in the end it
  750. 24:29doesn't matter if it's not directly
  751. 24:32relating to some sort of business
  752. 24:34outcomes
  753. 24:35>> you know because in the end that's what
  754. 24:37people care about that's what the come
  755. 24:38that's what's going to pay the salaries
  756. 24:40and whatn not
  757. 24:41>> well I mean these events often they're
  758. 24:42there for generating pipeline for right
  759. 24:45>> yeah but it's sometimes you know most of
  760. 24:47the time it's like indirect as well so
  761. 24:49let's say if you're doing a hackathon
  762. 24:50with students
  763. 24:52>> um we do like professionals senior
  764. 24:55engineers and students and everyone
  765. 24:57included but that ROI you will get when
  766. 24:59the students graduate and now they're
  767. 25:02working at a company and they would know
  768. 25:03like okay if I want to do take an
  769. 25:07example I want to do code reviews
  770. 25:09>> I did code reviews when I was in u my
  771. 25:11uni
  772. 25:12>> and I used code rabbit so they you know
  773. 25:16kids they become like a community for
  774. 25:19their
  775. 25:21career
  776. 25:22>> it it transitions into the career
  777. 25:23because when they're new in the career
  778. 25:25they have to answer all these questions
  779. 25:27I've given this task ask him what do I
  780. 25:28do? Oh, I used this tool like a few
  781. 25:30years ago. Why do you think all these
  782. 25:31big companies like uh you know all the
  783. 25:33hyperscalers they all have their student
  784. 25:35programs?
  785. 25:36>> Oh yeah, I know. I for me I
  786. 25:37[clears throat] studied meatronics in in
  787. 25:39university and I remember still working
  788. 25:41without a desk for my CAD project. So
  789. 25:43>> yeah,
  790. 25:44>> so it translates it just carries on and
  791. 25:47the time moves by so fast. These people
  792. 25:48will graduate they'll become seniors and
  793. 25:51now you have your own sort
  794. 25:52[clears throat] of like community
  795. 25:53members. So even though if like let's
  796. 25:55say you're at an event, you're just
  797. 25:57scanning people. Let's say you're at the
  798. 25:58booth duty. Someone comes in, you're
  799. 26:00like, "Hey, can I scan you? I'll give
  800. 26:01you a t-shirt." And the guy and the
  801. 26:03person's like, "Yeah, sure." Scan them,
  802. 26:05give them a t-shirt. Then you go to your
  803. 26:07VP, "Hey, we got a thousand lead scans."
  804. 26:10And then you reach out to the thousand
  805. 26:11lead scans and there's just no reply,
  806. 26:13nothing.
  807. 26:14>> It just looks good on paper.
  808. 26:15>> Yes.
  809. 26:16>> That hey, we got thousand leads from the
  810. 26:17event. Looks good for the CMO or
  811. 26:19whatever. But
  812. 26:20>> is that translating into anything? So
  813. 26:22how do you promote uh ROI from your
  814. 26:26events?
  815. 26:27>> So for us it's about the depth rather
  816. 26:29than just the numbers. There's this
  817. 26:30thing called value hours. The idea is
  818. 26:32that
  819. 26:33>> you did a hackathon or you did a webinar
  820. 26:35100 people came 1 hour was the average
  821. 26:36view time
  822. 26:37>> and there's a coefficient to it which is
  823. 26:39how engaged do you think the people
  824. 26:40were.
  825. 26:41>> Webinar people are not as engaged as
  826. 26:43inerson workshop. So let's put a
  827. 26:44coefficient of 0.5 100 into 1 hour into
  828. 26:470.5 50 hours of value hours. So that's
  829. 26:50like measuring the kind of depth how
  830. 26:52engaged the person is in your event. For
  831. 26:55our hackathon specifically, u it helps
  832. 26:57because it's hands-on.
  833. 26:58>> Yeah.
  834. 26:59>> Um the most important thing when we work
  835. 27:02with like enterprises, open source
  836. 27:03projects, dev tools, we got a lot of
  837. 27:05professionals and senior senior
  838. 27:07engineers. So we need to give incentive
  839. 27:09for them to come.
  840. 27:10>> So one of the incentives is you're
  841. 27:12riding the eye wave. You're basically
  842. 27:15any new cool tool comes out, we do a
  843. 27:17hackathon around it. any new industry
  844. 27:19sort of like term comes out we do a
  845. 27:21hackathon around it we get experts on
  846. 27:22this you know in the stream and you
  847. 27:24share resources that's the second part
  848. 27:27making it easy for people to contribute
  849. 27:30making it easy for people to build with
  850. 27:32these tools
  851. 27:33no one's judging you
  852. 27:35>> I think that's why people come to
  853. 27:36hackathons they want to learn they want
  854. 27:37to see what's out there
  855. 27:39>> surprisingly I thought it was going to
  856. 27:41be just students but we get like
  857. 27:43>> so many engineers and professionals
  858. 27:45>> yeah I mean
  859. 27:45>> the one we're doing in SF the one we did
  860. 27:47at GitHub hub 35% executives came
  861. 27:51uh 30 or something other person senior
  862. 27:54engineers and uh a lot of developers and
  863. 27:57people
  864. 27:58>> yeah over here you even see a lot of VC
  865. 27:59funds they sent some of their scouts to
  866. 28:01these tubby events too
  867. 28:03>> exactly yeah
  868. 28:04>> very interesting trajectory I want to
  869. 28:06pull us a little bit further um because
  870. 28:08I think one of the most interesting
  871. 28:09things that you experience every day
  872. 28:11through running all of these these
  873. 28:12events you're kind of so close to the
  874. 28:14developers of today and the developers
  875. 28:16of tomorrow really So can you give me of
  876. 28:18an impression like maybe you can start
  877. 28:19sharing of one of the most impressive
  878. 28:21projects that you've seen in the latest
  879. 28:23weeks or two weeks or month. Yeah. Um
  880. 28:25and then I'll be interested also to
  881. 28:26learn a little bit more how you see like
  882. 28:27the development workflow shifting on
  883. 28:30these events as well.
  884. 28:31>> Yeah. So what to what I was mentioning
  885. 28:34earlier like measuring ROI it's around
  886. 28:37for a dev tool if if I take as an
  887. 28:39example they care about we want feedback
  888. 28:43we want quality people like uh from all
  889. 28:46backgrounds when I mean quality people
  890. 28:48is people who are actively engaging with
  891. 28:49the platform can be students can be
  892. 28:51engineers want feedback for them from
  893. 28:53them we want to see use cases of our
  894. 28:55tool uh from the community and if they
  895. 28:58end up paying in the future we become
  896. 29:00like a sales pipeline or whatever that's
  897. 29:01a different story. Um the last hackathon
  898. 29:05we did to answer your question,
  899. 29:07>> it's a interesting story. We did it on
  900. 29:09Saturday.
  901. 29:10>> Yeah.
  902. 29:10>> Um at the Bright Data Loft with um port
  903. 29:15um and uh we had um
  904. 29:19Bright Data obviously we had people from
  905. 29:21Anthropic and stuff. It was a really
  906. 29:23nice big hackathon.
  907. 29:24>> Um we had a lot of people registered I
  908. 29:27think over 800.
  909. 29:28>> Wow. venue can already hold um close to
  910. 29:31200.
  911. 29:32>> So you had to cut people off at the
  912. 29:33door.
  913. 29:34>> Yeah. No, no, no. Uh we had weight list
  914. 29:36beforehand.
  915. 29:37>> Ah okay.
  916. 29:37>> So we had a weight list beforehand and
  917. 29:41uh this one kid came.
  918. 29:43>> He was at I think 12 years old.
  919. 29:45>> Oh wow.
  920. 29:45>> And he was on the wait list. So he
  921. 29:47didn't get in.
  922. 29:47>> Okay. And he's at the door and he's like
  923. 29:49his dad dropped him off and he's like
  924. 29:50hey I registered for the event and I'm
  925. 29:52looking on Luma and this guy is like 12
  926. 29:54years old on the Luma. he's not
  927. 29:56accepted, you know. And then I couldn't
  928. 29:58say no to him. I'm like, dude, just
  929. 30:00come. I'm coming. I'm just come on in.
  930. 30:02Yeah.
  931. 30:03>> So, I came [snorts] he came in and then
  932. 30:05um he was sitting I just gave him a
  933. 30:07desk. His some of his friends as well
  934. 30:10like yeah, just sit there build.
  935. 30:12>> In in my mind, I was like, "Okay, he's a
  936. 30:14kid. I mean, 12 years old." I was going
  937. 30:16to do
  938. 30:16>> when I was when I was 12, what was I
  939. 30:18going,
  940. 30:19>> you know?
  941. 30:20>> Yeah. His project was
  942. 30:24top three projects
  943. 30:26that I have received in the last 10
  944. 30:29hackathons we did.
  945. 30:30>> Wow.
  946. 30:30>> His project was insane.
  947. 30:31>> Thousands and thousands of submissions.
  948. 30:33>> His project was insane. He blew me out.
  949. 30:35He gave me imposter syndrome and I don't
  950. 30:37[laughter] get imposter syndrome.
  951. 30:40>> All right, tell me all about it. I want
  952. 30:42>> incredible. It was It was not mainly
  953. 30:43just about project. It's how first of
  954. 30:45all his demo video was so cool and cute.
  955. 30:48It was like a role play and he was role
  956. 30:50playing and he was acting and it was
  957. 30:52cool. He built like a go-to market sort
  958. 30:54of like app where you put a idea in his
  959. 30:57app. It's going to build the whole
  960. 30:59website and stuff. It's going to do
  961. 31:00research. It's going to pinpoint people
  962. 31:02in like San Francisco and stuff that can
  963. 31:04um you know um that you can engage with.
  964. 31:08The UI was incredible. how he used the
  965. 31:10whole pipeline for port bright data for
  966. 31:12scraping the uh data um from the
  967. 31:17internet and the UI was so good and uh
  968. 31:20the documentation you know small things
  969. 31:22like that because you have your project
  970. 31:24on GitHub right so small things like
  971. 31:25code quality and just how well you use
  972. 31:27the PRs the documentation read me
  973. 31:30>> and this was done in eight hours
  974. 31:32>> wow
  975. 31:33>> and I'll leave you'll see for yourself
  976. 31:35>> I mean just the guts to go there and
  977. 31:37heck with like people that are way way
  978. 31:39older than you build entire
  979. 31:41>> you know AI won't take your job these
  980. 31:42kids will [laughter]
  981. 31:45>> well yeah interesting that you say that
  982. 31:47because I think that's my my next point
  983. 31:48that I want to talk to you about it
  984. 31:50there's a lot of anxiety in the
  985. 31:52developer ecosystem right now about AI
  986. 31:55potentially taking that job like what
  987. 31:57what does it mean for me as a developer
  988. 31:59I spend so much time learning C++ I
  989. 32:03spent so much time understanding
  990. 32:05pointers and uh you know the complex
  991. 32:07relationship between hardware ware and
  992. 32:09software in these lower level languages
  993. 32:11and now all that time seems like it
  994. 32:16doesn't account to that much anymore for
  995. 32:18a lot of people and that triggers an
  996. 32:19anxiety how do you feel about that is a
  997. 32:23very good point I would say the number
  998. 32:26one benefit of going into these details
  999. 32:28for the basics for example is you
  1000. 32:31develop a superpower
  1001. 32:33>> you know what that superpower is
  1002. 32:35>> so the superpower is you learn how to
  1003. 32:39escape the hype cycle
  1004. 32:41because you know the fundamentals.
  1005. 32:43>> Mhm.
  1006. 32:44>> You cannot be persuaded with the hype.
  1007. 32:47>> Okay.
  1008. 32:48>> And that's very important.
  1009. 32:51>> So I always recommend focus on
  1010. 32:52fundamentals.
  1011. 32:53>> Yeah.
  1012. 32:54>> Um you don't have to be an expert in
  1013. 32:56every single thing.
  1014. 32:58>> Obviously there's pies learning. Know
  1015. 32:59something about uh know everything about
  1016. 33:01something something about everything. So
  1017. 33:03pick a niche. But I think with AI now is
  1018. 33:07I'm not going to say that it's not like
  1019. 33:08a time to worry but it depends where
  1020. 33:11you're coming from. There are a lot of
  1021. 33:13people in India who are like working at
  1022. 33:15very lower wages because
  1023. 33:20I mean there's a big divide in India
  1024. 33:21amongst engineers.
  1025. 33:22>> Mhm.
  1026. 33:23>> Some of the people are running
  1027. 33:24companies. Some people are, you know,
  1028. 33:26CEOs obviously at the big tech
  1029. 33:28companies, but also there are a lot of
  1030. 33:30outsourcing agencies that pay very
  1031. 33:33little amount compared to their home
  1032. 33:36country to developers in India.
  1033. 33:38>> They get a lot of stuff done. They don't
  1034. 33:40have a choice because they know that if
  1035. 33:42I quit this job that's paying me $3,000
  1036. 33:44a year, I'm not going to find another
  1037. 33:46one.
  1038. 33:47>> Right? The question you need to ask
  1039. 33:49yourself is why is it that someone from
  1040. 33:51India came from a village and they went
  1041. 33:54to US they went to London they they
  1042. 33:58obviously did something you know I
  1043. 34:01didn't come from a rich background my we
  1044. 34:02had debt and thing and um grew up in a
  1045. 34:06small apartment no no in no way
  1046. 34:09whatsoever I came from a rich background
  1047. 34:11didn't even go to uni in any university
  1048. 34:13outside India no masters nothing didn't
  1049. 34:15have you know it's expensive studying in
  1050. 34:18the US.
  1051. 34:18>> Yeah. [laughter]
  1052. 34:19>> Um so
  1053. 34:22with AI, I think all those people are
  1054. 34:25the ones who are going to be impacted
  1055. 34:26quite a bit.
  1056. 34:28So
  1057. 34:30it is time to worry but it depends where
  1058. 34:33you're coming from. Coming back to my
  1059. 34:35earlier point like you're not going to
  1060. 34:36be hired if you know one programming
  1061. 34:38language better than the other. Um I
  1062. 34:40think it's more about being a generalist
  1063. 34:43in all honesty. Mhm.
  1064. 34:45>> So if I'm giving an if I'm giving like
  1065. 34:48um task to a student right now, student
  1066. 34:51is like hey I have an interview and
  1067. 34:53whatnot and how do I prepare or what
  1068. 34:56task can you give me or like just in
  1069. 34:57general when I'm approaching founders
  1070. 34:59and recruiters and stuff give them a
  1071. 35:01website and ask them break down this
  1072. 35:03website for me. What would you change in
  1073. 35:06this website? I don't want to talk about
  1074. 35:07code.
  1075. 35:07>> Yeah.
  1076. 35:08>> Don't talk about code with me.
  1077. 35:09>> Talk to me about this website.
  1078. 35:11>> What would you break down? How would
  1079. 35:13that change the market? how would that
  1080. 35:14change the industry and what changes
  1081. 35:17would you make if you had full creative
  1082. 35:18control and things like that?
  1083. 35:20>> Yeah.
  1084. 35:20>> Um, so I think that's one and obviously
  1085. 35:23the second the obvious answers the
  1086. 35:25obvious answer is that how well people
  1087. 35:28work with these AI tools. So if you're
  1088. 35:29looking to get a job in law, what kind
  1089. 35:32of AI tools are being used in the law
  1090. 35:33industry? Um, if you're Kubernetes, how
  1091. 35:36do you use AI to make Kubernetes
  1092. 35:38smarter,
  1093. 35:39>> right? If you're in testing, how do you
  1094. 35:40do that? um if you're um if you're a
  1095. 35:45sort of data science person so there's a
  1096. 35:46lot of stuff that junior data scientists
  1097. 35:48used to do that now AI can do for you so
  1098. 35:51what apart from AI do you bring to the
  1099. 35:54table is the question you need to ask
  1100. 35:56yourself here's the other thing you know
  1101. 35:58why this is very important the the the
  1102. 36:00issue with people and students right now
  1103. 36:03you see them hey new uh model came out
  1104. 36:06and my tools and my pipeline and
  1105. 36:09everything is 30% more faster faster,
  1106. 36:1140% more accurate.
  1107. 36:13>> The model that just came out that I just
  1108. 36:15used in Claude is now 40 times more
  1109. 36:18smarter, you know, 40% more smarter. Um,
  1110. 36:22this new inferencing layer that came out
  1111. 36:25or whatever, this inferencing tool that
  1112. 36:27came out is 20% more smarter or faster.
  1113. 36:30This rooting mechanism that came out
  1114. 36:32that does everything for me, I just
  1115. 36:33write one prompt is now 10% more
  1116. 36:36smarter. What about you?
  1117. 36:39Are you smarter than what what you you
  1118. 36:41know than you what than what you were
  1119. 36:43yesterday? What are you doing to improve
  1120. 36:46your own personal self? So using these
  1121. 36:48AI tools as a helping hand is I think
  1122. 36:50the key. Uh don't worry about
  1123. 36:55don't worry about having n number of
  1124. 36:57things to learn. The industry will
  1125. 36:59always change. There's always going to
  1126. 37:00be something that you don't know and
  1127. 37:02that's fine. So it makes us human. Do
  1128. 37:04you know do you think I know everything
  1129. 37:05about Kubernetes? I don't. and I was
  1130. 37:07field CTO at Civo building data centers.
  1131. 37:09I don't know everything about
  1132. 37:10Kubernetes. I don't think many people
  1133. 37:12do. This is such a big project. I don't
  1134. 37:14know everything about Linux. I don't
  1135. 37:16know everything about networking,
  1136. 37:18>> but I know a lot from my hands-on
  1137. 37:20experiences, right? Um, so if you're
  1138. 37:24looking for if you're scared about
  1139. 37:25losing your job to AI, if AI can replace
  1140. 37:30any programming task that you're doing
  1141. 37:32right now, 100% you [clears throat] will
  1142. 37:34get replaced. No question about it. If
  1143. 37:36you're just good at C++ or Java and AI
  1144. 37:39can do that for you, you don't bring any
  1145. 37:41sort of other problem solving skills to
  1146. 37:43the table. Any sort of like uh uh you
  1147. 37:46know teamwork skills, empathy is
  1148. 37:49obviously a crucial one. How do you
  1149. 37:51interact well with developers, your
  1150. 37:53users, UI, UX and whatnot? Just the
  1151. 37:56whole sort of like shenanigan.
  1152. 37:58Yeah, if if AI can replace you, it will.
  1153. 38:02And um if you use AI as a helping hand
  1154. 38:06>> to sort of like um
  1155. 38:09empower stuff that you're already good
  1156. 38:11at,
  1157. 38:13I think it's great. So taking back to
  1158. 38:14the example of that 12-year-old kid, he
  1159. 38:16used claw or cordex or something pretty
  1160. 38:18heavily
  1161. 38:19>> but the thought process behind it, the
  1162. 38:21infrastructure behind it, the
  1163. 38:22architecture behind it. Um
  1164. 38:25a lot of questions lot of uh
  1165. 38:27conversations recently around
  1166. 38:28tokconomics people spending because you
  1167. 38:31know when cubernetes came around 2014
  1168. 38:33and then there was the cloud world
  1169. 38:34people money sending money in the cloud
  1170. 38:37bills and whatnot and now even today
  1171. 38:39there are so many companies active
  1172. 38:41there's a whole phops foundation the
  1173. 38:43whole idea of a phops foundation is
  1174. 38:44reducing your cloud bills there's so
  1175. 38:46many companies
  1176. 38:47>> you worked in that space before right
  1177. 38:49>> yeah I was at casti I was leading
  1178. 38:50developer relations and um business
  1179. 38:53doing some amazing so many companies
  1180. 38:55doing similar stuff.
  1181. 38:57>> So now we're seeing that with AI as
  1182. 38:58well. They have big budgets. Do you see
  1183. 39:00that? Did you see that news? 500
  1184. 39:02billion.
  1185. 39:03>> 500 million or 500 billion on cloud
  1186. 39:06bill. Half a bill something like that.
  1187. 39:09>> That would be like half of their
  1188. 39:10>> No, no, no. 500 million. 500 million.
  1189. 39:13>> I always think like cuz they Yeah. They
  1190. 39:14only have like somewhat billion of
  1191. 39:16revenue right now, which is crazy
  1192. 39:18already. But uh
  1193. 39:18>> Yeah. It can't be half a trillion
  1194. 39:20obviously.
  1195. 39:20>> Yeah. Yeah. [laughter] uh half a half a
  1196. 39:23billion dollars on claude bill and stuff
  1197. 39:26>> and even Sam Alman all these people are
  1198. 39:28now like hey um
  1199. 39:31>> people need to talk about you know
  1200. 39:33reducing their token costs
  1201. 39:35>> um a lot of uh agent hardnesses having
  1202. 39:38the narrative around that so AI won't
  1203. 39:41replace you personally a person using AI
  1204. 39:43will I don't know who said it
  1205. 39:45>> but it's a very good term but also
  1206. 39:47something becomes easier to do a lot
  1207. 39:49more people do it
  1208. 39:50>> you can spend spend more time in problem
  1209. 39:51solving. There are so many problems in
  1210. 39:53the world. Solve those problems. Use AI
  1211. 39:55to
  1212. 39:55>> Yeah.
  1213. 39:55>> as a helping hand.
  1214. 39:56>> I I want to dig a little bit deeper into
  1215. 39:58that because the I think the the topic
  1216. 39:59is really really important and you made
  1217. 40:02some great points, but I want to be a
  1218. 40:05bit more practical. What can I do if
  1219. 40:07I've been, you know, you are an
  1220. 40:08experienced engineer, you're not a
  1221. 40:10junior.
  1222. 40:11>> Um, for a junior, it seems somewhat
  1223. 40:13almost easier because you are not
  1224. 40:15constrained to the same ways of thinking
  1225. 40:17that that 12-year-old has no
  1226. 40:21restrain in the his head of like oh this
  1227. 40:23is the way I need to build this fast API
  1228. 40:25server first and then I can think about
  1229. 40:27how I scale out of this no he's just
  1230. 40:29like I want to I he almost has a natural
  1231. 40:31product sense which I think is what is
  1232. 40:33needed also for what you said in terms
  1233. 40:35of problem solving and building
  1234. 40:36something people want but if I'm in my
  1235. 40:3940s and I built my career on being very
  1236. 40:41knowledgeable in Kubernetes for example
  1237. 40:44what did I do to remain relevant do you
  1238. 40:47have a practical advice
  1239. 40:49>> if First of all, I'm 27.
  1240. 40:51>> Yeah.
  1241. 40:51>> Uh, so if if I was in my 40s,
  1242. 40:56>> again, it's it's about how you
  1243. 40:58communicate with the tools.
  1244. 41:00>> So code is just communication.
  1245. 41:03You has to write code, Java, C, C++, and
  1246. 41:06it just interacts with the systems. Now
  1247. 41:08that's transitioning into natural
  1248. 41:10languages. everything else behind that,
  1249. 41:13the architecture, how do you want to
  1250. 41:15system your, you know, architect your
  1251. 41:16system, how do you want to maintain it
  1252. 41:18and things like that, that's all still
  1253. 41:21there. There's always going to be a need
  1254. 41:22for a human to do that. So
  1255. 41:25my my answer is just in two parts. First
  1256. 41:29one being don't let go of the basics.
  1257. 41:31>> Yeah,
  1258. 41:32>> that's first.
  1259. 41:34Yeah, critical thinking. You you get to
  1260. 41:36escape the hype cycle. You get to know
  1261. 41:38the basic foundations and fundamentals.
  1262. 41:40Mhm.
  1263. 41:40>> And the second thing is like use AI to
  1264. 41:43automate the mundane tasks that you
  1265. 41:45don't like. Um and double down on
  1266. 41:50problem solving is what I would
  1267. 41:51recommend. So if you're 40 years old,
  1268. 41:53good news for you because uh you're so
  1269. 41:56into your career now. You have more time
  1270. 41:59to do stuff that was on your backlog.
  1271. 42:01And the last thing I would mention is I
  1272. 42:03don't know at which point we are now
  1273. 42:05where you can just I think we are there
  1274. 42:07that you can just approve the code that
  1275. 42:10AI wrote.
  1276. 42:11>> Oh.
  1277. 42:11>> Um
  1278. 42:12>> okay that's an interesting time. Yeah.
  1279. 42:14And
  1280. 42:14>> I mean it depends for I mean with code
  1281. 42:16review tools.
  1282. 42:17>> Okay.
  1283. 42:17>> I think they're quite smart enough to
  1284. 42:19figure out
  1285. 42:20>> there are any vulnerabilities and
  1286. 42:21whatnot.
  1287. 42:22>> Um but in the end there's always going
  1288. 42:25to be a human who's approving that
  1289. 42:27>> the PR being merged or whatever,
  1290. 42:29>> right? So when you are using these AI
  1291. 42:32tools to write code,
  1292. 42:35just make sure it's checked,
  1293. 42:38you know.
  1294. 42:38>> Yeah. And
  1295. 42:39>> apply your because you're the one who
  1296. 42:41still owns the the responsibility,
  1297. 42:43right, for whatever is shipped, not the
  1298. 42:44agent. You cannot blame the agent, but
  1299. 42:46you can also not fire the agent, but you
  1300. 42:48can fire yourself.
  1301. 42:48>> That's the other thing with AI like
  1302. 42:50agent. How do you give access uh AI? How
  1303. 42:53do you give identity access to AI
  1304. 42:55agents?
  1305. 42:56>> Mhm. You know, if agents mess some
  1306. 42:57messes something up, there needs an
  1307. 42:59identity attached to it that you can
  1308. 43:01call someone real.
  1309. 43:03>> Yeah. I mean, that's uh that's a whole
  1310. 43:05different discussion. I did had the
  1311. 43:06pleasure of recording an episode with
  1312. 43:08work, the founder of work. They do
  1313. 43:10authentication for agents. So, I
  1314. 43:12recommend people checking that out. I'll
  1315. 43:13happy to send it your way as well. He's
  1316. 43:15an amazing founder. The company is used
  1317. 43:17by companies like Anthropic, OpenAI, and
  1318. 43:19so on. They use his product. Um, but I
  1319. 43:22want to briefly stick around because I
  1320. 43:24think the topic is very interesting. Um,
  1321. 43:28let's talk about what you just said
  1322. 43:30regarding code review and code review
  1323. 43:32agents being good enough to review the
  1324. 43:33code. So, you don't need to actually
  1325. 43:35like you can just approve.
  1326. 43:37>> I've been hearing a lot of talk about
  1327. 43:39that not being the case. Recently, there
  1328. 43:42was the AI engineering code summit here
  1329. 43:45in San Francisco, World Fair, I think it
  1330. 43:46was called. Yeah,
  1331. 43:47>> I was there.
  1332. 43:48>> You were there. Yeah,
  1333. 43:49>> remember the talk from um shout out to
  1334. 43:52Dex Hury. He uh he made an amazing talk
  1335. 43:54about why agent software factories fail.
  1336. 43:58And the reason he brought was very
  1337. 44:00interesting because he said that
  1338. 44:01basically the reward system how we do
  1339. 44:05reinforcement learning today. It does
  1340. 44:07not take into account the long feedback
  1341. 44:09loop that you have when um agents write
  1342. 44:13unmaintainable code because the fact
  1343. 44:15that you have to do a refactor at some
  1344. 44:16point because things like performance
  1345. 44:18slows down or maybe you had some
  1346. 44:19security vulnerabilities that your tests
  1347. 44:21didn't catch and it deployed fine. All
  1348. 44:23of that is not built into the loop
  1349. 44:24because those issues arise three, four,
  1350. 44:26five, six, seven months later and that
  1351. 44:28hence they are not being downgraded in
  1352. 44:30the reinforcement loop and that's why
  1353. 44:32today you still have to look at the code
  1354. 44:34and you cannot just um deploy you know
  1355. 44:37lights off um software factories because
  1356. 44:40as you and I can talk to that too uh we
  1357. 44:43have the saying at code rabby the
  1358. 44:45entropy in your codebase gets bigger and
  1359. 44:47bigger as you deploy more and more
  1360. 44:49background coding agents into your your
  1361. 44:51codebase. I have a project that I've
  1362. 44:52been working on with coding agents for
  1363. 44:54about a year now and I can speak to that
  1364. 44:55like at the start when Esther first
  1365. 44:57built it out like I felt like I was
  1366. 44:59really using agentic engineering and uh
  1367. 45:02like putting the build it out very fast
  1368. 45:04build out the back end very well build
  1369. 45:05out the ETL pipeline that it needed to
  1370. 45:07process some things very well and I
  1371. 45:09really understood it now my agents are
  1372. 45:11in there all the time while I sleep or
  1373. 45:12while I go to my daytime job
  1374. 45:14>> and I just feel like the entropy has
  1375. 45:16increased so much so I don't I'm not I'm
  1376. 45:18sometimes worried when I click on the
  1377. 45:20even though all the flags are green I
  1378. 45:21don't Do you feel the same for some?
  1379. 45:23>> Let's take an example like Claude is
  1380. 45:24running if let's say Claude is running
  1381. 45:25your Slack and connected to your email.
  1382. 45:28It's essentially the same thing. You
  1383. 45:29could argue that hey, what if Claude
  1384. 45:31sent sends something messed up?
  1385. 45:33>> What if which it does,
  1386. 45:34>> you know, and like Yeah. So that's the
  1387. 45:36thing. It it does something very but
  1388. 45:37people are still like there's one entity
  1389. 45:39that's like I'm not going to give access
  1390. 45:41to my services to AI.
  1391. 45:42>> Mhm.
  1392. 45:42>> Which local AI is getting so popular,
  1393. 45:44you know,
  1394. 45:45>> uh because of that
  1395. 45:46>> and then the others are like okay I
  1396. 45:48don't care. um with code reviews in
  1397. 45:50itself I think it depends on the
  1398. 45:54what is at stake so for example I think
  1399. 45:58we will go into a era into an era where
  1400. 46:03humans are not reviewing code at all I
  1401. 46:05don't know when that will be 10 20 30
  1402. 46:07years down the line we will definitely
  1403. 46:08reach there that will happen
  1404. 46:11>> mhm
  1405. 46:12>> um because of how fast that things are
  1406. 46:13moving there's a lot of you know you
  1407. 46:15mentioned the context increasing and
  1408. 46:16increasing and increasing the whole
  1409. 46:18narrative around like company brains
  1410. 46:20obviously a lot of talk now now around
  1411. 46:23agent memory so that you don't have to
  1412. 46:25give the whole context again and again
  1413. 46:26in every conversation
  1414. 46:28>> but
  1415. 46:30human I could be wrong but human beings
  1416. 46:32not being reviewing not reviewing code
  1417. 46:34and just agent handling everything I
  1418. 46:36don't know you're saying that won't
  1419. 46:38happen in the next 50 years
  1420. 46:39>> oh no I will I'm
  1421. 46:40>> next 100 years
  1422. 46:41>> no no not even I'd say like I don't
  1423. 46:43think we're going to ship like that
  1424. 46:45actually
  1425. 46:47I work at a where we we build our
  1426. 46:49foundation on the fact that that will
  1427. 46:51not be the case anymore. Right. So we
  1428. 46:52building a [clears throat] lot lot of
  1429. 46:54tools. We just recently launched a tool
  1430. 46:56called change stack which is a
  1431. 46:57completely new way of how to review a
  1432. 46:59PR.
  1433. 47:00>> Yeah.
  1434. 47:00>> Uh so we don't we want to strip away
  1435. 47:02from you taking the the looking at the
  1436. 47:04code line by line and we are obstructing
  1437. 47:05multiple layers.
  1438. 47:06>> You have to you you have to because
  1439. 47:08these tools are so awesome. Why would
  1440. 47:10you not use it? If a
  1441. 47:13if an AI tool has that much potential
  1442. 47:15and power to scan the vulnerabilities
  1443. 47:17and check what happened in the industry
  1444. 47:19and make sure that you're not making the
  1445. 47:20same mistakes and stuff, no one's asking
  1446. 47:22you not to review it. But my point is
  1447. 47:25around how much of the what is at stake.
  1448. 47:28So I'll give you an example.
  1449. 47:29>> Mhm.
  1450. 47:30>> It's Black Friday.
  1451. 47:31>> Okay. You are a billion dollar company.
  1452. 47:33You're $20 billion company. You have a
  1453. 47:35big sale on Black Friday. Okay. Or
  1454. 47:37something like that. and you get paged
  1455. 47:39at 2 a.m. get paged at 2 a.m. that
  1456. 47:41something's messed up. You have to fix
  1457. 47:43it otherwise customers will get
  1458. 47:44affected. Let's say guaranteed let's
  1459. 47:47just say guaranteed you will lose uh
  1460. 47:48$500 million in sales guaranteed.
  1461. 47:51>> If you don't fix this now you have two
  1462. 47:53options. You can just ask AI hey
  1463. 47:56>> please fix this you know
  1464. 47:58>> make no mistakes
  1465. 47:59>> make no mistakes please fix it. You are
  1466. 48:01awesome very smart you are now working
  1467. 48:03as a senior debugging on call engineer
  1468. 48:06and whatn not. I don't think when a
  1469. 48:09billion dollar sale is on the line even
  1470. 48:12though the AI can do everything
  1471. 48:13perfectly the that human will double
  1472. 48:16check
  1473. 48:17>> there's so much on the line
  1474. 48:19>> you know so it's more about the
  1475. 48:20emotional aspect of it as well let's say
  1476. 48:2310 years down the line you get into the
  1477. 48:25same issue
  1478. 48:26>> oh yeah there's there's there's the CEO
  1479. 48:28of Versel he made this post Giamo uh
  1480. 48:31there's like if you're not looking at
  1481. 48:33code anymore the one of these five
  1482. 48:34things is true and he like listed about
  1483. 48:37either you don't have customers or you
  1484. 48:39don't have revenue or you are still
  1485. 48:41experimenting or something.
  1486. 48:42>> So even if 10 years down the line we
  1487. 48:44reach a point where
  1488. 48:46>> you know you don't have to look into the
  1489. 48:48AI code review which we probably will.
  1490. 48:50So that was my earlier point like right
  1491. 48:51now we are heading in a direction where
  1492. 48:54you don't have to review the code
  1493. 48:56>> but the thing is that if something
  1494. 48:57breaks
  1495. 48:59the human is going to be in charge
  1496. 49:01>> but don't you think that we have to
  1497. 49:03understand the change still
  1498. 49:06>> you do but it again depends on the
  1499. 49:08context if I'm changing a button's color
  1500. 49:10>> I'm not reviewing much
  1501. 49:12>> okay so we're building a lot of tools
  1502. 49:14here around helping you understand the
  1503. 49:16blast radius of your changes like the
  1504. 49:18obstruction layer of what you touch.
  1505. 49:20Maybe you like you're doing a back end
  1506. 49:22change and trying to surface that maybe
  1507. 49:24your agent changed the front end file.
  1508. 49:25So bring that to your intention instead
  1509. 49:27of you having to dig through it or find
  1510. 49:28out in production later.
  1511. 49:30>> These type of things that's the way I
  1512. 49:31see personally the the world going on
  1513. 49:33that pace. And then next to that is also
  1514. 49:36then of course the security part which
  1515. 49:38>> obviously
  1516. 49:39>> a lot of the number of security
  1517. 49:41vulnerabilities that have increased in
  1518. 49:43the age of AI is just so much so many
  1519. 49:45secrets sprawls and whatnot. So yeah,
  1520. 49:48depends on the blast radius. Um, but
  1521. 49:51obviously in the end, whoever is
  1522. 49:52approving the PR is a human.
  1523. 49:54>> Yeah.
  1524. 49:54>> So that person will be responsible when
  1525. 49:56something, you know, the light LLM
  1526. 49:58attack that happened as well. So
  1527. 50:01>> that was incredible.
  1528. 50:02>> That was kind of that was kind of crazy.
  1529. 50:04>> Yeah.
  1530. 50:04>> So I'm very pro AI. Um but am I
  1531. 50:08comfortable right now just for
  1532. 50:10it to run my whole systems without me
  1533. 50:13being or my engineers being like okay
  1534. 50:15hey
  1535. 50:16>> we are the ones who are doing the final
  1536. 50:17approval
  1537. 50:19>> um no but it works hand in hand the
  1538. 50:23review that the code has given
  1539. 50:26>> read by human checks everything is fine
  1540. 50:28merge the PR and if you're not using
  1541. 50:31like AI code reviews to review code I
  1542. 50:34mean why not cuz they're super fast and
  1543. 50:35stuff you know why not use it. But in
  1544. 50:37the end, it's a human taking the check.
  1545. 50:40And to answer the point,
  1546. 50:43um, 10 years down the line, it's a Black
  1547. 50:46Friday sale, agent can solve the bug,
  1548. 50:49but the person will go on the laptop and
  1549. 50:51see themselves. You know, there's so
  1550. 50:53much on the line. So, if you don't have
  1551. 50:55paying customers, you don't care.
  1552. 50:57>> Yeah. No, that's f well put. Uh, moving
  1553. 51:00on the lines, I think another point that
  1554. 51:02I had in my mental notes of things that
  1555. 51:04I really wanted to get your talk on is
  1556. 51:06you're running so many events all over
  1557. 51:08the world, Europe, London, Paris, um,
  1558. 51:12Berlin, San Francisco all the time,
  1559. 51:14India, global events. So, you're very
  1560. 51:17close to um, a lot of incredible
  1561. 51:19builders that you just u were telling us
  1562. 51:21about earlier as well. How do you see
  1563. 51:24them building and how have you seen the
  1564. 51:26shift of them using the tools like you
  1565. 51:29know cloud using cloud was very
  1566. 51:31different today than it is from a year
  1567. 51:33ago and uh same goes with like some
  1568. 51:36tools that we don't we stopped using
  1569. 51:37maybe uh I remember for example windsurf
  1570. 51:40having huge popularity last summer and
  1571. 51:42then now it's kind of died down and I
  1572. 51:44guess Devon has taken over but then as
  1573. 51:46well like the approach of how we use
  1574. 51:48tools it used to be
  1575. 51:51taboo to kind of open massive PRs and
  1576. 51:53people be like, "Oh, you should break
  1577. 51:55that down and da and distribute it so
  1578. 51:57people can understand." Now it's like
  1579. 51:58you see on Twitter, you see big Ctos
  1580. 52:02posting 400,000 lines of PRs, whatever.
  1581. 52:05So, uh, tell me what how do you see the
  1582. 52:08shift?
  1583. 52:09>> Yeah, I mean in Europe,
  1584. 52:11I don't think in US many people care
  1585. 52:13about like data sovereignty as such. The
  1586. 52:16US has a big uh argument around that.
  1587. 52:19Even India with their um data production
  1588. 52:21laws now um at our hackathons we mainly
  1589. 52:25see people have now enough time because
  1590. 52:27they have just one day to build in the
  1591. 52:29in the event space you know so the the
  1592. 52:33idea is how do you well how how well do
  1593. 52:35you integrate the sponsor tools
  1594. 52:37>> um in your project
  1595. 52:38>> and I don't think many people are
  1596. 52:40spending too much time on UI
  1597. 52:42>> as much because they can just wipe code
  1598. 52:44UI and UX every single UI we see is like
  1599. 52:48incredible
  1600. 52:49Um and uh something that would take like
  1601. 52:53coding from scratch like I know you
  1602. 52:54didn't code it from scratch. I know you
  1603. 52:56used some sort of like AI tools for
  1604. 52:58that. Um one of the cool thing that
  1605. 53:00people do is like if they're working in
  1606. 53:02a team they would divide the teams. They
  1607. 53:04would like you use you work on the
  1608. 53:06testing part. You you work on the review
  1609. 53:08part. I'll work on the infrastructure.
  1610. 53:11>> Um but one other one other aspect is is
  1611. 53:14>> Are you saying they're not doing that
  1612. 53:15anymore? They're doing that. They are
  1613. 53:17doing that anymore. No, they are doing
  1614. 53:19that
  1615. 53:19>> at our I mean that's how I used to go to
  1616. 53:21hackathons as a student all the time as
  1617. 53:23well. Like I would build out the back
  1618. 53:24end and then this other guy would build
  1619. 53:26out the front end.
  1620. 53:26>> Yeah. Cuz usually in the big inerson
  1621. 53:28events they have many sponsors.
  1622. 53:29>> Yeah.
  1623. 53:30>> Right. So someone's doing this one
  1624. 53:31thing, someone's doing monitoring,
  1625. 53:33someone's setting up something else.
  1626. 53:34>> Yeah.
  1627. 53:34>> Um and then there's infrastructure. So
  1628. 53:36where do I host it?
  1629. 53:38>> And then somebody doesn't come through
  1630. 53:39with their partner, you're screwed.
  1631. 53:40>> Yeah. Someone's [laughter]
  1632. 53:41someone's just uh doing uh you've seen
  1633. 53:44this many times. Someone's just the
  1634. 53:46marketing person. They're the ones
  1635. 53:48>> you need them too though. They're very
  1636. 53:49important. Very important then because
  1637. 53:51then if can nobody can speak you don't
  1638. 53:52win.
  1639. 53:52>> They're they're telling you about the
  1640. 53:54content about how the direction should
  1641. 53:56be and about the
  1642. 53:57>> video when they do the uh recording for
  1643. 54:00the demo.
  1644. 54:00>> Yeah.
  1645. 54:01>> Um so we see also we also see cracked
  1646. 54:03engineers. One person will come alone.
  1647. 54:05>> Yeah.
  1648. 54:06>> And they will win.
  1649. 54:08>> So that's I think that's the main point.
  1650. 54:10uh for that for that person to be
  1651. 54:12working as a designer for that person to
  1652. 54:14be working as a infrastructure person as
  1653. 54:17a developer as a I don't think they
  1654. 54:19write test during the hackathon really
  1655. 54:22>> um
  1656. 54:23>> but that one person is now doing all
  1657. 54:24these things and that's made possible
  1658. 54:26via via AI in 8 hours being able to
  1659. 54:29delegate all these tasks so you can
  1660. 54:31focus on what my theme is what my
  1661. 54:33problem solving is what my
  1662. 54:34>> more solo developers know more solo
  1663. 54:36participants
  1664. 54:37>> 50%
  1665. 54:39That's crazy. It used to be like you
  1666. 54:41people would get anxiety because they go
  1667. 54:43to an event to a hackathon, they knew
  1668. 54:44they had to find a teammate otherwise
  1669. 54:46they would have no chance.
  1670. 54:47>> In VM devs, uh 50 something% come by
  1671. 54:51themselves.
  1672. 54:53>> Wow.
  1673. 54:53>> Yeah.
  1674. 54:54>> So that's a that's a huge shift.
  1675. 54:55>> Yeah. And that alone person can can do
  1676. 54:59all these things in eight hours because
  1677. 55:00of AI.
  1678. 55:01>> So
  1679. 55:03>> their main question is I need to well
  1680. 55:05obviously win. I need to make cool
  1681. 55:06projects. I need to integrate all the
  1682. 55:08sponsor tools. I need to work on my idea
  1683. 55:11and um presentation and whatnot and um
  1684. 55:16and obviously how these integrate with
  1685. 55:19each other. So it's not like they're
  1686. 55:20delegating the entire thing to claude. I
  1687. 55:22don't think that's going to work. It's
  1688. 55:23just that the way they communicate has
  1689. 55:25changed. They were writing code before.
  1690. 55:26They're still writing code, reviewing
  1691. 55:28code, but
  1692. 55:30coding tools are doing most of the heavy
  1693. 55:31lifting.
  1694. 55:32>> Okay. Interesting. Uh what is maybe give
  1695. 55:36me some some idea like what what type of
  1696. 55:37tools do you see most popularly used on
  1697. 55:39the market? Is everybody on claude or
  1698. 55:41>> Yeah. A lot of people on claude. Codex
  1699. 55:43is up there.
  1700. 55:44>> Yeah.
  1701. 55:44>> Um
  1702. 55:45>> cursor. Any cursup users you see on your
  1703. 55:47events?
  1704. 55:47>> Cursor.
  1705. 55:48>> Yeah.
  1706. 55:49>> Not as much.
  1707. 55:50>> No. Claude definitely and Codex.
  1708. 55:53>> Yeah.
  1709. 55:53>> In our events. Um and these are also not
  1710. 55:57like sponsors like they just bring their
  1711. 55:58own claw and codic setup.
  1712. 56:01>> Um
  1713. 56:02>> yeah.
  1714. 56:02>> Interesting. Any review tools?
  1715. 56:06>> Uh any review tools? [laughter] We did a
  1716. 56:08hack.
  1717. 56:09>> We did a hackathon with code rabbit.
  1718. 56:11>> Yeah.
  1719. 56:11>> I think um during hackathons people
  1720. 56:14don't care much about code quality.
  1721. 56:16>> Yeah. No, you just got to ship it.
  1722. 56:19That's fine.
  1723. 56:19>> You just got to ship it in 8 hours. Make
  1724. 56:21sure it works.
  1725. 56:22>> Make sure make sure it works for the
  1726. 56:23demo. That's it. Breaks afterwards.
  1727. 56:25That's fine. Then you onboard the users
  1728. 56:27and everything crashes. But yeah, it's
  1729. 56:28all right.
  1730. 56:28>> They're not they don't want they don't
  1731. 56:30really care that much about code
  1732. 56:31quality. They just want to ship ship
  1733. 56:33fast. Care about UI a lot because that's
  1734. 56:35you know
  1735. 56:36>> it looks cool so the judges are happy.
  1736. 56:38They care about deploying so people can
  1737. 56:40use it easily. Reversal is popular.
  1738. 56:42Versel is quite popular. Yeah.
  1739. 56:43>> No that's cool. Um how do you see I
  1740. 56:47guess in the in the trend of all of
  1741. 56:48these people that are participating?
  1742. 56:51Are there any patterns that you see and
  1743. 56:54folks that come to your events where
  1744. 56:55like okay these people they might be
  1745. 56:57coming quite successful in what they're
  1746. 56:58going to do?
  1747. 57:00You can definitely see seasoned uh
  1748. 57:03hackathon people at events. One trait
  1749. 57:06that I have seen uh is um when you have
  1750. 57:09uh let's say three or four sponsors in
  1751. 57:11hackathon think about online or in
  1752. 57:13person and you have a limited amount of
  1753. 57:14time.
  1754. 57:14>> Yeah.
  1755. 57:15>> Number one mistake I see people make who
  1756. 57:16don't win is they would have a lot of
  1757. 57:18features in line.
  1758. 57:19>> Yeah.
  1759. 57:20>> And they would be like I'm going to imp
  1760. 57:21implement all these and whatnot. The
  1761. 57:24person who wins
  1762. 57:27build a minimum viable product first.
  1763. 57:30Very simple UI, simple project that
  1764. 57:32narrate that narrates the idea they had
  1765. 57:34on initially.
  1766. 57:35>> Mhm.
  1767. 57:36>> Has a working feature, the main feature,
  1768. 57:39simple UI, integrates all the tools,
  1769. 57:42save that as version one for backup, and
  1770. 57:44then they build on top of that. This
  1771. 57:46helps a lot with stress because if
  1772. 57:48you're building something for 8 hours,
  1773. 57:51it you will get stressed a little bit
  1774. 57:53because the time is ticking.
  1775. 57:54>> This helps with stress quite a bit.
  1776. 57:56>> Yeah.
  1777. 57:57>> Um and the other thing is make it easy
  1778. 57:59for people to judge your project.
  1779. 58:01>> The some people will have like a signup
  1780. 58:03page or they would ask the people to
  1781. 58:05like pull up a Docker image. The judge
  1782. 58:07is not pulling a Docker image to run
  1783. 58:08your project.
  1784. 58:09>> You know, [laughter] keep the demo
  1785. 58:11open-ended.
  1786. 58:11>> Yeah. And the last thing would be um
  1787. 58:16the idea does not matter that much.
  1788. 58:18>> Oh really?
  1789. 58:19>> Yeah. I have because I have seen people
  1790. 58:22with the simplest ideas
  1791. 58:24>> and perfect execution win hackathons.
  1792. 58:27>> Okay.
  1793. 58:27>> So it's not like
  1794. 58:28>> what's perfect execution look like?
  1795. 58:30>> It just works and it's seamless and it's
  1796. 58:32good user interface and UI UI and stuff.
  1797. 58:35There was one hackathon where it was
  1798. 58:36like
  1799. 58:37>> there was just a lot of Chrome, you know
  1800. 58:39how there are a lot of Chrome tabs and
  1801. 58:40stuff. One project person built like
  1802. 58:42some extension to manage all those
  1803. 58:44external code.
  1804. 58:45>> Oh, I have a friend of mine. He needs
  1805. 58:47that package. Man, this sounds crazy.
  1806. 58:49>> Simple simple tool, simple execution,
  1807. 58:51won the won the project.
  1808. 58:53>> Uh I don't know which hackathon was
  1809. 58:54this.
  1810. 58:55>> Yeah.
  1811. 58:55>> So idea matters.
  1812. 58:57>> Uhhuh.
  1813. 58:58>> It's not like a crazy thing that's going
  1814. 59:00to let that's going to make you win. I
  1815. 59:02mean in my idea like in my world and
  1816. 59:04perception and I've I've done a fair
  1817. 59:06amount of hackathons to to to say that
  1818. 59:08but I felt like the idea was getting
  1819. 59:11more and more important because I feel
  1820. 59:13like the the problem solving skill the
  1821. 59:16um idea of focusing your attention on
  1822. 59:18something that brings value to people
  1823. 59:21and is kind of somewhat novel or breaks
  1824. 59:22the pattern even um is something that is
  1825. 59:25more and more important as the execution
  1826. 59:27gets easier and easier because of the AI
  1827. 59:29coding agent. Don't you agree? Yeah, but
  1828. 59:32if you want to win the judges at these
  1829. 59:36if you go to like a sponsored event
  1830. 59:38>> and [clears throat] you want to win a
  1831. 59:38sponsored track prize, they want to see
  1832. 59:41how well you integrated the sponsor
  1833. 59:42tools.
  1834. 59:43>> Oh,
  1835. 59:43>> and these seasoned hackathon people know
  1836. 59:45that.
  1837. 59:46>> Yeah.
  1838. 59:46>> So, the idea does matter. It's just that
  1839. 59:48if it's purely just the idea
  1840. 59:51>> and the execution is not there.
  1841. 59:53>> Yeah.
  1842. 59:53>> Then um you're not going to win.
  1843. 59:56>> Okay.
  1844. 59:57>> But the main thing is about if you're if
  1845. 59:58you're learning I'm going to say
  1846. 59:59something cringe. If you're learning
  1847. 1:00:00something new and you're having fun,
  1848. 1:00:02you're a winner.
  1849. 1:00:03>> I mean, that's true.
  1850. 1:00:04>> Um, but these people are seasoned
  1851. 1:00:06hackathon people. You'll see at big
  1852. 1:00:07prizes.
  1853. 1:00:08>> If a hackathon has like 100k in prizes,
  1854. 1:00:10you'll see a lot of people who are
  1855. 1:00:11seasoned hackathon professionals.
  1856. 1:00:12>> Okay.
  1857. 1:00:13>> They have their own setup, whole
  1858. 1:00:14templates and everything.
  1859. 1:00:15>> Sharks are these guys that come with
  1860. 1:00:17their own keyboard to the event with
  1861. 1:00:18their little stand or bring a second
  1862. 1:00:20monitor.
  1863. 1:00:20>> They bring a second monitor and uh
  1864. 1:00:23>> their ideas are always simple.
  1865. 1:00:25>> Yeah.
  1866. 1:00:26uh nothing too crazy and uh we don't
  1867. 1:00:29have themes in our hackathons as such we
  1868. 1:00:31keep it open-ended we can do anything
  1869. 1:00:33>> but obviously if it's a themed hackathon
  1870. 1:00:34like hey build the best uh project for
  1871. 1:00:37city infrastructure
  1872. 1:00:39>> obviously then how unique your idea is
  1873. 1:00:40matters
  1874. 1:00:41>> but idea alone won't do anything if you
  1875. 1:00:44are not executing it well someone with a
  1876. 1:00:47boring idea and perfect execution will
  1877. 1:00:48win over your great idea and lack of
  1878. 1:00:51execution [clears throat]
  1879. 1:00:52>> well I guess there's a tangent that you
  1880. 1:00:54can to the professional world as well.
  1881. 1:00:56If your boss gives you a task and you
  1882. 1:00:58you do like uh the craziest idea of how
  1883. 1:01:02to solve it and the craziest angle that
  1884. 1:01:03has super much potential but you don't
  1885. 1:01:05execute well
  1886. 1:01:06>> ship fast. This is what Zuckerberg also
  1887. 1:01:08did with the meta
  1888. 1:01:09>> the meta glasses thing. The whole AI
  1889. 1:01:12universe
  1890. 1:01:15he was doing and people were like oh no
  1891. 1:01:17his demo failed
  1892. 1:01:18>> and whatn not you know Zuckerberg's demo
  1893. 1:01:20failed and should have waited and this
  1894. 1:01:23and that. No, it's fine.
  1895. 1:01:26>> Yeah,
  1896. 1:01:26>> build, ship, iterate on it. It's good.
  1897. 1:01:30>> Well, that's true. I mean, it's also a
  1898. 1:01:31fair statement to make when you have the
  1899. 1:01:33entire distribution engine of the world
  1900. 1:01:34on your product. But
  1901. 1:01:35>> Exactly.
  1902. 1:01:36>> But yeah, actually that's that's true.
  1903. 1:01:38>> If it's like a smaller company, that
  1904. 1:01:40would backfire a little bit.
  1905. 1:01:42>> Yeah.
  1906. 1:01:42>> Which is why minimum vi minimum viable
  1907. 1:01:44product that you know will work.
  1908. 1:01:46>> Mhm.
  1909. 1:01:46>> And any other fancy other features you
  1910. 1:01:48want to add, just do it later.
  1911. 1:01:50>> Yeah.
  1912. 1:01:50>> But yeah, key is moving fast. Ship fast,
  1913. 1:01:52move fast, break things.
  1914. 1:01:54>> Yeah.
  1915. 1:01:54>> Learn from your users.
  1916. 1:01:56>> Great. Um, yeah, maybe starting to to
  1917. 1:01:59wrap up a little bit. I I'd love to
  1918. 1:02:01finish this wonderful conversation on a
  1919. 1:02:03couple of encouraging notes and
  1920. 1:02:05thoughts. Um, you just mentioned a few
  1921. 1:02:07of them. Ship fast, learn fast. You
  1922. 1:02:09know, this entire we hear that a lot.
  1923. 1:02:12Uh, do you have some practical advice
  1924. 1:02:13for people who might be listening
  1925. 1:02:14thinking like, hey, um, you know, some
  1926. 1:02:16of the things you just said really
  1927. 1:02:18resonated with me. I'm in that spot
  1928. 1:02:19where I'm somewhat in my career but not
  1929. 1:02:22truly AI native yet and I don't feel
  1930. 1:02:24like I need to get somewhere. Where
  1931. 1:02:25where do people pick up? What do I do?
  1932. 1:02:28>> Yeah, if you're looking for your next
  1933. 1:02:30role, I would say list down what kind of
  1934. 1:02:33role do you want?
  1935. 1:02:34>> It's your ideal company look like what
  1936. 1:02:36does that role look like? Like what does
  1937. 1:02:37the person need to do? And then see what
  1938. 1:02:39kind of AI tools are being used in that
  1939. 1:02:41role.
  1940. 1:02:42>> If you're just starting out, yeah, the
  1941. 1:02:44advice for you is very simple. It does
  1942. 1:02:46not matter. Go get started. Get a job at
  1943. 1:02:48the Apple store, learn everything about
  1944. 1:02:50the Apple ecosystem, build Apple apps,
  1945. 1:02:53then go to your next job, right? Does
  1946. 1:02:56not matter. The question around which
  1947. 1:02:57tool I get started with, language do I
  1948. 1:02:59get started, does not matter.
  1949. 1:03:01>> Just literally doesn't. Just get started
  1950. 1:03:03with building.
  1951. 1:03:04>> Um, that's my recommendation for juniors
  1952. 1:03:07like students.
  1953. 1:03:08>> Yeah,
  1954. 1:03:09>> just get started with building and as
  1955. 1:03:10you move forward, just experiment with
  1956. 1:03:12different tools, expand your horizon.
  1957. 1:03:15>> Yeah. No one expects you to be an expert
  1958. 1:03:17when you're a student 17 18 years old.
  1959. 1:03:19Um but what they do expect you to do is
  1960. 1:03:23have
  1961. 1:03:24enough drive and sort of like they want
  1962. 1:03:26to see what has this person done based
  1963. 1:03:29on the resources that they already have
  1964. 1:03:30available. So I go to hackathons meetups
  1965. 1:03:34speak at conferences learning in public
  1966. 1:03:36which we mentioned earlier.
  1967. 1:03:37>> It can be a little bit awkward speaking
  1968. 1:03:39at conferences
  1969. 1:03:40>> intimidating
  1970. 1:03:41>> intimidating but it's going to help you.
  1971. 1:03:43Yeah,
  1972. 1:03:43>> you know, and these conferences have
  1973. 1:03:45special tracks for first- time speakers.
  1974. 1:03:47>> So, that's working in your favor.
  1975. 1:03:50>> And if you're a senior engineer, um, mid
  1976. 1:03:53to level engineer,
  1977. 1:03:54>> I mean, you're already there. You're
  1978. 1:03:55already using AI in your sort of like
  1979. 1:03:58workflows.
  1980. 1:03:59>> Mhm.
  1981. 1:03:59>> But now you have more time for problem
  1982. 1:04:02solving and now you can shift faster.
  1983. 1:04:04>> So, it's truly about focusing on this
  1984. 1:04:06product mindset, I think, is what I'm
  1985. 1:04:07hearing.
  1986. 1:04:08>> Product mindset, shift fast, use AI to
  1987. 1:04:10achieve all the tasks and goals.
  1988. 1:04:12>> Yeah. But make sure you are
  1989. 1:04:15>> you're not completely relying on it.
  1990. 1:04:17>> Yeah. um using it as a helping hand and
  1991. 1:04:19when you're using AI to review code
  1992. 1:04:21tools and whatever
  1993. 1:04:22>> um yeah do a final check because if
  1994. 1:04:25something messes up you're the one who
  1995. 1:04:27is responsible and one one thing I
  1996. 1:04:29mentioned earlier in the three points
  1997. 1:04:31that I was mentioning when AI is writing
  1998. 1:04:33code this is also true for junior
  1999. 1:04:35engineers
  2000. 1:04:37um when AI is writing code especially if
  2001. 1:04:39you're a student and AI can build the
  2002. 1:04:40whole website for you that is great I
  2003. 1:04:43think you should do it but whatever the
  2004. 1:04:46AI I has written make sure you read
  2005. 1:04:48through that and understand and learn
  2006. 1:04:50from that
  2007. 1:04:50>> so that you are not just
  2008. 1:04:52>> a code monkey.
  2009. 1:04:53>> Yeah,
  2010. 1:04:54>> that's the word. So if you're a student,
  2011. 1:04:56use AI, use clot to code
  2012. 1:04:58>> 100%. But what it's generating after
  2013. 1:05:00it's done doing it, you can ask it
  2014. 1:05:02followup questions like hey explain to
  2015. 1:05:04me how this works, what function you
  2016. 1:05:06wrote. That's an interesting segue into
  2017. 1:05:09uh I mean also what you talked about the
  2018. 1:05:11next frontier of a engineering not being
  2019. 1:05:13in the code writing anymore but in the
  2020. 1:05:15architecture level and truly
  2021. 1:05:16understanding as a software engineer
  2022. 1:05:18like what what is my next big thing that
  2023. 1:05:21I should learn study where do I bring
  2024. 1:05:23the most value today.
  2025. 1:05:24>> Yeah. Um
  2026. 1:05:28how to
  2027. 1:05:29if there's one thing I would say is
  2028. 1:05:32learn how to run LLMs locally.
  2029. 1:05:35Oh wow, that's a that's a good one.
  2030. 1:05:37That's a that's so
  2031. 1:05:38>> that's one thing that learn how to run
  2032. 1:05:40LLMs locally,
  2033. 1:05:41>> learn how to fine-tune models locally.
  2034. 1:05:44>> Um and uh how do you transition that
  2035. 1:05:48pipeline
  2036. 1:05:49>> uh at scale?
  2037. 1:05:51>> What kind of because that's where the
  2038. 1:05:52people are headed. you know a lot of
  2039. 1:05:54talk around uh uh running AI locally in
  2040. 1:05:58secure environments and there are any
  2041. 1:06:01number of things you can do to run that
  2042. 1:06:04to run LLMs on like infrastructure so
  2043. 1:06:06for example when Kubernetes came out
  2044. 1:06:08there's so many ways by which you can do
  2045. 1:06:09it can have your own virtual machines
  2046. 1:06:11and Kubernetes on top of that you can
  2047. 1:06:13use managed Kubernetes platforms like uh
  2048. 1:06:15EKS or whatever you can run it on that
  2049. 1:06:17you can use all these neo clouds and
  2050. 1:06:19smaller providers you can do that so
  2051. 1:06:20when you go to a job and the boss asks
  2052. 1:06:22you like you're just starting out and
  2053. 1:06:24hey we want to run LLMs we want to use
  2054. 1:06:26influencering tools we have 100 options
  2055. 1:06:28which one is the best so now if you have
  2056. 1:06:30the whole industry landscape idea
  2057. 1:06:32>> like hey you can be like we can just use
  2058. 1:06:33an API no we won't use an API we'll
  2059. 1:06:36we'll run it on our own hardware like
  2060. 1:06:38this no we won't use that we're going to
  2061. 1:06:39use Cerebras we're not going to use
  2062. 1:06:41Cerebras which is going to pay uh codecs
  2063. 1:06:43a monthly bill or whatnot
  2064. 1:06:45>> and um
  2065. 1:06:47>> yeah I mean you know about it like
  2066. 1:06:49running cubernetes there are so many
  2067. 1:06:50ways to do it the same thing with AI I
  2068. 1:06:52mean
  2069. 1:06:52run learn how to run AI models locally.
  2070. 1:06:55The other thing is because this is the
  2071. 1:06:57most basic thing the fundamental it's
  2072. 1:06:59like running a model on a machine is a
  2073. 1:07:01fundamental.
  2074. 1:07:02>> So it it brings us back to your earlier
  2075. 1:07:05point
  2076. 1:07:06>> the basics.
  2077. 1:07:07>> Yeah.
  2078. 1:07:07>> So it will teach you a lot
  2079. 1:07:10>> um which in itself is a lot of uh
  2080. 1:07:15>> valuable
  2081. 1:07:15>> there's you know the book uh not the
  2082. 1:07:17book the repository Cubanet is the hard
  2083. 1:07:18way by Kelsey High Totower.
  2084. 1:07:20>> Mhm. So if you're running Kubernetes
  2085. 1:07:22obviously in production you're let's say
  2086. 1:07:25billion dollar company you're most
  2087. 1:07:26probably using AWS
  2088. 1:07:28um
  2089. 1:07:30like Netflix uses AWS but those people
  2090. 1:07:33know how to run Kubernetes like on mini
  2091. 1:07:36cube or locally or in their own little
  2092. 1:07:38cluster right so that learning journey
  2093. 1:07:42that you get you get to see things
  2094. 1:07:44inside
  2095. 1:07:44>> and then you just use a managed service
  2096. 1:07:46to run that at scale
  2097. 1:07:47>> okay
  2098. 1:07:48>> so learn how to run LLMs locally It's a
  2099. 1:07:50lot of fun and you'll learn a lot.
  2100. 1:07:53[laughter]
  2101. 1:07:53>> You're going to see how it how it uh how
  2102. 1:07:55the networking works, how it interacts
  2103. 1:07:57with the
  2104. 1:07:58>> with other agents, how you run multiple
  2105. 1:08:00agents.
  2106. 1:08:01>> Um and then you just sort of like see
  2107. 1:08:02okay, how do I scale this now? And uh
  2108. 1:08:04yeah, but it's uh always comes down to
  2109. 1:08:07learn the basics.
  2110. 1:08:08>> Yeah. how things are working and when
  2111. 1:08:09you work with more complex tools um
  2112. 1:08:12whatever the complex tool gives you ask
  2113. 1:08:15it look at it study from it especially
  2114. 1:08:19if you're a student study from it
  2115. 1:08:20>> and then implement that
  2116. 1:08:22>> yeah an interesting quote comes to mind
  2117. 1:08:25here I had Simon the founder founder of
  2118. 1:08:27assistant UI here not too long ago and
  2119. 1:08:29he said cloud can get you 80% there
  2120. 1:08:32today but all the alpha is in the
  2121. 1:08:34remaining 20%
  2122. 1:08:35>> and those that 20% determines who gets
  2123. 1:08:38hired.
  2124. 1:08:39>> Yeah. [laughter]
  2125. 1:08:40>> Wonderful. Well, Canal, it's been an
  2126. 1:08:42amazing conversation. Thank you so much
  2127. 1:08:44for taking the time.
  2128. 1:08:45>> This was a lot of fun.
  2129. 1:08:46>> Yeah. I have a a little bit of a a
  2130. 1:08:48ritual that I do with every guest. So, I
  2131. 1:08:49have a couple of rapid fire questions uh
  2132. 1:08:51that I'm going to ask you uh now if
  2133. 1:08:53you're okay with it.
  2134. 1:08:54>> Yeah. Rapid fire.
  2135. 1:08:55>> Yeah. And you can answer them uh either
  2136. 1:08:57short or if you want to expand that's
  2137. 1:08:59also fine. Okay.
  2138. 1:09:00>> Yeah, sure.
  2139. 1:09:01>> All right. Favorite programming
  2140. 1:09:02language?
  2141. 1:09:04>> Golang.
  2142. 1:09:05>> Golang.
  2143. 1:09:05>> Yeah. I just love Golang. Let's just
  2144. 1:09:07keep it there. I don't want to start a
  2145. 1:09:08debate.
  2146. 1:09:08>> Okay.
  2147. 1:09:09>> Actually, shout out to Rust.
  2148. 1:09:10>> Yeah.
  2149. 1:09:11>> Um, shout out to Java also because my
  2150. 1:09:13career started with Java, so it's
  2151. 1:09:14emotional.
  2152. 1:09:15>> Okay. All right. Good. We'll keep it
  2153. 1:09:16there. Uh, favorite AI model.
  2154. 1:09:20>> Fable five.
  2155. 1:09:21>> Favorite five. [laughter]
  2156. 1:09:23>> So good. It's very expensive.
  2157. 1:09:24>> Yeah. But it's good. Um, cool. Uh,
  2158. 1:09:27favorite coding harness?
  2159. 1:09:30>> Cloud.
  2160. 1:09:31>> Cloud. Yeah. Okay. Cloud code.
  2161. 1:09:33>> Cloud code.
  2162. 1:09:34>> Yeah. Like like that. Okay. All right.
  2163. 1:09:36No open code, no nothing like that.
  2164. 1:09:37>> I like cloud code.
  2165. 1:09:38>> Okay, that's fair. I guess if I feel
  2166. 1:09:41like also now that they like obviously
  2167. 1:09:43they train they RL the model on the
  2168. 1:09:45harness so it just gets better and
  2169. 1:09:46better.
  2170. 1:09:47>> I like the cloud community. I think
  2171. 1:09:48that's another thing like the community
  2172. 1:09:50is quite there's a lot lot less noise. I
  2173. 1:09:54would say they just these people are
  2174. 1:09:55just building and shipping.
  2175. 1:09:56>> Where do you connect with the cloud
  2176. 1:09:58community?
  2177. 1:09:59>> Reddit.
  2178. 1:09:59>> Mhm. and uh LinkedIn and there's a lot
  2179. 1:10:03of pe we have seen claude very popular
  2180. 1:10:04in vm make devs so a lot of our users
  2181. 1:10:07when they get stuck somewhere they have
  2182. 1:10:09a question
  2183. 1:10:10>> probably I'm like what are you using
  2184. 1:10:12claude codex is up there as well those
  2185. 1:10:14are the top two
  2186. 1:10:15>> okay what do you do when you don't code
  2187. 1:10:17or or run your business
  2188. 1:10:19>> um
  2189. 1:10:20I'm a foodie
  2190. 1:10:22>> love trying out food
  2191. 1:10:24>> um I'm full-time on desk now so I'm not
  2192. 1:10:26I'm working for myself
  2193. 1:10:28>> um
  2194. 1:10:29>> left my job in June. June was my last.
  2195. 1:10:31>> Okay.
  2196. 1:10:31>> So, I'm like, okay, we are scaling. We
  2197. 1:10:33have close to two 250,000 people now.
  2198. 1:10:36So, I'm like, I'm just going to do my
  2199. 1:10:37own thing.
  2200. 1:10:38>> Yeah.
  2201. 1:10:38>> So, I thought if for someone who thinks
  2202. 1:10:41like, okay, you're doing your own thing,
  2203. 1:10:42you have all the time in the world. Now,
  2204. 1:10:43it's like a full-time. I'm now doing I
  2205. 1:10:45think I'm working more now
  2206. 1:10:46>> than I was before.
  2207. 1:10:48>> Yeah.
  2208. 1:10:48>> Um, but yeah, I am a foodie, so I love
  2209. 1:10:50trying new restaurants,
  2210. 1:10:52>> love shopping.
  2211. 1:10:53>> Yeah.
  2212. 1:10:53>> For silly stuff. Um, just like toys and
  2213. 1:10:56whatnot. Um,
  2214. 1:10:59TV shows, love TV shows, movies. I don't
  2215. 1:11:03go to cinema, but I watch it at home.
  2216. 1:11:05>> Uh, spending time with friends and
  2217. 1:11:07family is something I love quite a lot.
  2218. 1:11:09>> Yeah.
  2219. 1:11:09>> And, um, because I'm traveling a lot,
  2220. 1:11:11anytime I get, I just relax. Uh, I live
  2221. 1:11:14in London, so there's a lot of things to
  2222. 1:11:16do like musicals and I don't drink, so
  2223. 1:11:18not really pub kind of a I know you're
  2224. 1:11:21from Germany. I don't know if you drink,
  2225. 1:11:22but I have a I have German friends and
  2226. 1:11:24>> Yeah. No, we it's part of the culture.
  2227. 1:11:26drink the whole picture and he would not
  2228. 1:11:27get drunk. I'm like, "How are you not,
  2229. 1:11:29dude? How are you not drunk?" [laughter]
  2230. 1:11:30He's like, "It's just beer."
  2231. 1:11:32>> Yeah. Yeah.
  2232. 1:11:32>> Beer doesn't make me drunk, right?
  2233. 1:11:34>> It's water for us at this point.
  2234. 1:11:35>> And I'm like, so I'm like, "If you want
  2235. 1:11:36to get drunk, you have to drink hard
  2236. 1:11:38liquor." He's like, "Yeah, beer I can
  2237. 1:11:39drink as much as I want. I won't get
  2238. 1:11:41drunk." I'm like, "Wow." Super
  2239. 1:11:42>> that. I don't know about that. I don't
  2240. 1:11:43want
  2241. 1:11:44>> Yeah. But he's like, he drank this whole
  2242. 1:11:45picture of beer.
  2243. 1:11:46>> Yeah.
  2244. 1:11:47>> He [laughter] was fine.
  2245. 1:11:48>> Shout out to Daniel.
  2246. 1:11:49>> Yeah.
  2247. 1:11:50>> Uh,
  2248. 1:11:51yeah. Know I'm a foodie and I love uh I
  2249. 1:11:55think My life revolves around my family
  2250. 1:11:57and friends.
  2251. 1:11:58>> Yeah.
  2252. 1:11:58>> So, just spending time with them no
  2253. 1:11:59matter what we do
  2254. 1:12:01>> is what I love. And uh yeah, foodie,
  2255. 1:12:05movies, video games, Call of Duty, um
  2256. 1:12:10running,
  2257. 1:12:11badminton.
  2258. 1:12:12>> Yeah,
  2259. 1:12:13>> shopping.
  2260. 1:12:14>> Nice. That's a lot. Yeah,
  2261. 1:12:16>> that's it. Keeps me busy.
  2262. 1:12:17>> Thanks for sharing that. Uh I think this
  2263. 1:12:19is kind of the last point where I wanted
  2264. 1:12:20to give you the opportunity if you want
  2265. 1:12:22to say anything to the audience here
  2266. 1:12:23that you got coming up. um anything
  2267. 1:12:25people where can people follow you?
  2268. 1:12:27Obviously you got your YouTube channels
  2269. 1:12:28and so on and um yeah that's basically
  2270. 1:12:31it.
  2271. 1:12:32>> Yeah I'll just say two things. The first
  2272. 1:12:34thing I would say is uh go to
  2273. 1:12:35vmakedevs.org
  2274. 1:12:37and uh check out all our events
  2275. 1:12:39hackathons you can sign up and create an
  2276. 1:12:41account. We have built a cool platform.
  2277. 1:12:43we're going to do more cool stuff and if
  2278. 1:12:44you're a company who wants to get your
  2279. 1:12:46tool in the hands of like 200,000
  2280. 1:12:49engineers,
  2281. 1:12:50we have an incredible community and they
  2282. 1:12:52would be more than happy to you know uh
  2283. 1:12:55give you feedback, build with it. Uh the
  2284. 1:12:58third last point I would say is don't
  2285. 1:13:00worry it's going to be fine. That's what
  2286. 1:13:02I would say cuz in the in the end life
  2287. 1:13:05just works out and uh
  2288. 1:13:08don't worry about things that are not in
  2289. 1:13:10your control. AI is coming. AI is
  2290. 1:13:12replacing jobs. AI will replace some
  2291. 1:13:14fields. It's not in your control. Then
  2292. 1:13:16why are you worrying?
  2293. 1:13:17>> Mhm.
  2294. 1:13:18>> You know, I mean it sounds silly.
  2295. 1:13:21>> Yeah.
  2296. 1:13:22>> Someone is losing their job and I'm like
  2297. 1:13:23don't worry,
  2298. 1:13:24>> you know. Can't you can't say that.
  2299. 1:13:26>> But the thing is if something is not in
  2300. 1:13:28your control, what can you do?
  2301. 1:13:30>> But wouldn't you say that like let's say
  2302. 1:13:33I'm I'm we just talked about this and uh
  2303. 1:13:35I feel like we wanted to wrap up and now
  2304. 1:13:37I need to go back into it. Um
  2305. 1:13:39>> go for it.
  2306. 1:13:40>> Yeah. You
  2307. 1:13:43There's always something you can do.
  2308. 1:13:45>> Exactly.
  2309. 1:13:46So if I'm about to like if I'm on the
  2310. 1:13:49verge and I feel like oh my relationship
  2311. 1:13:51at work with my manager is not going so
  2312. 1:13:53well like my performance is apparently
  2313. 1:13:55not looking up so much like
  2314. 1:13:57there need there should be something I
  2315. 1:13:59can do about this like you know go watch
  2316. 1:14:00your tutorials go come to one of your
  2317. 1:14:02hackathons go like get code rabbit to
  2318. 1:14:05review your code so you don't get any
  2319. 1:14:06burn like all these things right so um I
  2320. 1:14:10think that that that there's almost for
  2321. 1:14:12anyone who's trying to who's not
  2322. 1:14:14completely strangled and something or
  2323. 1:14:16maybe works in a huge tech firm where
  2324. 1:14:18they just get cut off. Even then,
  2325. 1:14:19there's something they can do which is
  2326. 1:14:21train yourself up and go look for the
  2327. 1:14:23next opportunity. In fact, if your
  2328. 1:14:25company if you feel like that right now,
  2329. 1:14:26I think I should argue you should be
  2330. 1:14:27proactive and try to get something
  2331. 1:14:29somewhere else already, right?
  2332. 1:14:30>> Yeah. It's it's it's like so life is not
  2333. 1:14:33fair to everyone.
  2334. 1:14:34>> Yeah.
  2335. 1:14:34>> There's always hardships, you get laid
  2336. 1:14:36off
  2337. 1:14:37>> and um sometimes, you know, things are
  2338. 1:14:40not in your control. This is a very
  2339. 1:14:41personal advice. I understand it's very
  2340. 1:14:44hard to follow for a lot of people.
  2341. 1:14:46>> Human beings are wired differently. But
  2342. 1:14:48this is how I am wired.
  2343. 1:14:49>> Okay.
  2344. 1:14:50>> If something is not in my control, it
  2345. 1:14:52does not make me sad.
  2346. 1:14:53>> Mhm.
  2347. 1:14:54>> Worse things could happen to me in my
  2348. 1:14:55life. But if it's not in my control,
  2349. 1:14:57there's no point of worrying.
  2350. 1:14:58>> Yeah.
  2351. 1:14:58>> You know, uh but that's it has taken me
  2352. 1:15:01some time to sort of like but there's
  2353. 1:15:04always something you can do. There's
  2354. 1:15:05always uh people are always looking for
  2355. 1:15:07cool people. So people are always
  2356. 1:15:09looking for good people.
  2357. 1:15:11>> You can always do freelancing. You can
  2358. 1:15:12always upskill yourself. There are
  2359. 1:15:14people getting hired out there. There
  2360. 1:15:17are people getting jobs out there. The
  2361. 1:15:20question is just why are they getting
  2362. 1:15:21hired? Why am I not getting hired? So
  2363. 1:15:23obviously there's one good thing is
  2364. 1:15:25because of all these AI resources, the
  2365. 1:15:28barrier to entry has shrked quite a bit.
  2366. 1:15:30So for you to study, for you to learn,
  2367. 1:15:32for you to research, for you to upskill
  2368. 1:15:33yourself, it's very easy now. I mean you
  2369. 1:15:35have so many options.
  2370. 1:15:36>> So silver lining I would say that's a
  2371. 1:15:39silver lining. But uh if you want my
  2372. 1:15:41personal advice, things that are not in
  2373. 1:15:43your control, don't worry about it. Make
  2374. 1:15:45sure you give your best. I'll give one
  2375. 1:15:46one last example. Let's say John Wick
  2376. 1:15:48has an interview and Spider-Man has an
  2377. 1:15:50interview for the same job.
  2378. 1:15:53>> John Wick is very focused. John Wick is
  2379. 1:15:54spending 100% of his time
  2380. 1:15:56>> preparing for the interview. Spider-Man
  2381. 1:15:59is spending 50% of his time preparing
  2382. 1:16:00for the interview, 50% worrying about,
  2383. 1:16:02oh, what would I do if I don't clear it?
  2384. 1:16:04And let's imagine they both have the
  2385. 1:16:06same intellect.
  2386. 1:16:08>> Who do you think has a higher chance of
  2387. 1:16:09doing
  2388. 1:16:10you know.
  2389. 1:16:10>> Yeah. I mean, you can also o overprepare
  2390. 1:16:13that also happens. But, uh, yeah.
  2391. 1:16:15>> Yeah. Things that are not in your
  2392. 1:16:16control, don't worry. And then, yeah,
  2393. 1:16:17that's it.
  2394. 1:16:18>> Okay. I think we'll leave it at that.
  2395. 1:16:20Thank you so much for coming on the
  2396. 1:16:21show, Canal.
  2397. 1:16:22>> Thanks everyone for tuning in and um,
  2398. 1:16:24yeah, won't be the last time that you
  2399. 1:16:25see us. I think
  2400. 1:16:26>> I will be back. Great.

About this transcript

This page contains the full transcript of Which Skills Will Matter Most for Software Engineers? | Kunal Kushwaha by CodeRabbit, generated from the public captions YouTube serves with the video. The transcript has 15,562 words across 2,400 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.