Great video; I wholeheartedly agree. I enjoy my job, but after work I want to spend time with family and friends and pursue hobbies that keep me physically active.
Building your personal projects before landing a job helps you sharpen your skills instead of just doing nothing, and if you have an idea that have prospect or can solve a valid problem don't stop working on it even after you've successfully secured a role in the industry. You just don't know where that project might get you to. The only challenge with building a project while on a job is possibility of getting burnt out but if you can find the balance then go for it and make sure it is worth it, and try as much as possible to build projects that offers real world solutions.
Hi Brian, thanks for this video. It's definitely among the most realistic video I've seen in a long time. Developers don't need to be developing stuff 16 hours a day. 8 hours at work, another X number of hours outside of work. Personally, I don't see anything wrong with learning new stuff outside of work. However, there has to be a balance. By balance, I mean don't let your job completely dominate your life outside of work.
Thank you for this. This is such an eye opener. TBH, the biggest take away for me with this is the quote 'Everything You Do Should Serve A Purpose'. Before I work on ANYTHING! I will remember this quote for the rest of my life - it is soooooooo liberating. Thank you all the way from London.
Do as many projects as necessary to get hired and get better at what you do. Stuff that emphasizes the basics. After getting the job or several jobs, the only use for personal projects is something to do. Is that a good summary?
My situation is that I'm at my 1st developer job after completing a apprenticeship with them & am now doing a degree apprenticeship with with them. Do you think I need personal projects for when I start job hunting to move to another company even though I have 4+ years of dev experience as a Java Dev based in the UK. 🇬🇧
@@Emperor-Inker As someone senior who is also in UK then no, 4 years should be enough, focus on what you have coded there. Main thing is communicating it well to not sell yourself short.
I appreciate your insight. This is an opinion that I’ve never heard, before. Still, I’ll have to land my first role to be able to adopt this mindset. 👍🏾
I agree that learning framework X to build a personal project might be a waste of time. But the more senior you become, the more things you are required to understand deeply. It's hard to get that understanding just by reading a book and watching a UA-cam video. Building a web server/WS chat/Database/OS from scratch using only a standard library is a much better way. You will have to read theory along the way because you can't reinvent 30-40 years' worth of research in whatever area you are trying to build. But complex topics suddenly become understandable, and you no longer need to memorize any concepts of the library/framework/technology you use. You just understand them.
I don't really know what to say. There are some truth to what you said, but we don't do personal projects to please anyone. Personal projects help improve skills. The only thing I agree with you 💯 is that personal projects shouldn't take priorities over family life.
Well yes, you got into coding not because you intrinsically love it, but because it is just a job for you, it is perfectly logical that you would not want to spend your personal time on it.
You are getting the whole idea of personal projects wrong. It is about the joy of learning new things, doing something different than in your day job, extending your horizon... They are not to get you hired, this is the wrong motivation.
there a lot of people that do software engineer just for the money it isn't their passion. he is well spoken so he will probably move into management so he going to do fine
My personal projects did get me hired for my first few jobs, but he's right; recruiters these days are more interested in the time I spent in IBM. I do work on personal projects but only because it's fun for me. They're not gonna get me hired any more.
I think that you forgot to highlight that personal projects could possibly be a source of passive income. I agree that you should stop doing personal projects if you're not working through production or trying to fill something on your resume.
That's an interesting perspective. Personally I don't agree. Although it's true that personal projects are really helpful to have something to show or to talk about to get your first job I think they really useful after that. In my case is a way to code and create something thats not decided by what I am asked to do at my job (I enjoy creating things) or neither limited by the restrictions (from a business or technical point of view) at work. Another use is when I learn something new, it may not be applicable on my current job but it could be useful to get my next job. Even if it was possible to use what I learned on my job, there in some cases is better to work with something that I already mastered instead of what I'm still learning cause I need to deliver the features I've been asked. So for those cases I consider personal projects could be really useful.
I like the idea of building 'features' I've never built rather than another full stack C.R.U.D. app. For example, I have a working knowledge of React Native but I've never built an login system that uses facebook auth. So guess what I'm learning?
Honestly the best engineers I know just keep doing projects, learning new stuff, regardless of that paying or not... Of course avoid frameworks that are pointless toward overall progression
You were doing personal projects wrong. Sure, in the beginning of your career you can use them to get better at your job, but that shouldn't be your main focus otherwise they become a chore. Personal projects are about building fun stuff that you WANT to build, not for creating a portfolio and to improve your resume. Right now I'm building a chat app on Delphi 1 for Windows 3.11. That does nothing for my career, but I'm learning something that I find amusing and I'm having a blast doing it. And I can share that later with other retro enthusiasts, which is a plus. Now, of course, coding is my day job and also one of my hobbies and maybe coding is not a hobby for you. And that's okay, do something else that you love, play an instrument, do a sport, I don't know. But don't do personal projects just for the sake of getting more employable.
But it should be your main focus before you can get your next job by only talking about your work experience. How else will a beginner get more employable if you don't do personal projects?
3:00 If you're a master in "vanillaJS" you allready have your own foundation that you use to build something fast, dropping it just to jump on some hype-bandwagon makes me question that persons mastery, and in case of angular, we all know how that worked out with v1.
Hey Brian , I just watched your video and I must say that it was really informative and well-made. I was wondering if I could help you edit your highly engaging videos and thumbnails which will help your video to reach to a wider audience and increase your subscribers and viewers. Can we discuss about it?
Python in my honest opinion. Though after learning a bit of that, I realized it was just using C anyway, so I tried learning as much of that as necessary to understand what was happening. I didn't get far, but I'm coming back to it later. Also while not a coding language, SQL is super basic for databases.
The easiest programming language to learn is BASIC. It won't get you a job, but it will make other programming languages easier to learn because you figured out how to think like a programmer. For modern programming languages, Javascript or Python. Both of these languages can be used to develop command-line and web applications.
Great video; I wholeheartedly agree. I enjoy my job, but after work I want to spend time with family and friends and pursue hobbies that keep me physically active.
Building your personal projects before landing a job helps you sharpen your skills instead of just doing nothing, and if you have an idea that have prospect or can solve a valid problem don't stop working on it even after you've successfully secured a role in the industry. You just don't know where that project might get you to. The only challenge with building a project while on a job is possibility of getting burnt out but if you can find the balance then go for it and make sure it is worth it, and try as much as possible to build projects that offers real world solutions.
Hi Brian, thanks for this video. It's definitely among the most realistic video I've seen in a long time. Developers don't need to be developing stuff 16 hours a day. 8 hours at work, another X number of hours outside of work. Personally, I don't see anything wrong with learning new stuff outside of work. However, there has to be a balance. By balance, I mean don't let your job completely dominate your life outside of work.
Thank you for this. This is such an eye opener. TBH, the biggest take away for me with this is the quote 'Everything You Do Should Serve A Purpose'. Before I work on ANYTHING! I will remember this quote for the rest of my life - it is soooooooo liberating. Thank you all the way from London.
Do as many projects as necessary to get hired and get better at what you do. Stuff that emphasizes the basics. After getting the job or several jobs, the only use for personal projects is something to do. Is that a good summary?
That's right!
My situation is that I'm at my 1st developer job after completing a apprenticeship with them & am now doing a degree apprenticeship with with them. Do you think I need personal projects for when I start job hunting to move to another company even though I have 4+ years of dev experience as a Java Dev based in the UK. 🇬🇧
@@Emperor-Inker As someone senior who is also in UK then no, 4 years should be enough, focus on what you have coded there. Main thing is communicating it well to not sell yourself short.
Great video big fella!!!!
Thanks for sharing. I'll keep this in mind after I get my first job
I have an exact copy of your shirt, it feels so comfortable.
I appreciate your insight. This is an opinion that I’ve never heard, before.
Still, I’ll have to land my first role to be able to adopt this mindset.
👍🏾
creating projects is great to keep up with your skillset
I agree that learning framework X to build a personal project might be a waste of time. But the more senior you become, the more things you are required to understand deeply.
It's hard to get that understanding just by reading a book and watching a UA-cam video. Building a web server/WS chat/Database/OS from scratch using only a standard library is a much better way.
You will have to read theory along the way because you can't reinvent 30-40 years' worth of research in whatever area you are trying to build. But complex topics suddenly become understandable, and you no longer need to memorize any concepts of the library/framework/technology you use. You just understand them.
I don't really know what to say. There are some truth to what you said, but we don't do personal projects to please anyone. Personal projects help improve skills. The only thing I agree with you 💯 is that personal projects shouldn't take priorities over family life.
Well yes, you got into coding not because you intrinsically love it, but because it is just a job for you, it is perfectly logical that you would not want to spend your personal time on it.
Wuooo !!! Super Excelent info, Really thanks !!!!
Good philosophy of life that places programming within the greater context.
You are getting the whole idea of personal projects wrong. It is about the joy of learning new things, doing something different than in your day job, extending your horizon...
They are not to get you hired, this is the wrong motivation.
nerd
there a lot of people that do software engineer just for the money it isn't their passion. he is well spoken so he will probably move into management so he going to do fine
My personal projects did get me hired for my first few jobs, but he's right; recruiters these days are more interested in the time I spent in IBM.
I do work on personal projects but only because it's fun for me. They're not gonna get me hired any more.
This actually looks like practical advice compared to what I see on other youtube videos of software developers, where is the subscribe button?
I think that you forgot to highlight that personal projects could possibly be a source of passive income. I agree that you should stop doing personal projects if you're not working through production or trying to fill something on your resume.
That's an interesting perspective. Personally I don't agree. Although it's true that personal projects are really helpful to have something to show or to talk about to get your first job I think they really useful after that. In my case is a way to code and create something thats not decided by what I am asked to do at my job (I enjoy creating things) or neither limited by the restrictions (from a business or technical point of view) at work. Another use is when I learn something new, it may not be applicable on my current job but it could be useful to get my next job. Even if it was possible to use what I learned on my job, there in some cases is better to work with something that I already mastered instead of what I'm still learning cause I need to deliver the features I've been asked. So for those cases I consider personal projects could be really useful.
Can do a video on what it is like to work on real life projects , what exact additional technical skills do u earn as you grow
If you want to be a cubicle drone farm animal like this dude...... don't work on personal projects......
can you please share your original resume that had projects on it?
I like the idea of building 'features' I've never built rather than another full stack C.R.U.D. app. For example, I have a working knowledge of React Native but I've never built an login system that uses facebook auth. So guess what I'm learning?
The secret is to continually improve coding. You doing wrong
Honestly the best engineers I know just keep doing projects, learning new stuff, regardless of that paying or not... Of course avoid frameworks that are pointless toward overall progression
@@zhaohan_dong👍
You were doing personal projects wrong. Sure, in the beginning of your career you can use them to get better at your job, but that shouldn't be your main focus otherwise they become a chore.
Personal projects are about building fun stuff that you WANT to build, not for creating a portfolio and to improve your resume.
Right now I'm building a chat app on Delphi 1 for Windows 3.11. That does nothing for my career, but I'm learning something that I find amusing and I'm having a blast doing it.
And I can share that later with other retro enthusiasts, which is a plus.
Now, of course, coding is my day job and also one of my hobbies and maybe coding is not a hobby for you. And that's okay, do something else that you love, play an instrument, do a sport, I don't know.
But don't do personal projects just for the sake of getting more employable.
But it should be your main focus before you can get your next job by only talking about your work experience. How else will a beginner get more employable if you don't do personal projects?
UA-cam was a side project🙄
That's on you
And no one cares
If u have a project to accomplish do it
In the end u chose what you chose
Dam as
3:00 If you're a master in "vanillaJS" you allready have your own foundation that you use to build something fast, dropping it just to jump on some hype-bandwagon makes me question that persons mastery, and in case of angular, we all know how that worked out with v1.
Hey Brian , I just watched your video and I must say that it was really informative and well-made. I was wondering if I could help you edit your highly engaging videos and thumbnails which will help your video to reach to a wider audience and increase your subscribers and viewers. Can we discuss about it?
Coding is confusing. 😂 What's the easiest programming language to learn as a beginner?
Python in my honest opinion. Though after learning a bit of that, I realized it was just using C anyway, so I tried learning as much of that as necessary to understand what was happening. I didn't get far, but I'm coming back to it later.
Also while not a coding language, SQL is super basic for databases.
JavaScript or Python imo. Would give you the most flexibility and plenty of resources to learn them.
Python is number 1,followed by Javascript
Haskell
The easiest programming language to learn is BASIC. It won't get you a job, but it will make other programming languages easier to learn because you figured out how to think like a programmer.
For modern programming languages, Javascript or Python. Both of these languages can be used to develop command-line and web applications.
AI will replace web developers very first
It will replace all copy'n'paste Jobs 🤡
@@Noname-bg8sh copy paste jobs will be in high demand as they are the one who copies from chatgpt like apps and paste in the vscode😄