Related to these but slightly different: You can make money building databases and reports. This entails gathering data for companies that have it all over the place (in spreadsheets, text files, and documents, both online and printed), migrating everything to a fully organized database. Once data are gathered, you can offer reporting using whatever tool they have bought or want to buy. One caveat to this: It is often viewed by SOME in the company as a threat to their livelihood, especially if their job entails gathering information and generating reports manually, so you have to tread lightly.
Thank you so much for the amazing videos Tim. This is not a side hustle, but I took the liberty to get the timestamps for your video. You can just copy paste these. I'd donate if I could, but since I am not able to, here's my contribution: 00:40 - Freelance Development 02:02 - Tool Building and Plugins 05:00 - Blog Post Writing 07:54 - Competition Participation 09:47 - Open Source Contributions 12:24 - Volunteering for a non-profit 14:31 - Building a Full Software Solution 17:02 - Building Mobile Apps 26:00 - Build Small Games 28:20 - Create Useful Nuget Packages 28:55 - Create a Template Website Setup 32:48 - Consultation
This open source thing is crazy. Imagine expecting people to work for free until the thing is good enough to monetize and then flipping all the contributors the bird. (This isn't aimed at you, just something I keep seeing in open source these days).
I think this is missing a key perspective - the goal of open-source maintainers is practically never to make money off of their project. It isn't a bait-and-switch. Instead, what happens is that people expect the maintainers to continue working on and pushing the project forward for free. If you notice, that happens for years. Then, the maintainer gets tired. They want out, but they don't want to let down the community. So, they say something along the lines of "hey, if I could make this my job, I'd be motivated to work on it." They give the community years of free support, then get hate when they don't give more. Here's why I don't see your perspective as accurate - If it was the case that there were contributors who were working on the project that still wanted the library to be free, they could fork the project and keep it free. That practically never happens. Projects that are critical will die if their primary maintainer walks away because there is almost never a person or group that wants to step up to fill the gap. Even the times where people say the will step up, the failure rate of those transitions is fairly high. People don't realize how much work goes into maintaining a project. It isn't just accepting pull requests all day. In fact, every pull request that you accept is more dangerous than the last. Every time someone builds a feature for you "for free", you end up being the one that has to maintain that feature in perpetuity. It's like me offering to plant seeds in your garden. People pat me on the back for my contribution to your garden, but you are the one stuck weeding, cultivating, protecting, and harvesting the results. My ten minutes of contribution led to dozens of hours of work for you. At the end of the day, why does anyone else have a say about what an open-source maintainer does with their project? What gives anyone else the right? They don't own the work. Even if they contributed, that was their choice. The owner owns the project. They created it. They get to say what is done with it. If the license is truly open source, you can fork the project and do what you want with it because now you own that copy. People shouldn't be chained to their work or forced to work for free just because they gave the community years of their life already.
Good content as usual Tim! Watching the rest as I type this. On #1, this may not be immediately apparent to devs who haven't already gone through this, but plan ahead of time how to say "no" if the thing somebody wants you to build for them is: 1) Way too ambitious 2) Glorified IT / networking / fix my computer tech work (this drives me nuts) 3) Not in your wheelhouse (not your framework, language, etc.) 4) Not worth your time or effort, or maybe your plate is already too full 5) They're not offering enough compensation Don't get talked into doing something you don't want to do. Sometimes the reality is people just can't afford you, and that's okay. You're not obligated to build things for people if you're not 100% comfortable doing it.
I'd love to do software development side hustle on top of my full-time developer job, but I have no idea where to find a project. Perhaps a topic for another video?
I'm not sure what you are asking for. This video has 12 ideas for what to do. If you are looking for what app to build, find a pain point that you have and solve it.
Ahhh apologies! The comment was intended for the previous video of yours "value of side hustle". I didn't realize this video exists which is exactly what I was looking for!
![[DOKKAN BATTLE] Worldwide Campaign Announcement Video Part 2!](http://i.ytimg.com/vi/JpT5Voak6WA/mqdefault.jpg)
Related to these but slightly different: You can make money building databases and reports. This entails gathering data for companies that have it all over the place (in spreadsheets, text files, and documents, both online and printed), migrating everything to a fully organized database. Once data are gathered, you can offer reporting using whatever tool they have bought or want to buy. One caveat to this: It is often viewed by SOME in the company as a threat to their livelihood, especially if their job entails gathering information and generating reports manually, so you have to tread lightly.
Thank you so much for the amazing videos Tim. This is not a side hustle, but I took the liberty to get the timestamps for your video. You can just copy paste these. I'd donate if I could, but since I am not able to, here's my contribution:
00:40 - Freelance Development
02:02 - Tool Building and Plugins
05:00 - Blog Post Writing
07:54 - Competition Participation
09:47 - Open Source Contributions
12:24 - Volunteering for a non-profit
14:31 - Building a Full Software Solution
17:02 - Building Mobile Apps
26:00 - Build Small Games
28:20 - Create Useful Nuget Packages
28:55 - Create a Template Website Setup
32:48 - Consultation
Thanks! I added these to the description so that the video has chapters. This is really helpful.
@@IAmTimCorey thank you for the awesome content ❤
pleasee puutt timee stampsssssssssssssssssssss
Agree
This open source thing is crazy. Imagine expecting people to work for free until the thing is good enough to monetize and then flipping all the contributors the bird. (This isn't aimed at you, just something I keep seeing in open source these days).
I think this is missing a key perspective - the goal of open-source maintainers is practically never to make money off of their project. It isn't a bait-and-switch. Instead, what happens is that people expect the maintainers to continue working on and pushing the project forward for free. If you notice, that happens for years. Then, the maintainer gets tired. They want out, but they don't want to let down the community. So, they say something along the lines of "hey, if I could make this my job, I'd be motivated to work on it." They give the community years of free support, then get hate when they don't give more.
Here's why I don't see your perspective as accurate - If it was the case that there were contributors who were working on the project that still wanted the library to be free, they could fork the project and keep it free. That practically never happens. Projects that are critical will die if their primary maintainer walks away because there is almost never a person or group that wants to step up to fill the gap. Even the times where people say the will step up, the failure rate of those transitions is fairly high. People don't realize how much work goes into maintaining a project. It isn't just accepting pull requests all day. In fact, every pull request that you accept is more dangerous than the last. Every time someone builds a feature for you "for free", you end up being the one that has to maintain that feature in perpetuity. It's like me offering to plant seeds in your garden. People pat me on the back for my contribution to your garden, but you are the one stuck weeding, cultivating, protecting, and harvesting the results. My ten minutes of contribution led to dozens of hours of work for you.
At the end of the day, why does anyone else have a say about what an open-source maintainer does with their project? What gives anyone else the right? They don't own the work. Even if they contributed, that was their choice. The owner owns the project. They created it. They get to say what is done with it. If the license is truly open source, you can fork the project and do what you want with it because now you own that copy. People shouldn't be chained to their work or forced to work for free just because they gave the community years of their life already.
Dear Tim your ideas are precious thank you again dear Tim and keep it up.
Thanks!
Sweet content as always. Love the new intro. Its great to see you, Tim. 👍🏾
Great video Tim
Thanks!
Good content as usual Tim! Watching the rest as I type this. On #1, this may not be immediately apparent to devs who haven't already gone through this, but plan ahead of time how to say "no" if the thing somebody wants you to build for them is: 1) Way too ambitious 2) Glorified IT / networking / fix my computer tech work (this drives me nuts) 3) Not in your wheelhouse (not your framework, language, etc.) 4) Not worth your time or effort, or maybe your plate is already too full 5) They're not offering enough compensation
Don't get talked into doing something you don't want to do. Sometimes the reality is people just can't afford you, and that's okay. You're not obligated to build things for people if you're not 100% comfortable doing it.
I'd love to do software development side hustle on top of my full-time developer job, but I have no idea where to find a project. Perhaps a topic for another video?
I'm not sure what you are asking for. This video has 12 ideas for what to do. If you are looking for what app to build, find a pain point that you have and solve it.
Ahhh apologies! The comment was intended for the previous video of yours "value of side hustle". I didn't realize this video exists which is exactly what I was looking for!
I'm glad you found it!