90 karma · joined November 6, 2009
If someone "paid" me this way, there would be issues.
I'm not optimistic that this will happen. Anecdotally, I expound to acquaintances the risks of unprotected PII or questionably-secured home security apps, but convenience seems to outweigh such concerns.
Regulation is one approach to solve asymmetric information transactions. I don't see how that could be applied in general to software quality, but it could target the cases that have severe or widespread effects.
Sometimes there's not enough time to do that, like when you're thrown into an unfamiliar code base or need to interface with a new API. Then I thoroughly read enough chapters to get the syntax and skim the start of other chapters, plus the index/glossary, again minly to learn terms. The required depth depends on what you're doing. If there's an unfamiliar concept heavily used in the code, of course read those sections more.
I usually avoid exercises because I already have a project or goal, so I work up my own examples that advance those needs but still use the idea or technique of the exercises. I highly recommend trying out a new technique with a small test before applying it at large, or assuming its use as part of the software architecture. You don't want to discover late in the game that the way you planned to use Java generics or C# Pinvoke won't work.
Sometimes the goal is to learn a new technique or dive deeper into the language. I've immensely enjoyed books by Meyers, Alexandrescu, and Sutter, that have more self-contained sections. I still find it useful to read the ToC or skim the chapter introductions, but my mindset is usually more "how can I apply this?", and reading everything straight through doesn't give me enough time to focus on specific things.
I strongly disagree with this, as Usenet and even mailing lists offer many advantages over web forums. With web forums, I can't natively...
- Store, read, search content offline
- Read only new messages
- View thread context
- Access information redundantly (no SPOF)
- Killfile senders
- Integrate viewing and composing with local tools
While a particular site mitigates its disadvantages, perhaps via a better UI or via information not available elsewhere, the medium as a whole cannot. A website might be a fine view of information, but it should not be the only interface to that information. Doing so prevents all of the above uses and makes it much harder to reuse content in ways unforeseen by the original site. I suspect this is the root of the problem -- such reuse is not desirable for most sites, as it conflcts with their business model.
Netrek's macro system was another feature I wish were more widely adopted in games. Receiver-configurable distresses (RCDs) allowed a sender to publish named kinds of messages ("help at location, intercepting X, ship status, bombing planet, etc.) but receivers control the formatting. So I can set up my client to only show your hull+fuel for general distress calls but more data based on the kind of message.
This can make multitasking harder or easier. If tasks mesh well you can work on whichever you're better suited to at the time.
Democracy requires and educated and informed electorate [Jefferson], and if you don't know what the dots are, you can't connect them. Sure, willful ignorance will give you more time to be productive, but when society at large chooses this route, don't be surprised when things go downhill.