You're Building the Wrong Stuff... — Transcript
Full transcript
- 0:00I encourage newer developers so much
- 0:02that they should try to build software
- 0:03that solves some real world problem like
- 0:06actually building useful software that
- 0:09they could get users or eventually
- 0:10customers making some money from the
- 0:12software. And I think that's really
- 0:14valuable advice. Instead of creating
- 0:16some calculator app or some to-do list
- 0:18or some really basic stuff that's been
- 0:20done a thousand times, create something
- 0:21that solves a real world problem because
- 0:23going through that creative challenge is
- 0:26going to help you become a much better
- 0:27software developer. However, I'm going
- 0:28to go against my typical advice in this
- 0:31video and say that there is a time where
- 0:33you should build something that nobody
- 0:34asked for. Why would I say something
- 0:36like this? Well, many of the biggest
- 0:39advancements in my skills and my career
- 0:42started with software that had no
- 0:44specific goal in mind. I just created it
- 0:47unprompted for myself. So, there
- 0:50definitely is a scenario when you want
- 0:51to do this. And there is still
- 0:54definitely a scenario where you want to
- 0:56build software with a specific goal. I
- 0:58do that as well. But I wanted to talk
- 1:00about this side specifically in this
- 1:01video. The software nobody asked for.
- 1:03And while this video is not about AI, I
- 1:06did want to mention one thing about it
- 1:09because it's going to affect many
- 1:11software developers. And that is AI does
- 1:14not allow you to just create the same
- 1:16features you had to build before much
- 1:18easier and much faster. Instead, you're
- 1:20going to have to create 10 times as many
- 1:22features because AI is going to allow
- 1:25you to produce 10 times faster. But what
- 1:27management doesn't realize is when you
- 1:29have some requirement like that, you're
- 1:31not able to spend the time needed to
- 1:33truly understand each of those features.
- 1:35And as a result, the quality of the
- 1:37software is going to go down. So you
- 1:39could definitely push back and say,
- 1:40"Hey, let's focus. Let's keep the
- 1:43feature set clean and understand how
- 1:45everything works." However, many people
- 1:47in upper management are not going to
- 1:48understand that they're just going to
- 1:50push features out the door regardless.
- 1:52As a result, many developers are feeling
- 1:55like they are not learning like they
- 1:57used to or that they have to do learning
- 1:59now on their own outside of work more
- 2:01than they used to have to before. And
- 2:03I'm going to propose a solution to where
- 2:05you can learn a lot with minimal time
- 2:08commitment in as little as an hour a day
- 2:11working on something that has no
- 2:13external expectation or requirements
- 2:16given to you. And I'm going to do this
- 2:17by talking about some of the things I
- 2:19built for myself. Now, I'm super
- 2:20unorganized. Maybe I should have built
- 2:22an organization app from the start. That
- 2:24would have saved me a lot of effort and
- 2:26time. But I didn't do that. So, most of
- 2:28this code is nowhere to be found. So,
- 2:30you're just going to have to trust me.
- 2:31It wasn't until a few years into my
- 2:33career, I started saving most of my work
- 2:35on GitHub. Before then, it was like,
- 2:37yeah, I just kind of deleted it or it
- 2:39just disappeared over time. So much of
- 2:42this is like early career stuff. And
- 2:43then for some of the newer stuff, I do
- 2:45still have the code, but I'm not
- 2:46actively working on any of these
- 2:47projects as I'm just focusing on one big
- 2:50project right now. So, it all started
- 2:52probably back in high school where I
- 2:53built my very first HTML and CSS page.
- 2:57Rewind a little bit before this. I tried
- 2:59picking up C++, found it to be too
- 3:02difficult, probably because I had zero
- 3:04attention span and I decided picking up
- 3:07a book this thick was the way to start
- 3:09learning code. Yeah, that was probably
- 3:11not the best way to get started. I have
- 3:13since learned my lesson, picked up a
- 3:14book probably like HTML and CSS for
- 3:16dummies, something of that nature, and I
- 3:19put together my first web page. And the
- 3:21feeling this gave me was unlike anything
- 3:24before. This page, although it was
- 3:26atrocious, was probably a bigger
- 3:28achievement than if I managed to get
- 3:30through any of that C++ book because it
- 3:33got me hooked on building software. And
- 3:35don't even get me started about the time
- 3:37I set up a front end and a backend and I
- 3:40managed to get the backend data to show
- 3:42up in the front-end web page. That was a
- 3:46revelation to me, right? Like I had
- 3:47never done anything like that before. Up
- 3:48until this point, I was hard coding
- 3:50everything in HTML and CSS. And this was
- 3:52like very early career. I've gotten a
- 3:54little bit better since then. And then
- 3:56in my first job, I worked on a little
- 3:59project that was not assigned to me. I
- 4:01was just dorking around. We worked with
- 4:03PTZ cameras, Pantel Zoom, where you
- 4:06could move the camera around. And I was
- 4:08exploring the documentation for these
- 4:10cameras, and I was able to interface
- 4:12with their API. [snorts] And I just
- 4:14created arrow buttons on a page that
- 4:17allowed me to control the visuals of the
- 4:19camera. So, moving around the camera
- 4:21from my custom application. and I didn't
- 4:24have to go through any software provided
- 4:25by that camera company or any kind of
- 4:28third-party security camera software. It
- 4:30was all within my own code. So, that
- 4:32wasn't assigned to me, but it was one of
- 4:33the best projects for me because I was
- 4:35able to learn things at a deeper level.
- 4:37And again, it gave me that excitement
- 4:39feel. I showed it to my co-orker and
- 4:41they were like, "Yo, dude, this is
- 4:42actually pretty cool. We could use this
- 4:44in some of our custom software." Now,
- 4:46looking back, it's pretty basic stuff,
- 4:48but at the time, that was really the
- 4:50first time I ever did anything like
- 4:51that. There's a first time for
- 4:53everything. So, I went from my first
- 4:55HTML and CSS page to my first backend
- 4:58front-end setup to my first API calls
- 5:01over the network sending requests to a
- 5:03local PTC camera. And something I forgot
- 5:06about in this journey is earlier on
- 5:08closer to when I was building that HTML
- 5:09and CSS web page, I set up a Minecraft
- 5:12server. didn't really deal with any
- 5:13custom code, but I think that's what got
- 5:15me into the web development phase
- 5:16because I picked up a book on web
- 5:18servers and web development. And that
- 5:21got me started with building these web
- 5:23pages, but also setting up the Minecraft
- 5:26server from my local computer, setting
- 5:28up port forwarding, all the networking
- 5:30and stuff like that. So, my friends
- 5:31could actually join the server. And that
- 5:34was all from my machine. I wasn't paying
- 5:36for some hosting somewhere. So that was
- 5:38probably the big jump into tech where I
- 5:41wasn't just playing video games and
- 5:43stuff like that. I was actually trying
- 5:44to build stuff that other people could
- 5:46use. And then a few years ago, I built
- 5:47out a cryptocurrency explorer, being
- 5:50able to see all the transactions, all of
- 5:52the blocks for the blockchain that I was
- 5:54using. And this is something that got a
- 5:56good amount of users and I would say was
- 5:58an overall success and a really big
- 6:00learning journey because that was the
- 6:02time when I really jumped into the full
- 6:05end to end building the front end,
- 6:06building the back end, getting
- 6:07everything deployed, validating any
- 6:09data, keeping things secure, all of the
- 6:11stuff that you would concern yourself
- 6:13with deploying a real app. Now, that app
- 6:16did have a goal in mind. You know, I
- 6:17wanted to create a service for people to
- 6:19use, but it was of my own doing. It
- 6:21wasn't a boss saying, "Hey, here's your
- 6:23tasks that you need to complete." So,
- 6:25across all of these different projects,
- 6:27none of these were assigned to me on a
- 6:28ticket. And all of them taught me more
- 6:31than any of the projects where I was
- 6:32actually assigned tasks to do. And with
- 6:34the exception of the explorer and, you
- 6:37know, deploying a Minecraft server, I
- 6:38didn't have very clear outcomes that I
- 6:41wanted to get from it. I just wanted to
- 6:43start building something and seeing
- 6:45where it went. And then a few years ago,
- 6:47I wanted to pick up Rust. And I also
- 6:50wanted to get a much deeper
- 6:51understanding of cryptocurrency and
- 6:53blockchain. Not just using the
- 6:54blockchain's API, but actually
- 6:56understanding the protocol and how
- 6:59things work at a deeper level. So, I
- 7:01decided I was going to create my own
- 7:02cryptocurrency and blockchain from
- 7:04scratch. Now, unfortunately, Currycoin
- 7:06did not make it to the mainstream
- 7:09cryptocurrencies. I don't even think I
- 7:11got to the point where it could be used
- 7:13fully. But for the time I did spend
- 7:15building this, I learned probably more
- 7:17than, you know, months of just dorking
- 7:19around with cryptocurrency because every
- 7:21single thing I learned was new. It was
- 7:23challenging. It was self-initiated and
- 7:26way more efficient at learning because I
- 7:28was actually motivated to learn those
- 7:30things. I wanted to get the software to
- 7:32work. So that was a time where I was
- 7:34actually up late working on software,
- 7:36excited about it, and not avoiding it,
- 7:38if that makes sense. It was something I
- 7:40looked forward to doing. So, those are
- 7:42just some of the examples from what I've
- 7:44built. Nothing spectacular, but every
- 7:46single one of those gave me skills that
- 7:49I didn't pick up working in a normal
- 7:52job. At work, you create a feature, you
- 7:54ship it, and you move on. You don't get
- 7:56to spend as much time as you want to
- 7:58learn that feature at the detail you
- 8:00want. You know, when I was learning
- 8:02about the cryptocurrency stuff, I spent,
- 8:04you know, a day or two just researching
- 8:06different approaches and different
- 8:08structures so that I did things
- 8:10correctly. Well, when you have to give a
- 8:12daily report of your progress on stuff,
- 8:14you can't really do that very easily.
- 8:16So, you're often forced to just pick
- 8:17something and go with it. So, I think
- 8:19both of these approaches are valuable.
- 8:21And I don't necessarily think it has to
- 8:22be one or the other. Like I mentioned, I
- 8:24often encourage beginners to pick up
- 8:26projects that they want to get to some
- 8:28like real software production level. And
- 8:30I still think you should keep that in
- 8:32mind when you're building. If you're
- 8:34building something for yourself just to
- 8:35explore and it starts to turn into a
- 8:37real thing, figure out how you can go
- 8:39deeper and make it into a real software
- 8:41people could use. Because going from
- 8:44software that works for one person to
- 8:46software that works for many people is a
- 8:48skill of its own. and you have to start
- 8:50worrying about so many more things that
- 8:51you could ignore when the software was
- 8:53just for yourself. I mean, you're pretty
- 8:55confident you are going to use the
- 8:56software as you would expect. But what
- 8:58happens when you have other users using
- 9:00it? Are they going to break things? Are
- 9:02they going to do malicious actions? Do
- 9:04you have the security setup that you
- 9:06need? The list goes on. So, with this, I
- 9:08would encourage not just exploratory
- 9:11development, but also developing at a
- 9:14depth that you're uncomfortable with. So
- 9:16picking a project and continuing to work
- 9:18on it, going deeper and deeper or
- 9:21creating more features to where you're
- 9:23not just creating a shallow version of
- 9:25something interesting. You're creating
- 9:27something that's actually really deep
- 9:28and useful. So for me, I wanted to build
- 9:31out the blockchain. I wanted to build
- 9:33out the coin. I wanted to understand
- 9:35wallets and transferring tokens from one
- 9:37key to another. I didn't just want to
- 9:39create some cute little thing that
- 9:41nobody would really care about. I wanted
- 9:42to understand the complete end to end.
- 9:44So, if you're looking for portfolio
- 9:46projects, try not to get as many on
- 9:48there as possible. Instead, get a couple
- 9:50on there that are really, really good
- 9:52and go a little bit deeper than most
- 9:54people would go. That's going to help
- 9:55you stand out and show that you actually
- 9:57know how to build real production level
- 9:59quality software. This doesn't
- 10:00necessarily mean you have to build some
- 10:02super big software. It could still solve
- 10:04a very small problem. You know, building
- 10:06an entire blockchain and coin is just
- 10:09ridiculously over the top. But you could
- 10:11build a plugin for some software that's
- 10:14relatively small but very good and very
- 10:17useful. Or you could build a mod for a
- 10:20video game. Or you could build some
- 10:22website that has a certain tool that's
- 10:24very valuable. There's a million
- 10:26different possibilities of what you
- 10:27could build. What I'm saying here is not
- 10:29to build big, but to build very high
- 10:32quality and go a little bit deeper than
- 10:34you would if you were just trying to get
- 10:35something out the door, rushing to get
- 10:37it on your portfolio. make it your
- 10:40project and actually have some pride in
- 10:41the work that you build. So for me, I'm
- 10:43working on one software right now that
- 10:44I've been working on for months, but
- 10:46this is like the only thing I'm focusing
- 10:48on when it comes to exploratory software
- 10:50development is how could I make this
- 10:52project better? Because I'm at the point
- 10:53where I want to create really good
- 10:55software and not create a bunch of
- 10:57random stuff. So I'm focusing a lot more
- 10:59on the product design, what features it
- 11:01should have and which ones should not be
- 11:02included. Even things like marketing and
- 11:04sales and branding, all of the stuff
- 11:06around software development. So, how do
- 11:08you know what to build? I have two
- 11:10suggestions for this. You can find
- 11:12something you're interested in. Maybe
- 11:14that's Pokemon cards or Lego sets or
- 11:18piano. Or you can find some pain that
- 11:22you experience or an issue in some other
- 11:25software that you hate. So, if you're
- 11:27experiencing some pain in life, maybe
- 11:29you can't keep track of your ingredients
- 11:32for cooking. and the other apps out
- 11:35there the way they do it you just don't
- 11:36like. Well, you can solve that by
- 11:38creating your own software just for
- 11:40yourself. Once it's good enough, then
- 11:42you can look about sharing that with
- 11:43other people. But to start, just start
- 11:46building something that you are either
- 11:48interested in or solves a problem you
- 11:50face. And that's if you have no idea
- 11:52what to build. Some people have more
- 11:54ideas than they have coding experience.
- 11:56And in that situation, you should
- 11:58probably just spend more time learning
- 11:59the fundamentals of coding. But if
- 12:00you're in the situation where you have
- 12:01the coding abilities, but you don't know
- 12:03what to do with them because you're not
- 12:04being told what to do, go through the
- 12:06exercise of actually building something
- 12:08unprompted because that creativity is
- 12:11actually extremely valuable and is a
- 12:12skill many software developers do not
- 12:14have. So if you have that ability,
- 12:17basically not just coding abilities, but
- 12:20the bigger picture of piecing features
- 12:22together to create software, that's
- 12:24super valuable and it allows you to
- 12:26create the coolest stuff. So, those are
- 12:28some of my takes, but I want to know
- 12:29your opinion. If you have experienced
- 12:31this or you're working on anything
- 12:33interesting, let me know in the comments
- 12:34below. Give this video a thumbs up,
- 12:36subscribe, hit the notification bell,
- 12:38and I'll see you in the next lesson.
- 12:40Also, let me know if you've enjoyed this
- 12:41talking style of video. I post them from
- 12:44time to time, but it's not something I
- 12:46consistently do. So, if you enjoy this
- 12:48or tutorial stuff, let me know. Would
- 12:51really appreciate your feedback. Thanks.
- 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.