I hate to be the party pooper, but I'd would tell you to first get traction on your product, and then only quit your job if you feel you have no other choice than quit your job to do this full time.
Also be careful about your contract with your employer, making sure you're not overstepping boundaries that you have signed on. Some employers will take anything you've developped outside of work as their own IP, there are ways around it of course.
Thanks for replying. I totally agree with needing traction first.
I'm putting cart before the horse a little bit by asking the stuff in my post, but I am wondering if I'm chasing a dead end if the odds of getting revenue from a side hustle to be similar to a corporate software engineering salary is pretty much non-existent because of the time limits of trying to do both at the same time.
Comments
I hate to be the party pooper, but I'd would tell you to first get traction on your product, and then only quit your job if you feel you have no other choice than quit your job to do this full time.
Also be careful about your contract with your employer, making sure you're not overstepping boundaries that you have signed on. Some employers will take anything you've developped outside of work as their own IP, there are ways around it of course.
Thanks for replying. I totally agree with needing traction first.
I'm putting cart before the horse a little bit by asking the stuff in my post, but I am wondering if I'm chasing a dead end if the odds of getting revenue from a side hustle to be similar to a corporate software engineering salary is pretty much non-existent because of the time limits of trying to do both at the same time.
History is choc full of people that started something on the side and turned it into a profitable business. Absolutely pursue it, knowing that
a: no tree has even grown taller than the sky
b: Rome wasn't built in a day