Security is somewhat at the developer level, but usually only in a few cases where the software really is security related and gets properly audited before release. Those kinds of software projects are far and few between and even then the documentation is still lacking. Even then that's easier because the people doing the auditing are themselves coders. Documentation requires a whole different skill set (see Word Crimes by Weird Al) that is not always held by coders.

For most other apps, security rests at the system level and is thus outside the scope of what the developers are working on. In some cases the compiler will alert them to common problems.

The best kind of documentation you're going to get for now is really what we have now - some combination of end users writing on their blog, posts to stackexchange, or threads in mailing lists. And some of those may or may not apply to the code that's currently in use.

Longer term, there's things like what synfig does by crowdfunding development efforts including documentation and training. This has a lot of potential, but can quickly get expensive for end users.

I'm a rather odd duck. I did a lot of coding in college and my first job (writing software for hospitals) but have since moved to system administration/design and have a degree in technical documentation. I've written books on Linux and have documentation up on the LDP, some of which is still in use. So I've seen all the sides.

Coders are too busy writing code and making changes to what they write to give time for accurate documentation to be written. The days of "read the code for documentation" are long gone when you have multiple layers of libraries and applications to go through to find what you're looking for. This kinda worked in the days when you could fit an entire Linux install on three floppies but now that you need a few GB there's no way a single human can keep track of it all. Documentation takes time to write and get right. In the age of using github as a distribution and code changes between today and tomorrow, the documentation is suddenly invalid before it's written. Even then, it requires a lot of stupid questions asked by the documentation staff to coders who think they have better things to do.

As for TLDP there was a bunch of problems. Using DocBook was brilliant, but the toolsets were terrible to work with and difficult for people who never used SGML or XML. Linuxdoc was easier to use but really wasn't the way to go long term, especially since the tools were Linux-only and meant the tools were of limited use. Once Wikis took over online there wasn't enough enthusiasm in TLDP to convert and lead the charge.

http://whatthefuckhasobamadone...

I'll grant you that very well may be the case. Removing copays for regular checkups and vaccinations should help a bit, and it should be incumbent on the doctor's office to collect the copay at the time service is provided (in most cases, ER is different). The doctors for my family do that and there's never been a problem.

If the concern is the amount of money that is in collection rather than the number of outstanding collections, then having an insured population will help (or at least cut the amount from tens or hundreds of thousands down to whatever the deductible is).

It's better than going $100,000 in debt.

Probably, but with everyone covered with some level of insurance and getting rid of coverage limits should cut down on the number of people that are in collection for medical reasons.

Yes, since the bills would be covered by insurance.

http://sel4.systems/FAQ/

Is it really that hard to give more background information?

This should allow you to move a phone between Verizon and one of their MVNOs. While Verizon and AT&T use different technologies, T-Mobile and AT&T use GSM and LTE. As VoLTE becomes more popular and increases, I think most cell phone providers will start to standardize on that, which will mean they're all using the same technology (if not the same bands) and moving a phone between Verizon and AT&T may be possible in a few years.

Maybe it happened, maybe it didn't. But this immediate rush to blame/defend lets rumors fly around while the truth takes its time.

Yeah no.

I never said they were immune to crashes, but I did say that the value of the money is based on the economic output of the country. So while the USD isn't backed by gold, it's backed by something much more valuable.

Actual currency has a value that's generally standardized and stabilized by the output of the economy of the country and its value is backed by the government. For all its faults, fiat currency is way more stable over time than bitcoin and its derivatives.

Yeah, Sears is run by a rabid Randian: http://www.businessweek.com/ar...

Aside from dog whistle theatrics, there's nothing that Rand Paul can do about governments at the local level.