YouTube2Text

You're Building the Wrong Stuff... — Transcript

by Caleb Curry · 2,675 words · 380 segments · language en · Watch on YouTube

Full transcript

  1. 0:00I encourage newer developers so much
  2. 0:02that they should try to build software
  3. 0:03that solves some real world problem like
  4. 0:06actually building useful software that
  5. 0:09they could get users or eventually
  6. 0:10customers making some money from the
  7. 0:12software. And I think that's really
  8. 0:14valuable advice. Instead of creating
  9. 0:16some calculator app or some to-do list
  10. 0:18or some really basic stuff that's been
  11. 0:20done a thousand times, create something
  12. 0:21that solves a real world problem because
  13. 0:23going through that creative challenge is
  14. 0:26going to help you become a much better
  15. 0:27software developer. However, I'm going
  16. 0:28to go against my typical advice in this
  17. 0:31video and say that there is a time where
  18. 0:33you should build something that nobody
  19. 0:34asked for. Why would I say something
  20. 0:36like this? Well, many of the biggest
  21. 0:39advancements in my skills and my career
  22. 0:42started with software that had no
  23. 0:44specific goal in mind. I just created it
  24. 0:47unprompted for myself. So, there
  25. 0:50definitely is a scenario when you want
  26. 0:51to do this. And there is still
  27. 0:54definitely a scenario where you want to
  28. 0:56build software with a specific goal. I
  29. 0:58do that as well. But I wanted to talk
  30. 1:00about this side specifically in this
  31. 1:01video. The software nobody asked for.
  32. 1:03And while this video is not about AI, I
  33. 1:06did want to mention one thing about it
  34. 1:09because it's going to affect many
  35. 1:11software developers. And that is AI does
  36. 1:14not allow you to just create the same
  37. 1:16features you had to build before much
  38. 1:18easier and much faster. Instead, you're
  39. 1:20going to have to create 10 times as many
  40. 1:22features because AI is going to allow
  41. 1:25you to produce 10 times faster. But what
  42. 1:27management doesn't realize is when you
  43. 1:29have some requirement like that, you're
  44. 1:31not able to spend the time needed to
  45. 1:33truly understand each of those features.
  46. 1:35And as a result, the quality of the
  47. 1:37software is going to go down. So you
  48. 1:39could definitely push back and say,
  49. 1:40"Hey, let's focus. Let's keep the
  50. 1:43feature set clean and understand how
  51. 1:45everything works." However, many people
  52. 1:47in upper management are not going to
  53. 1:48understand that they're just going to
  54. 1:50push features out the door regardless.
  55. 1:52As a result, many developers are feeling
  56. 1:55like they are not learning like they
  57. 1:57used to or that they have to do learning
  58. 1:59now on their own outside of work more
  59. 2:01than they used to have to before. And
  60. 2:03I'm going to propose a solution to where
  61. 2:05you can learn a lot with minimal time
  62. 2:08commitment in as little as an hour a day
  63. 2:11working on something that has no
  64. 2:13external expectation or requirements
  65. 2:16given to you. And I'm going to do this
  66. 2:17by talking about some of the things I
  67. 2:19built for myself. Now, I'm super
  68. 2:20unorganized. Maybe I should have built
  69. 2:22an organization app from the start. That
  70. 2:24would have saved me a lot of effort and
  71. 2:26time. But I didn't do that. So, most of
  72. 2:28this code is nowhere to be found. So,
  73. 2:30you're just going to have to trust me.
  74. 2:31It wasn't until a few years into my
  75. 2:33career, I started saving most of my work
  76. 2:35on GitHub. Before then, it was like,
  77. 2:37yeah, I just kind of deleted it or it
  78. 2:39just disappeared over time. So much of
  79. 2:42this is like early career stuff. And
  80. 2:43then for some of the newer stuff, I do
  81. 2:45still have the code, but I'm not
  82. 2:46actively working on any of these
  83. 2:47projects as I'm just focusing on one big
  84. 2:50project right now. So, it all started
  85. 2:52probably back in high school where I
  86. 2:53built my very first HTML and CSS page.
  87. 2:57Rewind a little bit before this. I tried
  88. 2:59picking up C++, found it to be too
  89. 3:02difficult, probably because I had zero
  90. 3:04attention span and I decided picking up
  91. 3:07a book this thick was the way to start
  92. 3:09learning code. Yeah, that was probably
  93. 3:11not the best way to get started. I have
  94. 3:13since learned my lesson, picked up a
  95. 3:14book probably like HTML and CSS for
  96. 3:16dummies, something of that nature, and I
  97. 3:19put together my first web page. And the
  98. 3:21feeling this gave me was unlike anything
  99. 3:24before. This page, although it was
  100. 3:26atrocious, was probably a bigger
  101. 3:28achievement than if I managed to get
  102. 3:30through any of that C++ book because it
  103. 3:33got me hooked on building software. And
  104. 3:35don't even get me started about the time
  105. 3:37I set up a front end and a backend and I
  106. 3:40managed to get the backend data to show
  107. 3:42up in the front-end web page. That was a
  108. 3:46revelation to me, right? Like I had
  109. 3:47never done anything like that before. Up
  110. 3:48until this point, I was hard coding
  111. 3:50everything in HTML and CSS. And this was
  112. 3:52like very early career. I've gotten a
  113. 3:54little bit better since then. And then
  114. 3:56in my first job, I worked on a little
  115. 3:59project that was not assigned to me. I
  116. 4:01was just dorking around. We worked with
  117. 4:03PTZ cameras, Pantel Zoom, where you
  118. 4:06could move the camera around. And I was
  119. 4:08exploring the documentation for these
  120. 4:10cameras, and I was able to interface
  121. 4:12with their API. [snorts] And I just
  122. 4:14created arrow buttons on a page that
  123. 4:17allowed me to control the visuals of the
  124. 4:19camera. So, moving around the camera
  125. 4:21from my custom application. and I didn't
  126. 4:24have to go through any software provided
  127. 4:25by that camera company or any kind of
  128. 4:28third-party security camera software. It
  129. 4:30was all within my own code. So, that
  130. 4:32wasn't assigned to me, but it was one of
  131. 4:33the best projects for me because I was
  132. 4:35able to learn things at a deeper level.
  133. 4:37And again, it gave me that excitement
  134. 4:39feel. I showed it to my co-orker and
  135. 4:41they were like, "Yo, dude, this is
  136. 4:42actually pretty cool. We could use this
  137. 4:44in some of our custom software." Now,
  138. 4:46looking back, it's pretty basic stuff,
  139. 4:48but at the time, that was really the
  140. 4:50first time I ever did anything like
  141. 4:51that. There's a first time for
  142. 4:53everything. So, I went from my first
  143. 4:55HTML and CSS page to my first backend
  144. 4:58front-end setup to my first API calls
  145. 5:01over the network sending requests to a
  146. 5:03local PTC camera. And something I forgot
  147. 5:06about in this journey is earlier on
  148. 5:08closer to when I was building that HTML
  149. 5:09and CSS web page, I set up a Minecraft
  150. 5:12server. didn't really deal with any
  151. 5:13custom code, but I think that's what got
  152. 5:15me into the web development phase
  153. 5:16because I picked up a book on web
  154. 5:18servers and web development. And that
  155. 5:21got me started with building these web
  156. 5:23pages, but also setting up the Minecraft
  157. 5:26server from my local computer, setting
  158. 5:28up port forwarding, all the networking
  159. 5:30and stuff like that. So, my friends
  160. 5:31could actually join the server. And that
  161. 5:34was all from my machine. I wasn't paying
  162. 5:36for some hosting somewhere. So that was
  163. 5:38probably the big jump into tech where I
  164. 5:41wasn't just playing video games and
  165. 5:43stuff like that. I was actually trying
  166. 5:44to build stuff that other people could
  167. 5:46use. And then a few years ago, I built
  168. 5:47out a cryptocurrency explorer, being
  169. 5:50able to see all the transactions, all of
  170. 5:52the blocks for the blockchain that I was
  171. 5:54using. And this is something that got a
  172. 5:56good amount of users and I would say was
  173. 5:58an overall success and a really big
  174. 6:00learning journey because that was the
  175. 6:02time when I really jumped into the full
  176. 6:05end to end building the front end,
  177. 6:06building the back end, getting
  178. 6:07everything deployed, validating any
  179. 6:09data, keeping things secure, all of the
  180. 6:11stuff that you would concern yourself
  181. 6:13with deploying a real app. Now, that app
  182. 6:16did have a goal in mind. You know, I
  183. 6:17wanted to create a service for people to
  184. 6:19use, but it was of my own doing. It
  185. 6:21wasn't a boss saying, "Hey, here's your
  186. 6:23tasks that you need to complete." So,
  187. 6:25across all of these different projects,
  188. 6:27none of these were assigned to me on a
  189. 6:28ticket. And all of them taught me more
  190. 6:31than any of the projects where I was
  191. 6:32actually assigned tasks to do. And with
  192. 6:34the exception of the explorer and, you
  193. 6:37know, deploying a Minecraft server, I
  194. 6:38didn't have very clear outcomes that I
  195. 6:41wanted to get from it. I just wanted to
  196. 6:43start building something and seeing
  197. 6:45where it went. And then a few years ago,
  198. 6:47I wanted to pick up Rust. And I also
  199. 6:50wanted to get a much deeper
  200. 6:51understanding of cryptocurrency and
  201. 6:53blockchain. Not just using the
  202. 6:54blockchain's API, but actually
  203. 6:56understanding the protocol and how
  204. 6:59things work at a deeper level. So, I
  205. 7:01decided I was going to create my own
  206. 7:02cryptocurrency and blockchain from
  207. 7:04scratch. Now, unfortunately, Currycoin
  208. 7:06did not make it to the mainstream
  209. 7:09cryptocurrencies. I don't even think I
  210. 7:11got to the point where it could be used
  211. 7:13fully. But for the time I did spend
  212. 7:15building this, I learned probably more
  213. 7:17than, you know, months of just dorking
  214. 7:19around with cryptocurrency because every
  215. 7:21single thing I learned was new. It was
  216. 7:23challenging. It was self-initiated and
  217. 7:26way more efficient at learning because I
  218. 7:28was actually motivated to learn those
  219. 7:30things. I wanted to get the software to
  220. 7:32work. So that was a time where I was
  221. 7:34actually up late working on software,
  222. 7:36excited about it, and not avoiding it,
  223. 7:38if that makes sense. It was something I
  224. 7:40looked forward to doing. So, those are
  225. 7:42just some of the examples from what I've
  226. 7:44built. Nothing spectacular, but every
  227. 7:46single one of those gave me skills that
  228. 7:49I didn't pick up working in a normal
  229. 7:52job. At work, you create a feature, you
  230. 7:54ship it, and you move on. You don't get
  231. 7:56to spend as much time as you want to
  232. 7:58learn that feature at the detail you
  233. 8:00want. You know, when I was learning
  234. 8:02about the cryptocurrency stuff, I spent,
  235. 8:04you know, a day or two just researching
  236. 8:06different approaches and different
  237. 8:08structures so that I did things
  238. 8:10correctly. Well, when you have to give a
  239. 8:12daily report of your progress on stuff,
  240. 8:14you can't really do that very easily.
  241. 8:16So, you're often forced to just pick
  242. 8:17something and go with it. So, I think
  243. 8:19both of these approaches are valuable.
  244. 8:21And I don't necessarily think it has to
  245. 8:22be one or the other. Like I mentioned, I
  246. 8:24often encourage beginners to pick up
  247. 8:26projects that they want to get to some
  248. 8:28like real software production level. And
  249. 8:30I still think you should keep that in
  250. 8:32mind when you're building. If you're
  251. 8:34building something for yourself just to
  252. 8:35explore and it starts to turn into a
  253. 8:37real thing, figure out how you can go
  254. 8:39deeper and make it into a real software
  255. 8:41people could use. Because going from
  256. 8:44software that works for one person to
  257. 8:46software that works for many people is a
  258. 8:48skill of its own. and you have to start
  259. 8:50worrying about so many more things that
  260. 8:51you could ignore when the software was
  261. 8:53just for yourself. I mean, you're pretty
  262. 8:55confident you are going to use the
  263. 8:56software as you would expect. But what
  264. 8:58happens when you have other users using
  265. 9:00it? Are they going to break things? Are
  266. 9:02they going to do malicious actions? Do
  267. 9:04you have the security setup that you
  268. 9:06need? The list goes on. So, with this, I
  269. 9:08would encourage not just exploratory
  270. 9:11development, but also developing at a
  271. 9:14depth that you're uncomfortable with. So
  272. 9:16picking a project and continuing to work
  273. 9:18on it, going deeper and deeper or
  274. 9:21creating more features to where you're
  275. 9:23not just creating a shallow version of
  276. 9:25something interesting. You're creating
  277. 9:27something that's actually really deep
  278. 9:28and useful. So for me, I wanted to build
  279. 9:31out the blockchain. I wanted to build
  280. 9:33out the coin. I wanted to understand
  281. 9:35wallets and transferring tokens from one
  282. 9:37key to another. I didn't just want to
  283. 9:39create some cute little thing that
  284. 9:41nobody would really care about. I wanted
  285. 9:42to understand the complete end to end.
  286. 9:44So, if you're looking for portfolio
  287. 9:46projects, try not to get as many on
  288. 9:48there as possible. Instead, get a couple
  289. 9:50on there that are really, really good
  290. 9:52and go a little bit deeper than most
  291. 9:54people would go. That's going to help
  292. 9:55you stand out and show that you actually
  293. 9:57know how to build real production level
  294. 9:59quality software. This doesn't
  295. 10:00necessarily mean you have to build some
  296. 10:02super big software. It could still solve
  297. 10:04a very small problem. You know, building
  298. 10:06an entire blockchain and coin is just
  299. 10:09ridiculously over the top. But you could
  300. 10:11build a plugin for some software that's
  301. 10:14relatively small but very good and very
  302. 10:17useful. Or you could build a mod for a
  303. 10:20video game. Or you could build some
  304. 10:22website that has a certain tool that's
  305. 10:24very valuable. There's a million
  306. 10:26different possibilities of what you
  307. 10:27could build. What I'm saying here is not
  308. 10:29to build big, but to build very high
  309. 10:32quality and go a little bit deeper than
  310. 10:34you would if you were just trying to get
  311. 10:35something out the door, rushing to get
  312. 10:37it on your portfolio. make it your
  313. 10:40project and actually have some pride in
  314. 10:41the work that you build. So for me, I'm
  315. 10:43working on one software right now that
  316. 10:44I've been working on for months, but
  317. 10:46this is like the only thing I'm focusing
  318. 10:48on when it comes to exploratory software
  319. 10:50development is how could I make this
  320. 10:52project better? Because I'm at the point
  321. 10:53where I want to create really good
  322. 10:55software and not create a bunch of
  323. 10:57random stuff. So I'm focusing a lot more
  324. 10:59on the product design, what features it
  325. 11:01should have and which ones should not be
  326. 11:02included. Even things like marketing and
  327. 11:04sales and branding, all of the stuff
  328. 11:06around software development. So, how do
  329. 11:08you know what to build? I have two
  330. 11:10suggestions for this. You can find
  331. 11:12something you're interested in. Maybe
  332. 11:14that's Pokemon cards or Lego sets or
  333. 11:18piano. Or you can find some pain that
  334. 11:22you experience or an issue in some other
  335. 11:25software that you hate. So, if you're
  336. 11:27experiencing some pain in life, maybe
  337. 11:29you can't keep track of your ingredients
  338. 11:32for cooking. and the other apps out
  339. 11:35there the way they do it you just don't
  340. 11:36like. Well, you can solve that by
  341. 11:38creating your own software just for
  342. 11:40yourself. Once it's good enough, then
  343. 11:42you can look about sharing that with
  344. 11:43other people. But to start, just start
  345. 11:46building something that you are either
  346. 11:48interested in or solves a problem you
  347. 11:50face. And that's if you have no idea
  348. 11:52what to build. Some people have more
  349. 11:54ideas than they have coding experience.
  350. 11:56And in that situation, you should
  351. 11:58probably just spend more time learning
  352. 11:59the fundamentals of coding. But if
  353. 12:00you're in the situation where you have
  354. 12:01the coding abilities, but you don't know
  355. 12:03what to do with them because you're not
  356. 12:04being told what to do, go through the
  357. 12:06exercise of actually building something
  358. 12:08unprompted because that creativity is
  359. 12:11actually extremely valuable and is a
  360. 12:12skill many software developers do not
  361. 12:14have. So if you have that ability,
  362. 12:17basically not just coding abilities, but
  363. 12:20the bigger picture of piecing features
  364. 12:22together to create software, that's
  365. 12:24super valuable and it allows you to
  366. 12:26create the coolest stuff. So, those are
  367. 12:28some of my takes, but I want to know
  368. 12:29your opinion. If you have experienced
  369. 12:31this or you're working on anything
  370. 12:33interesting, let me know in the comments
  371. 12:34below. Give this video a thumbs up,
  372. 12:36subscribe, hit the notification bell,
  373. 12:38and I'll see you in the next lesson.
  374. 12:40Also, let me know if you've enjoyed this
  375. 12:41talking style of video. I post them from
  376. 12:44time to time, but it's not something I
  377. 12:46consistently do. So, if you enjoy this
  378. 12:48or tutorial stuff, let me know. Would
  379. 12:51really appreciate your feedback. Thanks.
  380. 12:53I'll see you in the next one.

About this transcript

This page contains the full transcript of You're Building the Wrong Stuff... by Caleb Curry, generated from the public captions YouTube serves with the video. The transcript has 2,675 words across 380 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.