News for hackers. Stuff that matters.

rando_guy_here

Re:I Quit Google to Work for Myself (2018) on Thursday December 26, 2019 @10:30AM (#21884417)
Yes, I'm coding all day, but I'm very nice to myself and only do it if I feel up for it. I just naturally have 14 hours in me because it's my own business, which was the really surprising thing after seeing how 40 elsewhere made me feel. I think starting this without the skills to fully pull it off was really key. The learning I've had to do along the way has been really rewarding and has really broadened me out as a tech professional, so there has been this constant positive development in myself as I progress, which keeps me getting up ready to try hard again. No job I've ever had motivated me like this. One other thing I think is key is proper goals. I'm not shooting for a "startup", I want a small business. I want to put something out that actually solves a problem, does it well, and make an honest living off it. I don't think I will ever sell my company for 100 million, but I do think I can make a living and offer myself a nicer working life than I've experienced in the corporate world. That is motivation enough for me.
Re:I Quit Google to Work for Myself (2018) on Thursday December 26, 2019 @07:57AM (#21883461)
17 sounds a bit hardcore, maybe you are very young:) I'm currently doing the exact same route, but at about maybe 14. For those who doubt, please don't until you try it. I have no idea why, but I can actually put 14 into my own project and I feel completely great. I work maybe 6 days a week like this, get up in the morning and just code until I crash. I'm about a year into it now and I honestly don't feel any burnout at all, if anything I'm becoming more energized and excited as my project nears a production quality and launch nears. You can work much harder and longer for yourself than you can for a check, I swear it's true. I was pretty burned after a standard 40-hour at my last job, I work twice as hard now and I feel great. Weird but true.
I think you need to ignore the projects you are trying to do and instead work on getting a decent CI/CD workflow setup, preferably with strong automation driving it. The reason I say this is that it sounds to me like you are a victim of lots of unfinished projects that probably never got running properly in dev, let alone in a deployed environment. I've been there and I know it's very demoralizing to work on something and not close the loop on it, and to be staring at a mass of code that didn't go anywhere. I fixed this in my own projects by starting to treat my side coding as proper development work. I put together a Jenkins container with pipelines that test/build/deploy my code automatically. I actually write tests and spend real time on architectural decisions that I might not have cared about if I was just hacking. The result has been that I'm a stronger dev now, much more professional and productive in my workflow, and my side projects are actual software that builds green and deploys. It took me like a month of side time to set that container up like I wanted it, but it has completely changed how I feel about my work. I take it seriously now. Give this a shot if this sounds right to you, I think it could help. Best of luck:)