Personally, I found success in developing projects using the technologies most widely sought after in my area (.NET). I looked at job listings to get a grasp on what employers wanted and went from there. I made sure every project tackled something I was interested in, and from there, I went through cycles of implementing a feature and refining it. I went down every rabbit hole I could, focusing on understanding over progress. There were many days I just read on concepts and took notes rather than code. I did this on two complex, larger projects and learned SO much. I have a CS degree, and though I got a lot out from my education, I probably learned just as much from the above method as in my degree program.
I haven't been able to get a job. I have worked on so many small and useless projects before that thought me a lot but didn't helped me , but since the beginning of this year I've been working on my biggest project yet, which I'm about to release, if it does not help me get job, it may become my job.
In my opinion, tackling problems or goals that a business would need is the way to go for a project. This can be having a project that show cases integrating payment service like stripe and using SQL database to log the orders. The other project can be integrating a email service sent after someone purchases or subscribes to your app. Showcasing these use cases show employers that you have knowledge in a specific use case that would help them.
When I graduated a few years ago, I set out to develop fooyin with a clear goal: to create a Linux music player that could rival (and eventually surpass) foobar2000. Many have been hoping for such a player for nearly two decades, and while some, like DeaDBeeF, have come close, none have fully hit the mark. If nothing else, the past few years have been an incredible learning experience, and I look forward to continuing this journey for many years to come.
00:05 Focus on a targeted approach while showcasing personal projects. 02:11 Build a variety of projects to reinforce learning 04:19 Finish your projects to show commitment and follow-through 06:30 Quality over quantity in personal projects 08:31 Focus on building a standout capstone project for career success. 10:42 Identify problems you want to solve as a developer 12:41 Gaining user base and demonstrating value is crucial for personal projects 14:55 Focus on building a useful, professional, and valuable final project.
You are like a positive backhand across the face when it’s needed most. No BS, nothing sugar coated, and yet I always walk away highly motivated. Thank You 🙏
At this point I don't care, I'm starting a studio and building small projects I can offer for sale. It's a pain in the ass dealing with all these nerds and HR games. Idk I doubt a company is going to want to hire you if you make a mini version of their bigger project. I'm done.
It does seem too cumbersome. Not only does one have to build a million things and know everything, but it seems once you get hired that's when all the politics, dehumanization, and corporate bs starts.
@@milhouse8166 yea build things that solve problems. And freelance if you can do that well you don't need a job. And companies don't want to hire you unless you can pull that off anyway.
I think this is good advice, but there is one thing I have to bring up. Yes, we come up with projects. However, with the number of developers around the world, it's damned difficult to come up with something original. Maybe originality isn't as important as I think it is. But on the other side of the coin, making yet another to-do list app as an example isn't going to make devs stand out.
1. "Maybe originality isn't as important as I think it is" 2. "making yet another to-do list app as an example isn't going to make devs stand out" Both of these are true.
Doing real work (even a few free small projects) will get you way further than toy projects. Built some static sites for businesses for some cred, first 'real' job after I did that was in the eComm space, then jumped to a more serious enterprise software role from there.
I’m building full stack web apps. They are SAAS but hopefully it will teach me enough to get a job. Could projects like that help me get a job one day?
There's a lot that goes into landing that first job, but yeah the personal projects that you build play a key role in helping you break into the industry.
if the developer doesn't know when their project is done, how is someone looking at this project going to know it's not done? "Done" could be "I don't have anything more to learn from this..." Software is never really done. I see so many people stressing about this, but someone perusing your github is really not going to be able to know.
Enterprise software is complex and boring. It relies on complex and scalable infrastructure and architecture. It also requires high quality gatekeeping. That's what difficult about building software. If you build an app that doesn't meet those requirements it can be considered trivial. If you're gonna build a trivial app make it fun and catchy. Build a mini game like Google's jumping dinosour, or an attractiveness rater, or supermarket price comparator. Build something that grabs peoples attention immediatelly and leaves them with a big smile.
I'm building my first python program. Turns out, stretching a single image across multiple monitors isn't a fully solved issue across Linux. Especially when dealing with different DEs and Wayland. I'm pretty excited cause it's just about finished. I have some features that I might add later, but they are kinda extra. But I'm super excited. Already got my next project figured out, which is a program that parses data from wire plumber and pipe wire, so you can assign a permanent identifier number to sinks, sources, and virtual sources. The current issue is that every reboot the number changes, requiring the user to use a janky GUI, or a cli tool and series of commands to change audio settings, which is insane. I have no clue how these will look on a resume. But I'm excited no e the less
I feel like a right numpty now, making programs that fetch cat images from an API and display them as terminal images is as far as I've gotten. That and my lame little TODO CLI program 😂. That's awesome dude. Keep on keeping on. CLI can be a bit intense for the noobs so I'm sure it'll go down well.
Those sound like some fairly practical projects. You can certainly add features to dive further into complexity after that MVP is out. I like that you identified what features are extra.
I’m building an Ecommerce website would that be considered a random project ? ( reason why i went with this is it seemed challenging which it has been lol compared to the regular todo lists and calculator apps)
This video was focused on building impressive portfolio projects. Projects like this are great learning projects that'll help you reinforce what you're learning. They have their use as well.
Can't believe I'm watching Ed Sheeran give advice on learning Software Development. Great content btw
Personally, I found success in developing projects using the technologies most widely sought after in my area (.NET). I looked at job listings to get a grasp on what employers wanted and went from there.
I made sure every project tackled something I was interested in, and from there, I went through cycles of implementing a feature and refining it. I went down every rabbit hole I could, focusing on understanding over progress. There were many days I just read on concepts and took notes rather than code. I did this on two complex, larger projects and learned SO much.
I have a CS degree, and though I got a lot out from my education, I probably learned just as much from the above method as in my degree program.
I haven't been able to get a job. I have worked on so many small and useless projects before that thought me a lot but didn't helped me , but since the beginning of this year I've been working on my biggest project yet, which I'm about to release, if it does not help me get job, it may become my job.
What is it?
@@codeintherough can't speak for buddy above but for me it's game engines. Built a bunch of crappy ones and am now building the final iteration
How do you monetize that?@@logicaestrex2278
In my opinion, tackling problems or goals that a business would need is the way to go for a project. This can be having a project that show cases integrating payment service like stripe and using SQL database to log the orders. The other project can be integrating a email service sent after someone purchases or subscribes to your app. Showcasing these use cases show employers that you have knowledge in a specific use case that would help them.
When I graduated a few years ago, I set out to develop fooyin with a clear goal: to create a Linux music player that could rival (and eventually surpass) foobar2000. Many have been hoping for such a player for nearly two decades, and while some, like DeaDBeeF, have come close, none have fully hit the mark.
If nothing else, the past few years have been an incredible learning experience, and I look forward to continuing this journey for many years to come.
What's so demoralizing for me is grinding away on personal projects while knowing that few if any hiring managers are actually looking at them
Life is difficult, unreliable, hurtful, stressful, and so forth. So the information technology world.
00:05 Focus on a targeted approach while showcasing personal projects.
02:11 Build a variety of projects to reinforce learning
04:19 Finish your projects to show commitment and follow-through
06:30 Quality over quantity in personal projects
08:31 Focus on building a standout capstone project for career success.
10:42 Identify problems you want to solve as a developer
12:41 Gaining user base and demonstrating value is crucial for personal projects
14:55 Focus on building a useful, professional, and valuable final project.
You are like a positive backhand across the face when it’s needed most. No BS, nothing sugar coated, and yet I always walk away highly motivated. Thank You 🙏
As a frequent language- and project-hopper, I appreciate this advice.
At this point I don't care, I'm starting a studio and building small projects I can offer for sale. It's a pain in the ass dealing with all these nerds and HR games. Idk I doubt a company is going to want to hire you if you make a mini version of their bigger project. I'm done.
It does seem too cumbersome. Not only does one have to build a million things and know everything, but it seems once you get hired that's when all the politics, dehumanization, and corporate bs starts.
@@milhouse8166 yea build things that solve problems. And freelance if you can do that well you don't need a job. And companies don't want to hire you unless you can pull that off anyway.
I'd love to help, I like this idea :p do you have a stack in mind?
I think this is good advice, but there is one thing I have to bring up. Yes, we come up with projects. However, with the number of developers around the world, it's damned difficult to come up with something original. Maybe originality isn't as important as I think it is. But on the other side of the coin, making yet another to-do list app as an example isn't going to make devs stand out.
1. "Maybe originality isn't as important as I think it is"
2. "making yet another to-do list app as an example isn't going to make devs stand out"
Both of these are true.
Thank you!
Doing real work (even a few free small projects) will get you way further than toy projects. Built some static sites for businesses for some cred, first 'real' job after I did that was in the eComm space, then jumped to a more serious enterprise software role from there.
Don I did this! Your words are graat encouragement for me to finish it
That's good advice.
I’m building full stack web apps. They are SAAS but hopefully it will teach me enough to get a job. Could projects like that help me get a job one day?
There's a lot that goes into landing that first job, but yeah the personal projects that you build play a key role in helping you break into the industry.
I build project when I see something I'd need. I needed UI test creator for UWP apps so I built it.
A graveyard of projects is fine. 80% of ideas are bad and you know it after giving it some work. It's not a reliable signal.
This is great, thank you! you are really helping me :))
Yo ur a g man, new sub 👍
Cause There Are Almost No Jobs That Will Hire Junior Developers
if the developer doesn't know when their project is done, how is someone looking at this project going to know it's not done? "Done" could be "I don't have anything more to learn from this..." Software is never really done. I see so many people stressing about this, but someone perusing your github is really not going to be able to know.
Really strong thumbna game lately my man
Enterprise software is complex and boring. It relies on complex and scalable infrastructure and architecture. It also requires high quality gatekeeping. That's what difficult about building software. If you build an app that doesn't meet those requirements it can be considered trivial.
If you're gonna build a trivial app make it fun and catchy. Build a mini game like Google's jumping dinosour, or an attractiveness rater, or supermarket price comparator. Build something that grabs peoples attention immediatelly and leaves them with a big smile.
This is definitely some solid advice
this also applies to the game development space
I'm building my first python program. Turns out, stretching a single image across multiple monitors isn't a fully solved issue across Linux. Especially when dealing with different DEs and Wayland. I'm pretty excited cause it's just about finished. I have some features that I might add later, but they are kinda extra. But I'm super excited.
Already got my next project figured out, which is a program that parses data from wire plumber and pipe wire, so you can assign a permanent identifier number to sinks, sources, and virtual sources. The current issue is that every reboot the number changes, requiring the user to use a janky GUI, or a cli tool and series of commands to change audio settings, which is insane.
I have no clue how these will look on a resume. But I'm excited no e the less
I feel like a right numpty now, making programs that fetch cat images from an API and display them as terminal images is as far as I've gotten. That and my lame little TODO CLI program 😂.
That's awesome dude. Keep on keeping on. CLI can be a bit intense for the noobs so I'm sure it'll go down well.
Those sound like some fairly practical projects. You can certainly add features to dive further into complexity after that MVP is out. I like that you identified what features are extra.
@@J_SavedbyGrace_Eph28 Everyone goes through those level or projects initially!
Frontend mentor projects?
What if I build it into a complete SaaS app?
I’m building an Ecommerce website would that be considered a random project ? ( reason why i went with this is it seemed challenging which it has been lol compared to the regular todo lists and calculator apps)
This video was focused on building impressive portfolio projects. Projects like this are great learning projects that'll help you reinforce what you're learning. They have their use as well.
Gold advise. Thank you! 😊
First 🎉🎉
🎉🎉