Speaking as part of the Bay Area/Silicon Valley software industry, -if- you can show a good Github portfolio and have a reasonable amount of prior experience, and both display obvious talent, you should be able to get in somewhere. Demonstrable experience > theoretical education.
Networking is important there, since recruiting tends to be much more about buzzwords and degrees than hiring managers are. Being able to get your resume straight to a hiring manager can be make or break.
That changes if you're talking software jobs incidental to other industries (financial, corporate IT, etc.) which is honestly most of them, statistically speaking. It definitely changes if you're talking consulting or field work, since clients want to be impressed by your credentials and your parent company will select on that. It also probably changes if you're talking outside an area that's already heavy in software industry.
Rule of thumb: jeans ok? You can probably manage without the degree if you're good. Khakis required? Not so much.
What the degree buys you, aside from access to the more conservative jobs, is some degree of assumption that you have some degree of training, as well as that you have enough follow-through to finish a degree. But even then, speaking for myself as a frequent hiring team participant, I'd be looking towards your internships, side projects, that Github portfolio, so forth.
Still, if you have the luxury of doing so, get the degree. It does make things easier.