1) Go to, present at, local meetups, unconferences.
2) Get involved in OSS projects.
3) Find a mentor.
4) Job hop to something that challenges you and probably pays you more as well.
One possibly valuable angle to look at this from: people with better soft skills sometimes keep their jobs longer and/or get promoted faster/further than people with better tech skills. And this often seems unfair to the techies.
(Written as a techie, consultant and startup guy who has hired, fired, and promoted those from both camps.)
The poor do not have free healthcare here. They have assisted/supplemented medical care in some states under certain conditions, less or none in others (like Illinois, where I live).
I know, as I have opened my home to someone who has been unemployed for some 18+ months, and though housing and food are taken care of, she struggles on the medical front. She previously had Medicaid in NY, which helped a lot, especially with covered prescriptions, but at the age of 30, she is ineligible for that same support here in Illinois.
Fail. "Agile principles are in direct conflict with a traditional software architect role" is a lie. A convenient untruth. Architecture sets guidelines, defines practices, provides reference code, discovers and proves out emerging technologies and frameworks. All this is orthogonal to agile development.
I get the low space message with what seems like a fairly limited number of apps installed, caches cleared and as much as possible pushed to SD ... what is the actual capacity there? HTC Incredible in my case ...
Have you been reading the news the past 15 years? That's precisely what derivatives are used for. Derivatives, and bought-and-paid-for auditors who also provide "consulting services."
I would imagine it has to do with variable penetration and/or a form of constructive interference or resonance, due to factors I couldn't specifically identify offhand.
Businesses doing business on Facebook is exactly more of the kind of thing Facebook wants, don't kid yourself. They won't pursue a lot of this stuff directly themselves, but they're happy for anything that drives revenue without pissing off users. See: Asana.
As someone who does and has worked on enterprise-grade software, and someone who now helps client teams facilitate development, both in-person, remote on-shore, and remote off-shore, I can confidently state: it all comes down to communication, and a lack of communication not only dooms telecommuting, but it's a strong indicator of longer term failure in the parent company.
If ideas, thoughts and facts cannot be clearly captured and/or communicated in a facile fashion, any complex project is risking higher failure rates. In-person buffering is a crutch at best.