I went from zero programming experience (English major) to a dev job in about a year and a half. There is a LOT of luck involved. In my case, I knew someone at

I went from zero programming experience (English major) to a dev job in about a year and a half. There is a LOT of luck involved. In my case, I knew someone at the company where I got hired, and was hired for a sort of 'unspecified assistant / other' position, and took on every single 'hey we need a script to...' task I could find until they gave me bigger projects. You need a story besides "I am a developer" to get your foot in the door, and your business degree is probably the place to start. What insights could your programming experience give you that a person with a comparable background would never have? What kinds of product opportunities could you spot that a great developer might not notice? So my first piece of advice is about your objective. Try to find the specific combination of skills and interests that you have that few other people have, and then think about where all of them might be useful. My second piece of advice is about your skill set. As someone who is mostly self-taught, it's going to be hard for you to get people to give your work serious consideration. Your reference projects should demonstrate a serious focus on readability, documentation, and testing. I advocate for those things in general, but people like you and me actually have something to prove, and we may not get many chances to show off. So when you learn a new framework or language, make sure you understand the preferred style for code and docs, the way projects are usually organized, and one popular testing framework. Those things will reassure employers that you are serious about doing a good job, not just copying the most-complete stackexchange answer and tweaking it until it works. Good luck.