Time really is a constraint. It does not make much sense to try to work all the time in order to achieve your goals. As programmers, we really ought to get that there are constraints and trade offs to things.
I would add to the list -- "Don't go it alone. Get other people involved, even if you don't have to."
Journalism ought to strive for compact, quality pieces that can be read at a fast pace. Many articles posted are much longer than they need to be, and their information density is not that great. It's not that it is never good, but rather that it is nowhere near the limits of what humans are capable of as far as communication goes.
Maybe the average article could be denser (though if you can give some examples of what you mean that might be more convincing). The "long form" piece is a rich stylistic tradition and it would be missing the point to try to compress it.
Take John McPhee's writing, for one thing.
I wonder what happens if you take away the reward. Neurons firing is related to energy. The reward has an associated amount of energy. Can it be something as simple as just distributing energy over time?
But is the BS intentional and is it always necessarily false? Or can it be something that is hard to communicate? "The Way that can be spoken of is not the eternal Way." Is this bullshit? If so, how is this information able to propagate over the course of centuries?
Seems to me that one has to separate out what the speaker is trying to imply or impress versus what they are saying. Statistics can be true, but they can also be presented with the intention of impressing the audience with a view that is not true. That is being misleading. It is different from lack of rigor and loose communications.
The article gives some interesting perspective. It talks about security vs. stress. What will be interesting is security vs. motivation. Wondering to what extent the author is motivated by his goals vs. a sense of obligation to his patrons, and how that compares to the motivation generated by insecurity.
Space is hard to get. So much of software involves spaces of some kind and yet we do not seem to think about it very well. Notions of space within software are so often either very rigid and jam-packed or infinite and formless.
Personally, I have enjoyed working in Qt. For anyone looking to get going, I recommend practicing by transcribing the example code and then try tweaking it a little (and more so for Qt / GUI development than with other technologies). It takes a bit of boot time, but once you get going you will find you naturally start to "get it".
You could start by writing comments. There is little chance of any bugs coming from that. If there are any tests available then you could work on understanding the tests and then step through the code in the debugger. Hope that helps.
Here is the argument in a nutshell (if I read it right): (1) The economy not really working that great even though it is working as intended. So it cannot be fixed, because it is not broken (2) For businesses to create new value, they need money. It used to be that they could make their own money, get moving themselves, but now things are dominated by bank lending. (3) Bank lending relies on continual economic expansion to work. (4) But economic growth is going to plateau, due to lack of new things to exploit (i.e. situation similar to lack of new countries for the Roman Empire to expand into). (5) There are alternative money systems that let people create things without bank domination. (6) The political Left is not savvy to this. If you want change you should push for support for alternative money and vote for such candidates.
It is hard to get what people are on about when it comes to anti-bank sentiment. But then again, one could say the same about free software. Seems like the kind of thing where one has to do a bit of their own research and their own thinking.
Time really is a constraint. It does not make much sense to try to work all the time in order to achieve your goals. As programmers, we really ought to get that there are constraints and trade offs to things.
I would add to the list -- "Don't go it alone. Get other people involved, even if you don't have to."